F4RADAR has been updated to work with 4.36.1.

I might have missed lookup here and there, so let me know if something needs to be fixed. Enjoy!

• version 0.38 changes (01.08.2022)
  • Updated for BMS 4.36.1

I’ve created a lightweight standalone radar application for BMS from scratch : F4RADAR. It shows all contacts spotted and gives information on the type when also identified. It shows individual planes and therefore should also be suitable for ATC, and the flights outside “the bubble”. With the right mouse button you can also draw BRAA-lines and it has the option to show a background map. It doesn’t require additional software for other players or server modifications. Do give it a try a let me know if you have suggestions or encounter bugs.

Download

You can get it ==> HERE <== on my google Drive folder.

Requirements

It should run straight from the box but formally installation of F4RADAR requires

• DirectX11 (which you are going to need for BMS anyway)
• 64bit Windows10 (feedback from Window7users is welcome)
• although already present on many systems Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 (click link) is required. Normally only the 64x version is needed, but some reported all 3 versions, x86, x64 and arm were needed to fix the issue of “vcruntime140_1.dll is missing”.
• Windows 7 users most likely have to install Platform Update for Windows 7

IVC set-up

To have IVC working properly, some small changes are needed so everybody hear each other This is very well explained by chihirobelmo in this post. Thanks chihirobelmo!

• uncheck ‘IVC enabled’ to have the IVC client running standalone.
• the name in IVC-client should be different than your BMS name.
• pilot set set ‘outsider=all’ in your ‘IVC client.ini’ (remove # comment at the beginning of the line)

Running F4RADAR

The program does not require a specific location, nor does it have to know where you installed BMS. It is fully standalone.

• The program has two run modes: BMS in 2D or 3D. In both cases the program will show you the radar contacts

  • 3D-mode: your plane shall parked in the ramp, when you fly the program will turn-off
  • 2D-mode: in the 2D campaign map view make sure the clock is running and you’re slotted into a plane, load and save the DTC to be able to cycle the bullseye STPT

• Airfield data is provided in geometry.csv which shall be in the same folder as the program. The current provided data reflects the 4.34.4 airfield data but can be user modified

• Contact identification information is provided in types.csv which shall be in the same folder as the program

• Various toggle buttons and the View menu allow you to show or hide scope items

• The options menu (Edit->Options…) allows you to configure color, sizes and control setup. The settings can be saved in the F4RADAR.ini file which will be read upon next startup. The file will be placed in the same folder as the program

• The help menu (Help->View Help) gives brief explanation of the program and functionality

Version history:

• version 0.1 initial release (18.06.2020 )
• version 0.2 changes (25.06.2020 )
  • Added the option the load and toggle a background map. Any size will do as it will be stretched to the 1024x1024km grid but I kindly suggest maps found in the WDP installation folder
  • Added the option to toggle the Bullseye being shown
  • Increased detection range
• version 0.3 changes (26.06.2020)
  • Speedbased magnitude of heading vectors
  • Decluttered info when drawing a BRAA-line and changed color for clarity
  • Toggle added in view menu for display of the labels
• version 0.4 changes (04.07.2020)
  • History trail for contacts
  • Keyboard keys to toggle map, history, labels and bullseye
  • Options for all colors, bullseye rings, vector length, history length, size of contacts, and transparency of the map
  • Added the option to save preferences in .ini file, will be placed in same folder as .exe
• version 0.5 changes (12.07.2020)
  • Added flights “outside the bubble”, for now both friendly and hostile show up as “bogey”
  • Fixed crash when you tried to use the program whilst flying
• version 0.6 changes (20.08.2020)
  • Added USA airbases and associated toggle
  • Added game time in the upper right of the window
  • F4RADAR now shows friendly contact below 5000ft and with the detection range
  • Fixed BE cross disappearing on secondary monitor
• version 0.7 changes (20.08.2020)
  • fixed game time only showing when in 3D
  • added option to change color of airbases
  • added a minimum detection speed for friendly contacts
• version 0.8 changes (24.09.2020)
  • added callsigns outside the bubble, these contact have a trailing dash in their name
  • detection range of 200NM also added to friendly AWACS
  • fixed saving the minimum detection speed
• version 0.9 changes (24.09.2020)
  • added the option to swap mouse button functions (default now right to pan)
  • fixed detection range back to 200NM instead of 200km
  • removed the trailing dash for “out of bubble” contact, as apparently this refers to NORDO.
• version 0.10 changes (05.10.2020)
  • added the option to use the program when your under your parachute or dead, thus not parked on the ramp
  • added statusbar with program and radar status plus game time
  • fixed game time by adding days when running longer campaigns
  • fixed issue of loosing connection to the 3D state of BMS
• version 0.11 changes (13.10.2020)
  • added the a scrollable and moveable (click header) table showing flight info, for bogey limited to number of planes
  • added support for multination war, neutral, hostile and at war are shown as bogey
• version 0.12 changes (15.10.2020)
  • added contacts are now shown when spotted in BMS and plane info is given when identified in BMS, 5000ft restriction and 200NM detection limit have been removed
  • added plane info in the table when contact is identified in BMS
  • added latitude and longitude mouse position in the status bar
  • fixed table is shown in alphabetical order
  • fixed plane information in table, previous release showed wrong info for certain contacts
• version 0.13 changes (26.10.2020)
  • added spotting and identifying of contacts can now also be done by allied nations
  • added lat/long for all theaters in the northern-eastern hemisphere
  • fixed map image for 2048x2048 theatres like POH
  • table no longer shows empty flights
• version 0.14 changes (29.10.2020)
  • added toggleable context menu to show detailed info at mouse over
  • added yardstick
• version 0.15 changes (30.10.2020)
  • fixed bug in aircraft type in context menu
• 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
• 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
• 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
• version 0.19 changes (06.12.2020)
  • Fixed error in spotting
• 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
  • Final version for BMS 4.34.4
• version 0.21 changes (23.12.2020)
  • Updated for BMS 4.35.0
  • Disabled airbases
• version 0.22 changes (29.12.2020)
  • Fixed number of planes in table
  • Fixed Windows7 support
• version 0.23 changes (01.01.2021)
  • Fixed IVC table click still active with table not visible
  • Fixed Windows7 support, for real now
• 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
• version 0.25 changes (30.01.2021)
  • Added reading runway from .csv file
    • 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]”
  • Fixed crash when cycling bullseye stpt before bullseye was loaded
