Download

https://github.com/BenchmarkSims/bms-blender-plugin

Changelog

• 1.0.7 (03.04.2025)

  • Hotfix for previous compile issues

• 1.0.6 (03.04.2025)

  • Fix 3dbuttons.dat export format incorrect

• 1.0.5 (22.01.2025)

  • Fix export of nested translation DOFs

• 1.0.4 (18.01.2025)

  • Bounding box & scaling fix
    • fix export scaling, blender uses meters as base unit, BMS works in feet, so always apply meter-to-feet factor
    • apply the scale factor as set in scene->units->unit scale
    • bounding box uses min/max coordinates of mesh entities only and excludes eg camera
    • radius in parant.dat is correctly scaled
    • default nr of switches and dofs set to zero in parant.dat to prevent editor crashes

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.

---

1. Download

---

You can get it ==> HERE <== the zip password = bms

---

2. 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”. Also make sure to install the latest version to prevent crashes at startup
• Windows 7 users most likely have to install Platform Update for Windows 7

---

3. 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)

---

4. 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, yet shall be hot to see threat circles and lines
  • 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
• version 0.40 changes (27.08.2022)
  • Updated for BMS 4.36.2
• version 0.41 changes (17.09.2022)
  • Updated for BMS 4.36.3
• version 0.42 changes (09.01.2023)
  • Updated for BMS 4.37.0
• version 0.43 changes (04.02.2023)
  • Updated for BMS 4.37.1
• version 0.44 changes (19.03.2023)
  • Updated for BMS 4.37.2
• version 0.45 changes (01.08.2023)
  • Multi threading
• version 0.46 changes (03.08.2023)
  • Fix mode switching in multiplayer
  • Fix deagg velocities not shown
• version 0.47 changes (03.08.2023)
  • Added dedicated naval shape
  • Added the option to retry version checking
  • Fix crash on certain jpg formats
  • Fix BRAA/BE tool tip not begin shown
• version 0.48 changes (04.11.2023)
  • Updated for BMS 4.37.3
• version 0.49 changes (28.11.2023)
  • Updated for BMS 4.37.3.2
• version 0.50 changes (03.06.2024)
  • Updated for BMS 4.37.4
• version 0.51 changes (08.07.2024)
  • Updated for BMS 4.37.4.1
• version 0.52 changes (09.09.2024)
  • Updated for BMS 4.37.4.2
• version 0.53 changes (02.11.2024)
  • Fix 2D-mode
• version 0.54 changes (08.12.2024)
  • Updated for BMS 4.37.5
• version 0.55 changes (20.01.2025)
  • Updated for BMS 4.37.6
• version 0.56 changes (27.03.2025)
  • Updated for BMS 4.37.7
  • Optimisation when not showing ground units
• version 0.57 changes (28.03.2025)
  • Fix 2D-mode

#f4radar

@Betto amazing work!

@Radium said in Updating some 3d models for ground vehicles:

