Cockpit display extraction
-
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.
-
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.
Please try the Harm Training Mission from 4.35 with HAD and TGP active and report back if you could run it without freezing as that Training TE is kind of a benchmark for the freeze
-
Please try the Harm Training Mission from 4.35 with HAD and TGP active and report back if you could run it without freezing as that Training TE is kind of a benchmark for the freeze
Oak - Just popped into the HARM TM, HAD running on RMFD, TGP on LMFD. Both were putting out constant data, could switch SOI back/forth. Only odd thing (I have never used the TGP with HAD before) was that the crosshairs did not move and were locked on the current SP. That normal?
-
Oak - Just popped into the HARM TM, HAD running on RMFD, TGP on LMFD. Both were putting out constant data, could switch SOI back/forth. Only odd thing (I have never used the TGP with HAD before) was that the crosshairs did not move and were locked on the current SP. That normal?
Fisrt of all lucky you that you don’t get a freeze. With the combination HAD TGP with TGP as SOI you need the TMS right in order to put TGP in area mode to be able to move the cursor
-
Fisrt of all lucky you that you don’t get a freeze. With the combination HAD TGP with TGP as SOI you need the TMS right in order to put TGP in area mode to be able to move the cursor
LOL, never been very lucky! Just ran again, still no freeze but I do know I need to RTFM on the HAD changes in symbols! While you are being so helpful, is there a way to have the TGP slew to the locked HAD target?
-
Please try the Harm Training Mission from 4.35 with HAD and TGP active and report back if you could run it without freezing as that Training TE is kind of a benchmark for the freeze
I do not fly training missions. Only custom TEs and campaign missions, but I tried HARM mission. It froze. Obviously that training mission is porked. Otherwise I have zero issues with MFDE.
-
I do not fly training missions. Only custom TEs and campaign missions, but I tried HARM mission. It froze. Obviously that training mission is porked. Otherwise I have zero issues with MFDE.
It’s not a porked Training TE, already confirmed by devs that it’s any issue within BMs itself. It’s just not as likely in TE or Campaign or not yet clear which circumstances lead to the freeze.
-
For me so far not as likely is never.
-
For what its worth Im getting freeze ups in training mission with no extraction. Soooooo:?:
-
For what its worth Im getting freeze ups in training mission with no extraction. Soooooo:?:
What do you mean with no extraction?
You don’t have no extraction tool running such as RTT Client, MFDE,Yame?If so you have still extraction running in the background as BMS is still writing the DED,MFD,HUD image data to the shared memory.
To turn of extraction in BMs you have to set in config set g_bExportRTTTextures 0
-
What do you mean with no extraction?
You don’t have no extraction tool running such as RTT Client, MFDE,Yame?If so you have still extraction running in the background as BMS is still writing the DED,MFD,HUD image data to the shared memory.
To turn of extraction in BMs you have to set in config set g_bExportRTTTextures 0
I think I’m aware of that.