[F4RADAR] Lightweight standalone radar application
-
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.
-
What a quick support for 4.35!
Our squadron could move to 4.35 thanks to your work. -
Thank you for the update and your answer, fly safe!
-
Following feedback of disappearing flights I stumbled onto some other quirks as well. Furthermore I had another go at support Windows7, let’s hope I got it right this time!
As always I’m looking forward to your suggestions and feedback and thank you for all your kind words!
version 0.22 changes (29.12.2020)
- Fixed number of planes in table
- Fixed Windows7 support
-
Hi Tumbler,
I had another try as Win7 user, but I still get an error.
Windows 7 SP1,
Microsoft Visual C++ 2015-2019 Redistributable (x64) - 14.27.29016 (hope that is the same as you listed in your first post)The error is
Graphics Exception
Error Code 0x80004002
E_NOINTERFACE
No such interface supportedin file GraphicsDX.cpp line 215
Hope this helps you. If you need additional info just let me know.
Cheers
[EDIT: used F4Radar 0.22]
[EDIT: this with a NVIDIA 1070 TI unfortunately, don’t have driver version at hand atm.] -
Minor update with a small fix (thanks BibleClinger) and hopefully the long awaited Windows 7 support! Do let me know! please note that Windows 7 users most likely have to install Platform Update for Windows 7 to get it working.
version 0.23 changes (01.01.2021)
- Fixed IVC table click still active with table not visible
- Fixed Windows7 support, for real now
-
Hi Tumbler,
thanks for your effort. Much appreciated! So, regarding the welcome win 7 feedback ;). version 0.23 is exiting without error report. I checked the Platform Update (x64 only!), says it is already installed. DxDiag says DX11 is present (BMS runs btw.)
Anything else I can check? Can you provide a debug version that spits out some sort of log file? Only asking, no obligation or expectation.Cheers
-
This post is deleted! -
I found increasing the bubble size of ‘flight’ type in the Editor will enhance F4RADAR reliability.
It might affect the dynamic campaign performance but for TE events it is must have.
The default fighter bubble size is limited to 50nm so it’s a bit short to give a picture.Briefly tested, in MP if Host edited bubble size in DB it synchronizes to clients.
I might update Korea Training Theater later. -
Hi Tumbler31,
We have an issue when we start PvP TE (Blue side in US and RED side in DPRK) that Human RED fighters could not be seen from BLUE C2
We also have a problem that some BLUE fighters also disappears during TE.This TE is an example.
https://drive.google.com/file/d/16m28QGRm6WPWn6FaZWSCHY_Yib5l7-3I/view?usp=sharing
Regards,
-
Just as a reminder, F4R doesn’t use the bubble anymore. It uses the spotting and ID’ing also used by BMS itself. Being spotted depends on a lot of things like EWR, MkI eyeball etcetc. This spotting isn’t perfect and sometimes gives weird situations where you see a contact at 200NM but not the one at 1NM. This also happens in game “chalice, picture clear” and 30s later you have and R-77 inbound.
But what shouldn’t happen, is that friendly contacts disappear. I’ll have a look at the supplied TE. Which theater are you using and which seat did you have as F4R operator?
And sorry about the W7, I’ve set all flags to ensure compatibility and rechecked all used DX11 functionality, so I’m pretty short on options, but I’ll check the last resorts. Don’t hold your breath though.
-
But what shouldn’t happen, is that friendly contacts disappear. I’ll have a look at the supplied TE. Which theater are you using and which seat did you have as F4R operator?
We use KTT. The TE I uploaded on 16th is modified for KTO but if you can test with KTT then This TE is the exact one we had a trouble.
F4R seat is US PKG 1978 DRAGNET31.
The problem is…
If we have humans on DPRK PKG1995 SATAN5 we can’t see them on F4R.
If we have humans on the US side sometimes EL or wingmen disappear from F4R.We did TE with both sides all slot human joined so I’m not sure if it happens for AI.
When I tested a theater in SP both US and DPRK planes were visible.Just as a reminder, F4R doesn’t use the bubble anymore. It uses the spotting and ID’ing also used by BMS itself. Being spotted depends on a lot of things like EWR, MkI eyeball etcetc. This spotting isn’t perfect and sometimes gives weird situations where you see a contact at 200NM but not the one at 1NM.
Was the bubble system unreliable or was it “too much clear that sees everything”?
-
A small update allowing you to change the default STPT 25 used for the bullseye. You can cycle the STPT up/down with Z/X-keys. In cockpit you can change this on the BULLSEYE page in the DED ( list-0-8 ).
version 0.24 changes (23.01.2021)
- Added the option to change the default STPT used for the Bullseye, cycle up/down with Z/X-keys
[…]
Was the bubble system unreliable or was it “too much clear that sees everything”?It was difficult to define a balance indeed and respect some sort of ‘fog of war’, especially for identifying contacts.
-
The image and the tacview file link is our latest PvP training.
All GREEN/RED AC were human joined.
I set RED departure airbase to OSAN, then park GREEN AWACS at SUWON which is only 11nm north of OSAN so that I expected AWACS can monitor RED A/Cs.However, in the entire session, human AWACS couldn’t find any RED A/Cs. And it sometimes drops #2 #3 contacts of GREEN ESCORT. We’ve been flying this TE about 10 times but in recent 4 - 5 sessions, maybe since a certain version of F4RADAR update, we couldn’t see RED A/Cs in the entire session and C2 has no job. I tried to park C2 to different airbases but no lack.
We usually train BVR by set both ALLIED/AGGRESSOR flights to the same TEAM(US) and in that case F4RADAR can monitor all groups in the entire session. Stable as perfect. But when we want SEAD involved we need RED SAM as AI doesn’t shoot friendly. And Aggressors have to be in RED so they don’t shot by friendly(RED) SAMs.
https://drive.google.com/file/d/1mdxDRWFFGvCMXxtgqV2RiH-ji7waa5CP/view?usp=sharing
Our squadron prefers a more reliable radar that doesn’t drop contacts. Even if all contacts are the same color on the F4RADAR, we prefer to ID manually by comms, departed airbases, corridors, etc. But losing important contacts is more critical. IMO modern GCI/AWACS should have more stable radars. ‘Fog of War’ exists in the manual ID criteria.
So if using bubble information can be more stable we’d prefer it, and maybe instead no more automatic GREEN/RED side identification, no callsign displays, for ''fog of war" representation. (Maybe manual ID/callsign set would be demanded)
I know there can be several different demands from others. This is just one of those different wishes.
F4RADAR is very careful that it forces updating. I understand it is because even if some versions may have issues with those balance and respect for ‘Fog of War’, no one can keep using old versions. BMS MP experience kept fair to everyone. I hope you can keep a good balance for the entire community.