You can disable the mouse wheel entirely (more on that below) but I don’t think you can disable the mouse wheel for zoom alone. No idea why the mouse wheel click doesn’t work for you. Are you using any 3rd party tools (e.g. Alternate Launcher) to set your key bindings? If so, make sure you actually assigned a function to the middle mouse button.

If that doesn’t work, you’ll find a file called Falcon BMS.cfg in your Falcon BMS\User\Config folder, where you can do several things:

1. Razor’s option works, but if you don’t want to get rid of your FOV change entirely (other than the “Look Closer” function, L by default), look for this command: “set g_fFOVIncrement”
   By default, this is set to 5, which means you add or substract 5 degrees of FOV with a single change, which is a lot and can be disorienting when it happens unexpectedly like when you’re adjusting a knob. Change that to 1, however, and the zoom in/out transition will be a lot smoother, having far less of a visual effect, and allow you to recover quicker and more easily.

2. To disable the mouse wheel entirely, add these lines:

set g_sScrollUpFunction “SimDoNothing”
set g_sScrollDownFunction “SimDoNothing”
set g_sMiddleButtonFunction “SimDoNothing”

In order to reset the default functionality of all, delete the lines or adjust them as follows. This may also fix your middle mouse button issue:

set g_sScrollUpFunction “FOVDecrease”
set g_sScrollDownFunction “FOVIncrease”
set g_sMiddleButtonFunction “FOVDefault”

@seifer said in IVC stereo separation possible?:

Unrelated to this, but I wonder if any jet implementation does 3d sound for RWR spikes. Does anyone know? That would be pretty cool!

Check this website: https://www.terma.com/markets/air/audio/3d-audio/

From what I can find so far, they have supplied to or have contracts with the RDAF, BAF and RNLAF for their F-16 MLUs, with USAF and/or its ANG/AFRC for the A-10C and F-16, and they’re working with BAe, so I’m guessing Eurofighter Typhoons and possibly F-35 also have it.

It’s a theater Falcas is working on, but is unfortunately not public yet.

@seifer said in IVC stereo separation possible?:

Unrelated to this, but I wonder if any jet implementation does 3d sound for RWR spikes. Does anyone know? That would be pretty cool!

Check this website: https://www.terma.com/markets/air/audio/3d-audio/

From what I can find so far, they have supplied to or have contracts with the RDAF, BAF and RNLAF for their F-16 MLUs, with USAF and/or its ANG/AFRC for the A-10C and F-16, and they’re working with BAe, so I’m guessing Eurofighter Typhoons and possibly F-35 also have it.

It’s a theater Falcas is working on, but is unfortunately not public yet.

You can disable the mouse wheel entirely (more on that below) but I don’t think you can disable the mouse wheel for zoom alone. No idea why the mouse wheel click doesn’t work for you. Are you using any 3rd party tools (e.g. Alternate Launcher) to set your key bindings? If so, make sure you actually assigned a function to the middle mouse button.

If that doesn’t work, you’ll find a file called Falcon BMS.cfg in your Falcon BMS\User\Config folder, where you can do several things:

1. Razor’s option works, but if you don’t want to get rid of your FOV change entirely (other than the “Look Closer” function, L by default), look for this command: “set g_fFOVIncrement”
   By default, this is set to 5, which means you add or substract 5 degrees of FOV with a single change, which is a lot and can be disorienting when it happens unexpectedly like when you’re adjusting a knob. Change that to 1, however, and the zoom in/out transition will be a lot smoother, having far less of a visual effect, and allow you to recover quicker and more easily.

2. To disable the mouse wheel entirely, add these lines:

set g_sScrollUpFunction “SimDoNothing”
set g_sScrollDownFunction “SimDoNothing”
set g_sMiddleButtonFunction “SimDoNothing”

In order to reset the default functionality of all, delete the lines or adjust them as follows. This may also fix your middle mouse button issue:

set g_sScrollUpFunction “FOVDecrease”
set g_sScrollDownFunction “FOVIncrease”
set g_sMiddleButtonFunction “FOVDefault”

@16th:

So I used to be able to use the A/R missile step button to open the fuel door….I guess that 's not happening anymore?
I gotta take my eye off the prize and mouse click that sucker? Go tumbleweed everytime!
Short cut key, here I come!
Realistic as hell.
Anyone got any pointers about this?

Toggling the A/R door is or used to be, by default, on the shifted DX layer of the NWS/MSL STEP button in (certain?) key files. That may be what you’re referring to?

The low altitude camera and the RECCE POD (only found on BAF MLU, I believe) are only eye candy, unfortunately.
IRL, what they do (AFAIK) is that when you press the “release” button, the camera will make several pictures of the area you’re flying over. These pictures are stored in the camera’s memory, offloaded after landing and shipped to intelligence services who will develop and analyse the footage. In BMS, the pod doesn’t take photos or store data, so at best, your RECCE patrol will temporarily add intel on the 2D map.

That said, these days, the low altitude camera and RECCE pod has been replaced by the NTISR (non-traditional intelligence, surveillance, recon) capabilities of targeting pods like the Sniper, which is safer (more stand-off range, no longer requiring overflying the area), more versatile (not dependant on aircraft orientation or movement during operation, direct feedback to the pilot of what he’s aiming at) and probably has better camera options (resolution, spectral imaging, zoom levels, …)

@Bad:

Exact

You can use the SpotLight to capture the cockpit at night (usefull when Ramping)

Spotlight only works after you’ve turned the BATT on, though. What we need are finger lights.

I don’t know if the LAR only shows aerodynamic range in which the bomb is expected to be able to reach the target from point of release, or if it’s updated based on the bomb settings, but the closer you are to target, the harder it would seem to achieve bomb impact conditions of speed X at angle Y from bearing Z. Especially because most JDAMs have no dedicated surfaces to create drag or effect big direction changes.

As such, wouldn’t the jet simply prohibit release if it calculates that the criteria set through the SMS page are not / no longer attainable?

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?

@victor031:

LOL….
on relative time scale 1 falcon day is equal to how many days??
I think Falcon Time scale may be designed just like Geological timescale LOL

There is no scale: 3 - 4 Falcon weeks could mean right now, high noon today, spring next year or the end of this decade.

Or as Blu3wolf puts it:

It will get here when it gets here. Should arrive 3 to 4 weeks after the last time someone asks for it

@Blu3wolf:

but typically fighters switch to departures on the runway.

As always, it depends. I have heard such an early switch to Departure once on a Dutch QRA audio excerpt, but AFAIK, in the Belgian Air Force, you only switch to Departure once safely above a certain altitude. I think it may even be after the whole flight is properly airborne.

What is weird and IMO needs changing, however, is the “Fly heading …, resume own navigation” you get by departure. It has to be one or the other. You can’t have both in one transmission.