[F4RADAR] Lightweight standalone radar application
-
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 chirilo! Which value exactly did you change in the editor in order to achieve that? I mean for the “bubble” size
-
Another update with a small fix. Until i find the time to write a xml-db parser, i’ve included the option to read runways from a .csv file. The zipfile includes an example with the data as used before. Note the following:
- file name should be “geometry.csv” and in the same folder as F4RADAR
- start your runway definition with “[airfield]”
- each runway should be defined as: “objective-X [km], objective-Y [km], RunwayDimPt1-X [ft], RunwayDimPt1-Y [ft], RunwayDimPt2-X [ft], RunwayDimPt2-Y [ft], RunwayDimPt3-X [ft], RunwayDimPt3-Y [ft], RunwayDimPt4-X [ft], RunwayDimPt4-Y [ft]”
the data can be extracted from MC and checking the objectives and then showing the pointdata in the editor.
- Added reading runway from .csv file
- Fixed crash when cycling bullseye stpt before bullseye was loaded
@chihirobelmo: with your and other user’s help, I try to keep improving the program and find bugs. Since 4.35 some odd things seem happen: human contacts disappear, agged units disappear. I’m trying to pinpoint the issue and sadly it’s not just “increase the detection range”. In other words, the spot- and ID-flag is not so much the issue. It seems to be something in the program database itself. I keep looking for the issue and might ask you to try some beta versions with possible fixes.
-
Hello Tumbler
Would like to know what do the numbers mean below the label name?
There’s a three digits which i presume should be flight level?
And then there’s a two digits number - i presume that should be speed?
However that two digits jump from 30-40 to sometimes 70-80 which is really confusing.
What do these two digits number represent?And by the way, is there anyway to ID the difference between Bogey / Neutral / Hostile?
Or maybe incorporating the usage of IFF - M3 code / squawk code etc….Thanks!
-
An update to make the program work with the latest BMS release 4.35.1. Furthermore I’ve reinstated the 200NM/5000ft detection on top of the BMS detection to cope with some weird behaviour. This implies that all aircraft within 200NM of the F4RADAR player or within 200NM of a friendly AWACS and above 5000ft MSL are detected. Within 20NM of the player or AWACS the detection altitude is 0ft MSL.
version 0.26 changes (24.02.2021)
- Updated for BMS 4.35.1
- Reinstated 200NM/5000ft check + normal BMS spotting
@philip the label is altitude in hundreds of feet MSL and the ground speed in tens of knots. The latter jumps around a bit for contacts outside the bubble. I’ve also looked at IFF M3 but didn’t get that operational yet, who knows what the future holds. So for know bogey is bogey until the AWACS can get and ID or your flight has done a VID.
-
Thank you!
-
TvT is a great opportunity to do some live debugging in a MP environment. I managed to catch some mistakes and fixed an error in the table showing the missions for friendlies. Do note that on this version the radar seems to need some minutes to warm up, but due to TvT I decided to release the version anyway. I hope to fix this shortly.
version 0.27 changes (06.03.2021)
- Changed spotting code
- Fixed mission in flight table
-
Great tool! Thank you! During TvT is amazing!
-
F4RADAR can now also be run from the 2D campaign map, so no need to enter 3D anymore (you still can though). In order to run from 2D make sure the campaign/TE time is running and your slotted into a fragged plane. In order to cycle the bullseye STPT load and save the DTC. Threat circles and lines do not yet work from 2D.
Changed the spotting again preventing dropping of contacts. Also added ground contacts. Please note that types.csv shall be present in the same folder as F4RADAR for correct identification of the radar contacts. Note that some double entries are present in the table and sometimes on the scope as well. I will try to fix this asap.
Thanks a lot Bibleclinger, Freudis and all other beta testers I forgot to mention. Great how human GCI’s and F4RADAR bring the TvT even further alive!
version 0.28 changes (17.03.2021)
- Added option to run from 2D campaign map
- Added types.csv file to the package for contact identification
- Added ground contacts
- Changed spotting code
-
Small update
version 0.29 changes (03.04.2021)
- fixed x,y-swap in custom BE-points
-
This thread deserve a sticky given the quantity of people that start using it.
-
version 0.30 changes (17.04.2021)
- internal fixes
-
hi, I launched v0.30 and it says you have to update.
-
Sorry, my mistake. I’ve put v0,31 online. Sorry for the inconvenience.
version 0.31 changes (16.05.2021)
- no functional changes
-
This already awesome program needed a world vector shoreline map underlay…
So I made one…
-
@b.s.:
This already awesome program needed a world vector shoreline map underlay…
So I made one…
Nice! Can this be made part of the program install Tumbler31/B.S.?
-
A suggestion if I may: don’t let the program force quit if the user is on an outdated version.
Notifying the user of the update, sure, but force quitting just gets in the way if you need to quickly take up the GCI role and don’t have the time to update. IMO the pros of this feature simply don’t outweigh the cons.
After all, encountering already fixed bugs when using an older version is the user’s prerogative.
-
Nice! Can this be made part of the program install Tumbler31/B.S.?
+100.
Couldn’t agree more. It would be far more than useful, because this would make the map immediately understandable for all (me, as first! :D), you know.
With best regards.
-
Lightweight standalone radar application not working:p
-
Is there a reason you haven’t updated BMS to U1 yet? If not, can you apply the update and then check if F4RADAR works?
-
Hello Tumbler,
With the recent update of BMS 4.35 U2, my F4radar can no longer run. It shows an error message “can only run based on BMS4.35.0”
I wonder if there’s any solution for this so that i can continue to run human GCI.
Thanks!Kind regards