• version 0.26 changes (24.02.2021)
  • Updated for BMS 4.35.1
  • Reinstated 200NM/5000ft check + normal BMS spotting
• version 0.27 changes (06.03.2021)
  • Changed spotting code
  • Fixed mission in flight table
• 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
• version 0.29 changes (03.04.2021)
  • fixed x,y-swap in custom BE-points
• version 0.30 changes (17.04.2021)
  • internal fixes
• version 0.31 changes (16.05.2021)
  • no functional changes
• version 0.32 changes (29.06.2021)
  • Updated for BMS 4.35.2
• version 0.33 changes (30.06.2021)
  • fixed incorrect slot number in flight
• version 0.34 changes (07.08.2021)
  • internal fixes
• version 0.35 changes (19.10.2021)
  • Updated for BMS 4.35.3
  • Small fix in ground spotting
• version 0.36 changes (23.04.2022)
  • Updated for BMS 4.36.0
  • Added naval contacts
• version 0.37 changes (29.04.2022)
  • Fixed type lookup
• version 0.38 changes (01.08.2022)
  • Updated for BMS 4.36.1
• version 0.39 changes (03.08.2022)
  • Fix slot number

#f4radar

Update to v0.37:
Updated the type file and changed some internals to reflect the correct type of the identified contact

Thanks for the reports!

F4RADAR has been updated to work with 4.36.0. It now also shows naval contacts (if they are spotted and/or identified).

I might have missed lookup here and there, so let me know if something needs to be fixed. Enjoy!

• version 0.36 changes (23.04.2022)
  • Updated for BMS 4.36.0
  • Added naval contacts

Thanks for the report. The issue is confirmed, we’re looking into it.

New version to work with 4.35U3

• version 0.35 changes (19.10.2021)
  • Updated for BMS 4.35.3
  • Small fix in ground spotting

And thanks all for the suggestions. ‘Remembering’ contact might be an idea indeed.

And for Taxiways the situation is a bit more complex. You can extract info from the xml’s like F4A did, but then you get the texture tiles which gives some weird plots.
Another idea is to include a new category in the geometry file to allow line drawing. The coordinates you then have to extract from eg the editor. That a bit of a puzzle, so something automated with be better. I’m open for suggestions.

There are indeed some differences, these are deep in the code but I’ll give it a look. Do note that ASEC is where it should be (use gun cross as reference), but it seems the speed and alt-tapes should be a bit further outward and lower, and the bearing tape a bit lower

Make sure your provider supports IPv6: https://test-ipv6.com/

Great to see there are still many active user of F4RADAR!

And as the last the posters have noticed, the program has some quirks. These are related to issues in BMS itself and have proven to be quite difficult to solve. So for now you’ll see double entries in the flight table, and worse, some contacts dis- and reappearing on the scope.

I’ll put in a change request at LM and ask them to update the documentation accordingly

I’ll put in a change request at LM and ask them to update the documentation accordingly

Well noted, thanks. Some silly mistakes, should be fixed in a next release.

Confirmed and fixed. Thanks for the clear description!

Issue confirmed and fixed. Thanks for the report and clear repro!

Small fix in slot number, thanks for the report @BibleClinger

• version 0.39 changes (03.08.2022)
  • Fix slot number

F4RADAR has been updated to work with 4.36.1.

I might have missed lookup here and there, so let me know if something needs to be fixed. Enjoy!

• version 0.38 changes (01.08.2022)
  • Updated for BMS 4.36.1

@Carbinjay xlog, crash log and dumps would help.

And make sure to update your Nvidia drivers. Apparently it can cause the issue you describe (see similar names topics)

@Icer hmmm that one. Can you also post the .xlog? You have to run with -mono

@Icer it worked and now it doesn’t anymore? That’s curious, did you change something in between?

And please share the full dump and post post the text file logs files here, I might have a look on my phone

@actrade cool you got it working now! The update installation process leaves some room for improvement as you might have noticed…

Anyway, enjoy u1!