THE BUG

After launching an AIM-9M / AIM-120C missile a misplaced bright dot can be observed trailing the missile.

This bright dot changes it’s position relative to the missile as the missile alters it’s flight path to the target.

The farther the missile becomes from the F-16 the more the dot gravitates towards the center of the exhaust trail of the missile.

The bright dot disappears when the fuel in the missile is depleted, this leads to the conclusion that the Trail Dot is a misplaced part of the exhaust animation for the missile.

The Trail Dot can be observed from the VIEWINT: Pan (3D) Cockpit and from the VIEWEXT: Orbit Camera.

When observing the missile using the VIEWEXT: Weapon Camera the Trail Dot is absent, and the missile animation appears to function as intended.

GENERAL INFO

The bug was noticed during Instant Action \ Fighter Sweep gameplay.

Date: 24.10.2022

Falcon BMS Version: 4.36.3 (x64) 26590

https://i.postimg.cc/tJML95Qy/Trail-Dot.png

Need someone to check and confirm.

Anyway, I am glad that the Falcon BMS is doing really good.

Super glad that the MICROPROSE gave it’s official approval to the Benchmark Sims.

The latest (4.37.4) Falcon BMS trailer looks super good.

The future for the Falcon BMS is looking bright.

Hi.

Is the Advanced Precision Kill Weapon System II (APKWS II) implemented in the Falcon BMS?

Or is it planned to be implemented?

Some more FREE INTEL: the DCS World F-16C Viper has no APKWS II implemented.

@MaxWaldorf said in BUG: Orbit Camera Position Reset:

@FierceLV Not a bug, it is by design…

Hi.

Personally, I think Falcon BMS is beyond what is considered good, but still, it can be even more good.

I think Falcon BMS lacks intuitive camera management.

The overall camera management system is plagued by inconsistencies, just to name the few:

1. FOV in Orbit Camera doesn’t reset on reentry.

2. Position in Orbit Camera resets on reentry (case with disabled mouselook).

3. Zoom in Orbit Camera resets regardless of mouselook or NUMPAD keys.

4. Zoom in Chase Camera resets on reentry.

5. You can’t switch directly to Chase Camera from Flyby Camera (need to wait while it does automatically).

6. FOV in Chase Camera doesn’t reset on reentry.

7. After switching to Flyby Camera the Chase Camera FOV resets.

8. After switching to Flyby Camera from Orbit Camera the Orbit Camera FOV doesn’t reset.

9. There is no option to switch directly to the Radar Locked Target Camera, instead Enemy Aircraft Camera picks random aircraft, and you need to cycle through all of those to find the one you are locked onto.

All by design? With all respect I find this design to be inadequate of the awesome jet that is Falcon BMS.

Need to state one important point, just in case:

If something is truly good - then it is good, it doesn’t matter where this good already is implemented, the Falcon deserves the best possible. So keeping this camera design as it is is weird.

I don’t know if this helps or not, but:

Falcon BMS is much better than DCS.

And the main reason: the attitude towards your creation.

DCS pursues wealth, whereas Falcon BMS pursues the Dream.

I am not writing how it must be, I am suggesting the best possible for the Falcon.

And the fact alone that the current camera design appears as a bug to a player raises some thoughts.

It is up to you to decide.

https://forum.falcon-bms.com/topic/23499/suggestion-remove-the-orbit-camera-position-and-zoom-reset

THE BUG

When reentering the VIEWEXT: Orbit Camera the Camera Zoom Level resets to it’s default value.

This also happens when changing Camera Zoom Level (VIEWEXT: Zoom In, VIEWEXT: Zoom Out) while in the VIEWEXT: Orbit Camera with enabled External Mouselook (Setup\Controllers\Advanced Options\View Control\Enable External Mouselook).

Upon reentering the VIEWEXT: Orbit Camera the Camera Zoom Level should be the same as it was when previously using the VIEWEXT: Orbit Camera.

THE BUG

Using NUMPAD keys to alter the Orbit Camera Position upon reentering the VIEWEXT: Orbit Camera the camera resets to it’s default position.

Upon reentering the VIEWEXT: Orbit Camera the camera should have the same position as it was when previously using the VIEWEXT: Orbit Camera.

NOTES

With enabled External Mouselook (Setup\Controllers\Advanced Options\View Control\Enable External Mouselook) after altering the Orbit Camera Position using the mouse and reentering the VIEWEXT: Orbit Camera the camera’s position doesn’t reset.

