Cockpit display extraction
-
Hello Guys
First I would like to thank to BMS team for this X-mas gift.
But I have also a Question regarding cockpit display extraction.
I’m actually working with two screens and one above another .
Secondary monitor was only for MFD RWR and DED like in 4.34 to manage from CDE.
Is there any explanation how to set up again on secondary monitor all this stuff : HUD ,MFD’s RWR DED?
Or somewhere in manual how to do this.Tnx in advance.
-
Hello Guys
First I would like to thank to BMS team for this X-mas gift.
But I have also a Question regarding cockpit display extraction.
I’m actually working with two screens and one above another .
Secondary monitor was only for MFD RWR and DED like in 4.34 to manage from CDE.
Is there any explanation how to set up again on secondary monitor all this stuff : HUD ,MFD’s RWR DED?
Or somewhere in manual how to do this. Tnx in advance.you need to use RTT now for Extracting MFD RWR and DED. It’s located in your Falcon BMS 4.35/Tools/RTTRemote folder. In your case just use the RTTClient.exe All the positioning is done in the RTTClient.ini file
-
Hello Guys
First I would like to thank to BMS team for this X-mas gift.
But I have also a Question regarding cockpit display extraction.
I’m actually working with two screens and one above another .
Secondary monitor was only for MFD RWR and DED like in 4.34 to manage from CDE.
Is there any explanation how to set up again on secondary monitor all this stuff : HUD ,MFD’s RWR DED?
Or somewhere in manual how to do this. Tnx in advance.You Must to use RTT remote like Oakdesign said … But notice that your FPS of your exportation is now BMS FPS/2 … So if you fly with 60fps in your main screen, the exportation will show 30fps !
Cockpit Display Extraction was better than RTT ! So sad …
-
There is a modified version of MFDE out there, that is working with 4.35. Maybe oakdesign has heard of it
At least until BMS stops to deliver data. If that happens RTT and MFDE are lost. -
There is a modified version of MFDE out there, that is working with 4.35. Maybe oakdesign has heard of it
At least until BMS stops to deliver data. If that happens RTT and MFDE are lost.Hi, Razor,
I’ve flown 4.35 and without any tweaking on my part MFDE is working, except that the MFD’s don’t show up. What do you get when you try it?
Joe -
Cockpit Display Extraction was better …
But had to be removed due to DX11 conversion.
In the past (and in theory now) RTT is much more performant than the old stuff.
But, it seems to have it’s difficulties atm. which for sure will change.
Don’t give up! -
I use only MFDE for it and I get both MFDs, altimeter, speed meter, ADI, VSI, AOA, DED, fuel, RPM, RWR, trim and gear. I don’t have more space on the other screen
-
But had to be removed due to DX11 conversion.
In the past (and in theory now) RTT is much more performant than the old stuff.
But, it seems to have it’s difficulties atm. which for sure will change.
Don’t give up!I hope you’re right ! It’s sad to see my screen just with 30fps …
-
Hello Guys
Tnx for your explanations I appreciated lot.But to explain for those who knowledge about programming is not well.
Ok so you start RTTclient.exe and you will see on to your primary monitor two windows open one small one bigger with some circles and orange X.
To get those windows on to your secondary monitor you need to do some steps.Go to C:/Falcon BMS 4.35/Tools/RTTRemote/RTTClient.ini
Open this wit note and go to or find :# Which RTT displays do you want to show on the client side?
USE_HUD = 0
So if you want to have them all (RWR ,DED) just change 0 to 1 and they will be now all able to work.
Next step in same file is to decide your position on to your secondary monitor:
Go to the bottom of the script and you will find this:
HUD_X = 1595
HUD_Y = 2613
HUD_W = 656
HUD_H = 638
HUD_ONTOP = 0Then in the X,Y,W,H = you need to decide what is position of Window HUD or MFD on to your secondary monitor.
If you don’t know how ? like me then you can use maybe your old BMS 4.34 and then go to Cockpit Display extraction and open it.
There you can find your old settings.If you been work before with CDE?Ok we take example HUD and you will see “Adjust window rectangle”
Left:
Top:
Width
HeightIn our situation 4.35 this is:
X=
Y=
W=
H=Now you can use your positions like you use before in 4.34.
Now you can start your 4.35 and go to 3D you will see that all your desired windows are in secondary monitor.
On the good positions if not you have to go back and correct them. I can’t find out to move them with mouse like in old CDE to make fine tuning. So every time you have to go out ant to make small changes in to your RTTClient.ini file.
Now we can go in to 3D you are in the cockpit but all your windows are black no output from your MFD or HUD in to them. Ok no problem go out and go then in to your
Go to C:/Falcon BMS 4.35/user/falcon bms.cfg and search for this :
set g_bExportRTTTextures 0 change 0 to 1.
Now again in the 3D and you will have all windows working.To BMS Team:
I don’t know or I can’t find way to move windows to desired position like in CDE just to put mouse on it and with left click set them on the right position.
Another issue what I Manage is that @__rafalejab__ maybe meant is that for example on my secondary monitor cursor on left MFD in radar mode move very slowly and in the same moment looking on the primary monitor in the cockpit moves exactly fast?
That make for me in the combat situation difficult where the time of reaction to lock the target is in milliseconds.
Best Regards -
First of all a very big thank you to the BMS team, its great what you are doing in your free time. Please keep going on.
I have 2 extra monitors for the mfds with thrustmaster mfd frames ontop and i fond a solution for adjusting the screens.
1. Go to you driver screen setup. I m using a nvidia card, while dragging the positions of the additional screens i fond out the x and y coordinates of them.
2. Put these coordinates into the rttclient.ini file as 117LAP wrote, add width, height and ontop lines for the left mfd and run the rttclient.exe.
3. Adjust the values until they are matching the trustmaster frames.For me it was a 5 minutes job.
-
I’m using YAME64 for the gauges and RTT for the MFDs. Works like a charm until RTT freezes up, but I hope a solution for this problem will be found sooner rather than later.
All the best,
Uwe
-
I’m using YAME64 for the gauges and RTT for the MFDs. Works like a charm until RTT freezes up, but I hope a solution for this problem will be found sooner rather than later.
All the best,
Uwe
I’m running the same Uwe, no freezes anymore. You don’t have Yame still outputting to the MFDs do you? I did by accident and had CTDs, all good now! Also selected DX11 (RENDERER = 2) in the RTTClient.ini config instead of “0” to pick automatically, no idea if that helps or not.
-
For MFD extraction it doesnt matter which Tool used all RTT, Yame and MFDE will suffer from freezing up as it’s not the tools failing to read but BMS failing to write to the F4TexSharedMemoryArea
-
For MFD extraction it doesnt matter which Tool used all RTT, Yame and MFDE will suffer from freezing up as it’s not the tools failing to read but BMS failing to write to the F4TexSharedMemoryArea
Weird. I haven’t had any freezing up with MFDE after 6-8 hours of flight. So far works like it did in 4.34.
-
Good Day, All
I don’t know if this helps anyone, but…
I was getting sporadic ctd’s while using MFDE, as in 4.34, with MFD’s. As they weren’t displaying data anyway, I turned them off, and I’ve done 2 missions with no CTD’s -
For MFD extraction it doesnt matter which Tool used all RTT, Yame and MFDE will suffer from freezing up as it’s not the tools failing to read but BMS failing to write to the F4TexSharedMemoryArea
Hi, Oak,
I took your post in a “BMS can’t keep up” kind of way, so I removed all but bare minimums ( in my case I just have RWR,fuel flow, trim panels and Hyd A and B.) Since then I haven’t had CTD’s. Yet -
Hi, Oak,
I took your post in a “BMS can’t keep up” kind of way, so I removed all but bare minimums ( in my case I just have RWR,fuel flow, trim panels and Hyd A and B.) Since then I haven’t had CTD’s. YetThese gauges don’t read from F4TexSharedMemoryArea but from F4SharedMemory which is another datastructure and memory adress area and doesn’t cause any conflict. And F4SharedMemory in contrast to F4TexSharedMemoryArea.
By the way BMS will always write to F4SharedMemory there is not even a config option to turn that off. Only BMS writing the F4TexSharedMemoryArea can be turned of by setting g_bExportRTTTextures 0 -
I made sure to delete the MFDEs from YAME64’s setup and I’m only using it to read the F4SharedMemory stuff as outlined by oak above. RTTClient (non-networked) is used for the MFDs.
All the best,
Uwe
-
https://bmsbugs.blu3wolf.com/view.php?id=4
All the best, Uwe
-
I am Extracting mfds with MFDE. I do not have any crashes or freezes at all. Maybe it is RTT client because it’s not shared memory because it is working for me just fine.