Meeting BMS team standards (every model suggested to be transfered will be independantly judged, regarding its coherence for KTO theater, and its overall quality.

I’d say the quality offered here, is light years better than what we currently have

Updated for 4.37.0

• version 0.42 changes (09.01.2023)
  • Updated for BMS 4.37.0

• version 0.55 changes (20.01.2025)
  • Updated for BMS 4.37.6

also a reminder of the available options

It was a bit of a puzzle but the bug was found. So don’t throw away your ol’ trusty Cougar, also no need to put in an Otto P1, just a bug hiding in the code since 1998 waiting to strike

Seems we overlooked page 4 of the VR guide which still shows the old configuration options. The correct overview should be

set g_nVRHMD 0                              // Enables VR, 0 no VR, 1 SteamVR, 2: OpenXR (default 0). Note, can be overridden by -vr or -novr command line options.
set g_fVRZoom 2.0                           // Adjust zoom factor for VR ZOOM (default 2.0).
set g_nVRHMCSEYE 0                          // Choose HMCS renders, 0 Right eye, 1 Left eye, -1 Both eyes (default 0).
set g_fVRResolution 1.0                     //  **!!keep at 1.0 in 4.37.6!!** Adjust VR resolution multiplier (default 1.0).
set g_bVRParallelRenderThread 1             // Enable Multi-Thread optimization for VR (default 1).
set g_bVRNoPresent 0                        // Enable the companion window in VR, thus only HMD will show image in 3d (default 0).
set g_bMixedRealityCockpitCoverEnabled 0    // Enable the Mixed Reality Cockpit Cover (default 0). CNote, can be toggled in game.
set g_fVRIPDMultiplier 1.0                  // Adjust world scale, (default 1.0).
set g_fNoVRF15HUDSymbolPositionOffset 21.0  // Adjust F-15 HUD symbols for non VR users (default 21.0).
set g_bVRPredictFutureHeadMatrices 0        // Enable predict future head matrices for SteamVR (default 0). Note, only works when 'set g_bVRParallelRenderThread 1' is set.

noteworthy are g_fVRZoom replacing g_fVRZOOMFOV and the additon of g_fVRIPDMultiplier

This and potential 4.37.6 changes, will be updated in the new document and the Falcon BMS.cfg file.

• version 0.50 changes (03.06.2024)
  • Updated for BMS 4.37.4

Another small update to 1.0.5 fixing the translations DOFs, hope this will help our blender modelers! Do let me know your feedback.

Seems the advanced render controls also needs some TLC, so I’ll give that a look next.

The server has the option to require unaltered data files to prevent clients from giving themselves super powers, see g_bRequireSameAcdataMP. The files checked are:

• .dat files in Data\Sim\
• .xml files in Data\TerrData\Objects

The server checks the hash of the clients and will not allow connection if there’s a mismatch. As it’s a hash check, even an added space will cause failure.

To help finding the culprit, a tool was added to u3. In <BMS folder>\Tools\BMS Hash Checker\ you’ll find it. The server can create a checksum file, which clients can use to find the file that is causing the issue

@MaxWaldorf said in Balkans campaign CTDs when starting mission:

@Seifer sorry, I’m not managing Balkans…

think seifer mentioned KTOI is also affected?

Still valid

https://forum.falcon-bms.com/topic/20866/enabling-dump-files-at-all-times-and-creating-frozen-game-dump-files

@turkster72 said in Radar Cursor Randomly Stops Working:

@chihirobelmo Yes, that’s prob it - I have DMS UP on a shifted layer - will rebind. Thanks

it should also work with dms up on shifted layer

@HaggisHero yes the issue is known. It’s a bug. Hopefully @airtex2019 can give it some TLC

@airtex2019 @chihirobelmo this pops up quite regularly. Has this bug become a feature or can you fix it?

@VDK enjoy it while it lasts…

15ft miss from a 18.000ft drop, that’s pretty amazing for a dumb bomb.

@rubbra said in 4.37.7 Audio - Betty has a stammer for Pull Up:

@Tumbler31 as I say in the post above - I have 100% not changed this, but will gladly test what you post above and report back. Seems a bit premature to mark it solved though!

yeah, maybe you should ask a dev what could be the fix

@rubbra said in 4.37.7 Audio - Betty has a stammer for Pull Up:

@Tumbler31 In User.cfg nothing.

In Falcon BMS.cfg, which is untouched by me, and a clean install when .7 updater screwed up my install:

set g_sCompatibleChanges "all"                       // Dev Setting
set g_sNonCompatibleChanges "all"                    // Dev Setting

As I say, untouched by me.

That’s not unchanged, reset to default
set g_sNonCompatibleChanges "none+HEAD_TRANSLATION_OFFSET+PREPARE_PROTOFY_FM+MIXED_REALITY+SELF_HEALING_AAR+ACDATA_PROTO+F15_FIRE_TEST+FIGHTER_TRACKS+DISPLAY_PLAYERS_COUNTDOWN+DONOR_UI" // Dev Setting

Please show what’s the set g_sNonCompatibleChanges entry in your .cfg