With enabled External Mouselook it is impossible to alter the Orbit Camera Position with the NUMPAD keys, however it is possible to alter the camera position with the NUMPAD keys while in the VIEWINT: Pan (3D) Cockpit view.

THE BUG

After launching an AIM-9M / AIM-120C missile a misplaced bright dot can be observed trailing the missile.

This bright dot changes it’s position relative to the missile as the missile alters it’s flight path to the target.

The farther the missile becomes from the F-16 the more the dot gravitates towards the center of the exhaust trail of the missile.

The bright dot disappears when the fuel in the missile is depleted, this leads to the conclusion that the Trail Dot is a misplaced part of the exhaust animation for the missile.

The Trail Dot can be observed from the VIEWINT: Pan (3D) Cockpit and from the VIEWEXT: Orbit Camera.

When observing the missile using the VIEWEXT: Weapon Camera the Trail Dot is absent, and the missile animation appears to function as intended.

GENERAL INFO

The bug was noticed during Instant Action \ Fighter Sweep gameplay.

Date: 24.10.2022

Falcon BMS Version: 4.36.3 (x64) 26590

https://i.postimg.cc/tJML95Qy/Trail-Dot.png

Need someone to check and confirm.

Hi!

During control configuration noticed that functions

CKPIT: Drop Chaff (non EWS AC)
CKPIT: Drop Flare (non EWS AC)

have the same functionality.

Both functions after activation dispense one flare and rounds of chaff.

Does it work as intended?

Falcon BMS 4.36.0 (x64) Build 26181

@Frederf said in Reassigning Q W E R T Y:

You’d have to open the .key file in Notepad and edit. It might be slightly delicate because the radio menus have lots of .key file entries for next page, previous page, sending stuff. But with care and liberal use of backups you can migrate it to another key. What key do you want to reassign it to?

I have reassigned the Wingman Menu to another key, it works properly, no problems so far.

@Frederf said in Reassigning Q W E R T Y:

You’d have to open the .key file in Notepad and edit. It might be slightly delicate because the radio menus have lots of .key file entries for next page, previous page, sending stuff. But with care and liberal use of backups you can migrate it to another key. What key do you want to reassign it to?

You mean if Wingman Menu is assigned to another key it will cause some kind of desync in other key bindings?

Managed to solve the problem with the help of the following information:

BMS Technical Manual Page 123 Paragraph 10.1.2

Non changeable keys example (Key file content / UI output):

SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -0 “REM: Hardcoded (not changeable)”

Changeable keys example (Key file content / UI output):
SimRadarElevationUp -1 0 0XFFFFFFFF 0 0 0 1 “TQS: ANT ELEV Knob - Tilt Up”

Solution steps:

1. Open a desirable .key file located in Falcon BMS\User\Config folder with a text editor.

2. Find in the opened .key file:

RadioAWACSCommand -1 0 0XFFFFFFFF 0 0 0 0 “RADIO: AWACS Menu”
RadioWingCommand -1 0 0XFFFFFFFF 0 0 0 0 “RADIO: Wingman Menu”
RadioElementCommand -1 0 0XFFFFFFFF 0 0 0 0 “RADIO: Element Menu”
RadioFlightCommand -1 0 0XFFFFFFFF 0 0 0 0 “RADIO: Flight Menu”
RadioTowerCommand -1 0 0XFFFFFFFF 0 0 0 0 “RADIO: ATC Menu”
RadioTankerCommand -1 0 0XFFFFFFFF 0 0 0 0 “RADIO: Other Agencies Menu”

3. Edit the lines to look like this:

RadioAWACSCommand -1 0 0XFFFFFFFF 0 0 0 1 “RADIO: AWACS Menu”
RadioWingCommand -1 0 0XFFFFFFFF 0 0 0 1 “RADIO: Wingman Menu”
RadioElementCommand -1 0 0XFFFFFFFF 0 0 0 1 “RADIO: Element Menu”
RadioFlightCommand -1 0 0XFFFFFFFF 0 0 0 1 “RADIO: Flight Menu”
RadioTowerCommand -1 0 0XFFFFFFFF 0 0 0 1 “RADIO: ATC Menu”
RadioTankerCommand -1 0 0XFFFFFFFF 0 0 0 1 “RADIO: Other Agencies Menu”

4. Save and overwrite the file.

5. Launch the simulator and reassign the Q W E R T Y.

IMPORTANT: the edited .key file must be loaded as a Current keyfile in order for this solution to work.

Thank you for the help.

This issue almost drove me away from Falcon BMS. Maybe this solution will help someone.