[BUG FIXED] RTT Remote - Freezing
-
After several tests I think that I have a solution for my problem at least.
In my opinion i think that in many PCs (including mine) the imaging shared memory can not be handled and this is why the RTT and the game freezes. Even if you edit your Falcon Bms config in order to export the mfds for example when the game feels that this is not possible then crashes the RTT or the game generally. This can be spotted in the User file. When the sim feels that bug then it’s changes by itself the falcon bms.cfg file. The odd thing that I have noticed is that next to these lines “set g_bExportRTTTextures” “set g_nRTTExportBatchSize” the description is missing and the file is obviously unintended changed.
In order to help the sim to deal with the image shared memory i limited the fps in the RTTClient.ini to 20 and I changed the “set g_nRTTExportBatchSize” to 5. Now the exported MFDs have slowest update but they do their job without crashing at all even in a harm mission. Generally i think that the thing the thing that stresses the sim is the quick change of MFDs pages or the TGP image.
All the above are just thoughts and for now for me at least is a solution.
Note that i use the RTTclient x32 with admin rights and in the RTTClient.ini I have also set the RENDER = 2 as suggested above.
That’s all for now. Merry christmas!!!
-
Great finding,
as I have run and tested all Dsiplay Extraction tools always with g_nRTTExportBatchSize 1 so basically in sync with the game FPS I went in 4.35 up only to g_nRTTExportBatchSize 2 as my thinking was:
if the issue is a BMS internal timing with the shared tey memory setting it to half the FPS should be enough.
Apparently not.
I went with a g_nRTTExportBatchSize 10 and was able to have both TGP and HAD on in the Harm Training TE without freezing External MFD.
So now to test how low I can go.Edit: Setting higher g_nRTTExportBatchSize just prolongs the time until a freeze might occur but still occurs
-
Because the problem is within BMS….
-
As promised, a short video demonstrating how the “set g_bDoubleRTTResolution” option will disable, or enable display extraction. On my machine at least.
Apologies for the quality, it was my first attempt at recording video.
-
@oakdesing try to set the antilising setting to lower value. My setting is 2
-
Gents,
Try as much voodoo stuff as you like but as long as an update fixing the code issue is not published, you won’t have a proper fix…
Cheers
-
As promised, a short video demonstrating how the “set g_bDoubleRTTResolution” option will disable, or enable display extraction. On my machine at least.
Apologies for the quality, it was my first attempt at recording video.
Ok now I see. You are using MFDE 0.6.3.0 compiled before August 6 2019 which still reads the g_bDoubleRTTResolution value from the BMS config in order to determine the coordinates. So with your version g_bDoubleRTTResolution 0 assumes to image size rendered by shared memory to be 600x600 or g_bDoubleRTTResolution 1 to be 1200x1200.
With the latest commit as of August 2019 this has removed from MFDE and even MFDE doesn’t use that parameter anymore calculates the RTT areas directly from the values from the shared memorycommit message from latest release
…
-use RTT coordinates from sharedmem (not from config)Most obvious visaul difference to see which version of MFDE is in use
old has still has option for MFD #3 and #4newer one has those removed as well as not relying on g_bDoubleRTTResolution at all
-
@oakdesing try to set the antilising setting to lower value. My setting is 2
1. it’s already clear that there is no workaround without BMS code fix
2. changing antialiasing doesn’t make technically any sense as it would have no impact in sharedmemory data writing -
1. it’s already clear that there is no workaround without BMS code fix
2. changing antialiasing doesn’t make technically any sense as it would have no impact in sharedmemory data writingAfter one hour in the 3d I had a freeze again. So guys you are right but it was worth digging the problem to the bone.
-
Ok now I see. You are using MFDE 0.6.3.0 compiled before August 6 2019 which still reads the g_bDoubleRTTResolution value from the BMS config in order to determine the coordinates. So with your version g_bDoubleRTTResolution 0 assumes to image size rendered by shared memory to be 600x600 or g_bDoubleRTTResolution 1 to be 1200x1200.
With the latest commit as of August 2019 this has removed from MFDE and even MFDE doesn’t use that parameter anymore calculates the RTT areas directly from the values from the shared memoryMost obvious visaul difference to see which version of MFDE is in use
old has still has option for MFD #3 and #4newer one has those removed as well as not relying on g_bDoubleRTTResolution at all
I had no idea there was another version of MFDE available. At least that explains what I was seeing.
-
I just did another testing flight and neither RTT nor komurcu’s app froze for me during this flight (same TE as used above). I know this doesn’t exactly make debugging this issue easier, I’m just adding data points
All the best,
Uwe
EDIT: Using blk52s for what it’s worth
I have the same Issue and in my case I am using Komurcu app. I configured RTT based on: https://www.benchmarksims.org/forum/…l=1#post557243. Also, I used F16 CM-40 and flight a Harm attack and after 10 minutes everything went freeze. Once the FalconMFDServer ( the Ap that works as a server to manage the MFDs) was closed by the system. I read several potential solutions but I understood that no one is conclusive and we should wait the coming of the BMS team with a solution. Am I right?
-
Yes you are correct. You have to wait for an update. All current available tools for MFD display extraction use the same underlying technique to read the MFD Data and as it’s BMS itself that stops providing the data none of the tools using the shared memory can do anything to fix it
Gesendet von meinem SM-G930F mit Tapatalk
-
Thanks for your input.
A clear message and thus we avoid being each one of us going around making a mess in our BMS.
-
It’s a bug. Turn off RTT export in your BMS config and enjoy hours a fun without freezes
-
It’s a bug. Turn off RTT export in your BMS config and enjoy hours a fun without freezes
Lol. We spend a lot of money and time in order to install different system for show the MFD on different screen ! And a lot of people have cockpit … it’s very sad to turn off the exportation of MFD
-
Lol. We spend a lot of money and time in order to install different system for show the MFD on different screen ! And a lot of people have cockpit … it’s very sad to turn off the exportation of MFD
Bugs can be fixed
-
Lol. We spend a lot of money and time in order to install different system for show the MFD on different screen ! And a lot of people have cockpit … it’s very sad to turn off the exportation of MFD
Just wait for U1 and have fun with 4.34 in the meantime. There’s nothing we can do until then, and it won’t last long for sure.
-
https://bmsbugs.blu3wolf.com/view.php?id=4
All the best, Uwe
-
It’s not only RTT, MFD extractor and also komurcu’s app freeze when this happens, so I’d suspect it’s a problem within BMS and not specifically with RTT.
All the best,
Uwe
Bingo!!!
I 've had one of those crashes … no log , pure CTD. Solved it by turning OFF antialising in the game and forced (AA and AF) via driver profile … no more CTD… for me.
-only thing “game” controls is VSYNC (also, app controlled and default enabled in driver profile) and TripleBuffering (if you use vsync) - but I run fullscreen … other cases may vary
-