Unfortunately, we don’t control WDP anymore…

Nothing I can do here…

OMG thank you , you guys are awesome

@riceygringo Love this little app! Thank you for creating it. 👍 One thing though & maybe I’ve missed a step…I still hear my breathing into the mic. Is this expected? Or did I miss something in the setup??

Disregard the mic issue. I somehow had 2 mic inputs. The Audio Input capture plus Mic/Aux. Muting the Mic/Aux solved my problems. 👍

I’ll add this in this Section. The F4Wx Thread is quite long and thought it might get lost. My hope is someone will find it useful. Thank you BMS community for everything 🍻

@Icarus

I’m using a laptop which has Win10. So, not updated to Win10.

Apparently it has something to do with something called “hardware acceleration”. No idea though what that even means…

A library to read and write Falcon BMS logbook files:
https://gitlab.com/hsleisink/falconbms-logbook

Hi,

I have set up my right and left MFD with RTT on my 1 screen running BMS and have it set on value 1 for screen overlay. I start RTT after launching Falcon. However, I like my MFD’s placed in the lower corners of the screen, and since they are set for overlay I cannot access the screen choices that lie underneath them. My question is, is there a way to “turn on and off” the RTT extracted MFDs while in the 3D environment only, so I interact with the 2D screen choices? I tried to set the overlay value to 0 but then when in the 3D environment I did not see anyway to turn them on.

Thank you for any assistance.

@Frysiek I use SemlerPDX’s AVCS4 Voice Attack programme, which he conspicuously doesn’t take credit for. Its great and he’s very helpful on Discord.

Sorry for the punt!

@VIPER-0 Yes, I’m aware of this. it contains the required headers.
As I mentioned, the SharedmemoryViewer under ./tools shows the correct data.
I am trying to use my existing C# reader to read data for my voice attack plugin.
It had worked for many years.
With the new version something got corrupt and I want to know if something had changed in the shared memory OSB classes.

@dunc I was told you might be able to assist.

@airtex2019 I’ve gone ahead and added functionality to the parser plugin to auto-populate the key file with the vJoy bindings that will ship with FoxVox v2.3 so you don’t have to mess with that and can focus on the bigger picture going forward. The plugin is easily configured to run after BMS starts by detecting the BMS version in shared mem, so it will update the key file after AL has already reset everything. I’ve tested that it works great and makes mapping callbacks to vJoy easy by placing them in a text file named vJoyBinds.ini located in the same config folder as the key file.

I’ll distribute the new FoxVoxParser.dll and default vJoyBinds.ini file as assets for a new library with the next FoxVox update.

If I’m changing theater, I will change to the new one in the drop down then restart WDP. Sometimes it still complains if you change it then immediately load a mission from the new campaign - though I think this has improved somewhat recently.

@suhkoi69 I have found a fix for this. You need to change the order in your theater.lst file (BMS\Data\TerrData\TheaterDefinition) and place ITO above ITO80’s, then save and open MC. When you open BMS this unfortunately gets reverted, however, if you open MC and load the campaign/te beforehand, this is not an issue.

What compass are you referring to? In Helios there is an EHSI gauge that gets its data from BMS SharedMemory.

I had a compass I created in Helios from a custom gauge in a Hornet profile I had, as the Hornet does have a floating compass on the right eyebrow. Is that what you are looking for?

@Falcas is it possible to enhance Weather Commander in including the automatic calculation of fog altitude as it is done in BMS ?

@airtex2019 it’s a good idea, but at the end of the day I would rather just assign the drive letter and forget about it. I don’t actually like scripting things like this (Drive letters, or batch files for configuration of monitors and software) I prefer to spend my time doing other things.

It’s just that when I added in the voice recognition software, starting everything up reached a pain point I wasn’t willing to tolerate and it was keeping me out of the sim.

Nevermind, its working in the meantime.

@Voynut said in RTT HUD Mirror Flip or MFDE fix:

@Sneakpeek Not really. Still running it on the mfd extractor.

Hi there, thanks for the response.

I’ve found the following software, which is meant for the Raspberry PI: https://github.com/johndcollins/RTTClient.
As far as I could see, it already brings the capability, to flip the images (didn’t try it, thogh). On Linux, it’s also not that necessary, as you could easily do that on the OS side.
All in all, it also brought the capability to move the windows. Looked quite nice.

I’ve almost managed to get it to compile on Windows, but I’ll try to put together a small app myself.

All other solutions weren’t satisfactory. I’ve stumbled across some programs, like Ultramon, that would be able to mirror flip a screen, but only with a lot of effort and fiddling on the user side.

On the other hand - @Dunc: Is the RTTClient still actively maintained? If so, I’d kindly like to ask, whether it’s possible to extend it with the capability to mirror flip (not rotate) the HUD image horizontically?
From the users perspective, I’d suppose that this would be the best solution - of course I’d understand if it didn’t come to be.

Cheers,
SP

@Falcas could you please check if the Offset angle is correctly calculated ?

to respect the key points following:

climb & dive angle (20° & 15°) release height (2000ft) speed 500cas G 3.5 Angle off 40

It is impossible to obtain an Offset Angle equal to 25.5°

after drawing a schematic on paper, I checked that the Offset Angle is lower than 25.5°, and I found 17°

AOD is correctly calculated : AOD = (release altitude/tan [dive angle]) - bomb range = 2000/tan (15 degrees) - 4902=2562ft

MAP distance = bomb range + tracking distance with :
Bomb range = 4902 feet
Tracking distance = 1.69 x GS x tracking time
MAP Distance = 1.69 x 500 x 5 = 4225ft ~ 0.7 nm
text alternatif

Vertical tracking distance = 513 x sin (15 degrees) x 1.69 x 5 = 1121 feet

Track point altitude = pickle altitude + vertical tracking distance = 2000 + 1121 = 3121 feet

Apex altitude = track point altitude + (dive angle x 50)
Apex altitude = 3121 feet + (15 x 50) = 3,137 + 750 = 3871 feet = Approximately 3,900 feet

Pull-down altitude = Apex altitude - (climb angle x 50) = 3871 - (20 x 50) = 2872 feet -> correct

Pop-to-pull-down distance = (Apex Altitude (AGL) x 60)/Climb Angle = 3871 x 60/20 = 11613~1.9nm

Possibly I am working on this project unnecessarily as indicated in this text in red of the BMS technical manual page 3-12 which states:

“Note: This chapter will be completely overhauled for either 4.37.x or 4.38.0. Also, the file structure will change dramatically. However, most info is still valid.”

Nevertheless, I am continuing the work. This tool will be available soon for Falcon BMS 4.37.2, but it will probably no longer be relevant in the next simulator update…