[F4RADAR] Lightweight standalone radar application
-
After tedious work I managed to add taxiways for quite some KTO airbases for those into ATC and ground ops. Do let me know if you like it and if maybe taxilines are missing.
version 0.16 changes (02.11.2020)
- Added taxiways for Kunsan, Osan, Seosan, Sachon, Choongwon, Chongju, Suwon, Yechon, Mandumi, Kwangju, Hoengsong, Kangnung, Pohang, Sokcho, Taegu, Pusan, Pyongtaeg, Kimhae
-
I Tumbler, it seems good on Win 10, but not on Win seven. The F4Radar failed when BMS entering 3D.
With my first look on Win 10, the position of the planes is good for Chongwoon, my friends will check the others airfields. -
Tumbler, good work!
I have some recommendations for improvements:
1. label deconfliction - If there some A/C flying close together, nobody is able to read call sign, height nor speed. It would be better, that a user can grab the label and move it to an other range and/or bearing from the track symbol and fix it there.
2. hook of track symbol - to measure the bearing and range between two a/c it would be better to assign the line to the tack symbols so that you get a read out of bearing and range continuously. State of the art would be to draw multiple of this bearing/range lines between multiple a/c.
3. draw of static lines and points to mark something on the scope
4. import of routes, preplanned threat steerpoints and steerpoint lines from the current TE of BMS (selectable)
5. display of BE-position of the cursor on an movable window and
6. display of the bearing/range from a certain point or hooked track on the cursor position
7. display on M-number instead of speed on an a/c label (switchable)
I know this is a lot of work, but it would make the job of an aircraft controller much easier.
And I would prefer to couple the detection volume on the AWACS or the coverage of the ground RADAR station(s), that’s more realistic.
Regards Prot
-
So after verification, all your AB improvements are good. Nice job Tumbler.
For next job, i wish to have a movable BE, and your soft will be fully usable for us.
-
Anyone trying to use this on a small P2P MP Coop Campaign setup? Trying to find an out of the way flight close to TO time to put the “AWACS” pilot in and leave on the Ramp is not easy. To test it out I put my AWACs pilot in as my wingman and left him there, not an ideal situation, but I looked at every other base and it just sat in the “Planning” stage with no new flights fragged. Ideally putting him in a C130 or and actual AWACs would be great… or am I missing something?
-
After a test this Wednesday, with 9 pilotes, all is perfect, at Choongwon and Chongju, but only on w10
Ty -
The latest release now also plots the PPT circles and lines as visible on the HSI. Please note that the plane needs to be hot!
I’ve also tried to declutter the view. Zoomed out the label will now only show the flight label. eg DART1. With sufficient separation between the contacts it will show the individual labels. This is a toggleable option and you can tune this distance in the option menu with “intra flight distance”. Also note that when the flight splits in elements, it will show the elements names eg DART11 and DART13. Do check it out and let me know if it works for you.
Furthermore I’ve done quite some changes under the hood you most likely will not notice, except for the fact the program now uses Direct X11. So please be sure to have that installed. You are going to need that for 4.35 anyway.
The program should work with Windows7 now, but please let me know if that is really the case.
Finally thanks again for your suggestions and feedback and especially Eagle-Eye for testing the software. All you help and feedback is highly appreciated, keep it coming!
version 0.17 changes (18.11.2020)
- Added PPT and lines as visible on the HSI and stored in DTC, note that jet needs to be hot
- Added declutter option which only show flight or element name when zoomed out
- Added taxiways not plotted when zoomed out
- Implemented DirectX11 and Windows7 support
-
Hi and thank you for your work.
Sadly I can’t get your software to work (W7/DX11, redistributables are installed), it crashes at launch with the following error:Any idea why that might be?
Thanks! -
Hi and thank you for your work.
Sadly I can’t get your software to work (W7/DX11, redistributables are installed), it crashes at launch with the following error:Any idea why that might be?
Thanks!I cannot see the attachment, so could you try again? I don’t have w7 myself, so it’s a but difficult to test for me.
-
Edited, seems like there was a problem with the PNG…
-
Edited, seems like there was a problem with the PNG…
Thanks, could be the issue you’re running 32bit W7 and some errors with the libs. I’ll look into it.
-
Nope, Win 7 x64 here
-
Another update, this one allows you to select (and see) the IVC frequencies. Just launch your IVC-client, connect to the server and you’re done. You don’t have to select ‘force local control’.
By the way, did you know you can move around the tables by clicking on the header of a table and dragging it? And thanks for your suggestions and bug reports! @seekles, W7 is still on the todo-list.
version 0.18 changes (05.12.2020)
- Added IVC support (currently only x64 version tested)
- Added allied contacts are always shown
- Fixed errors in mission type indications
- Fixed ‘bad alloc’ crash
-
A quick update with an important fix in spotting and thus showing aircraft on the scope and in the table. I had some previous reports on this issue, but couldn’t find a way to reproduce it. But specific conditions of another case helped me spotting the erratic behaviour. So keep those reports and feedback coming!
And whilst I have your attention, a short reminder how to have IVC working correctly for the GCI: uncheck ‘IVC enabled’ when setting up the MP session. Your IVC-client should run standalone not connected to BMS in order to be seen as an outsider. This was very well explained by Chihirobelmo in this post. Thanks again Chihirobelmo!
version 0.19 changes (06.12.2020)
- Fixed error in spotting
-
Another update to fix the program freezing for short periods. And by popular demand leading zeros are added to the angle of BE and BRAA indications.
Also note that to prevent IVC attenuation, you should use a different name in your IVC-client than the one you use in BMS.
version 0.20 changes (09.12.2020)
- Added leading zero(s) at the angle indication for BE and BRAA
- Fixed program freezing for short periods
-
An incredible app ! Thank you for developing and more importantly, SHARING !!!
-
@fjp:
An incredible app ! Thank you for developing and more importantly, SHARING !!!
Gladly agreeded.
And I’d add “And updated constantly, as well!”, if I dare to.
With best compliments, dear Tumbler, and best regards to all.
-
Hi Tumbler, thank you very much for this must-have and the work you’re still doing to improve it.
Will it be possible to see the aircraft or pkg Squawk/Iff ?
Merry Christmas in advance and HNY, hope this one will be better for everyone. -
F4RADAR now supports BMS 4.35.0. As there we’re some changed in the airbases and I didn’t have time to update those, this option is temporarily turned off.
Enjoy and let me know if you run unto bugs or have ideas for improvement. And yes, squawk codes are on my wishlist as well.
version 0.21 changes (23.12.2020)
- Updated for BMS 4.35.0
- Disabled airbases
-
Thanks a lot for this update too…
and Merry Christmas (to all your beloved ones too), most of all!
Keep always safe, with best regards.