[BUG FIXED] RTT Remote - Freezing
-
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
-
-
It really makes me sad having 4.35 out and no extraction working. It makes me prefer the previous version as long it is not fixed. And yes, I am just writing this to make some noise (see https://bmsbugs.blu3wolf.com/view.php?id=4)
-
Well … I don’t know what did he fix… really…
What I mean by that, it wasn’t broken for me. shared mem/tex extraction never froze for me.
Flew already ~4 hrs in sp campaign mode with “Falcon MFD for android”, and only that one ctd I refer 2 posts above.
-(while I activated NVG with antialiasing via game, now rather via profile… no single ctd after, I was also using undervolting for graphics card - so no 100% guaranties , but Cyberpunk never crashed for me!!! - oh am I too good with my system configuration LOL)I am also using opentrack, voice-attack, winamp , - along with “MFD server” and client on android tablet via usb cable (lan/wan tethering)
set g_bExportRTTTextures 1 // This enables the shared texture memory area for HUD/MFDs/HMS/RWR/DED/PFL set g_nRTTExportBatchSize 1 // This determines how often the shared texture memory area (if it is enabled) will be updated (every Nth frame, default/min is 2)
This is all what I have in cfg … tex extract never froze on any of mfd pages I have used ,… FCR, HSD, FLIR , TFR , WPN - mav/harm(has) … RWR
Good Luck sir
-
FWIW,
using MFDE 0.6.3 by Lightning,
initially no gauge displays - fixed by editing config as per post re RTT.
freeze after 10 mins - complete freeze. had to ctrl alt del to get out.Went to Nvidia 3d settings and set for maximum performance.
- two exercises in EMF and KTO gauges working, no issues.
-
FWIW,
Just flown a multiplayer mission with all gauges working. no issues, other than my poor flying… -
FWIW,
Just flown a multiplayer mission with all gauges working. no issues, other than my poor flying…No need to update with mission success, the bug has been approved by the devs and fixed for the next upcoming update. Just be aware you might be lucky and fly consecutive mission without hitting the bug. I personally don’t hit it in every mission as well but it’s existing and confirmed by a number of display Extraction tools user
-
Huh, well yeah, probably. …but, we’re not talking about some variable thing eg. ATM/GTM unit flag in campaign, so once it happens and ctd , but other 999 times is a pass.
It is about texExtraction which is or enabled and working , or it is disabled and not working. So how come that it works on “few” systems and freezes on all others… (not that there are much more of them, I count about maybe 10-20 )
Well I guess it is to be expected with “bugs bunny’s” - you never know what are you going to get
-
Guys, let me try to stop all rumors
There were 2 issues as part of this RTT problem:
1. RTT export itself would freeze
2. BMS itself would freeze and potentially CTDThe BMS freeze was a problem of the RTT export code causing a sync problem with the GFX engine. In short details - The DX11 device context isn’t thread safe in general (i.e you can’t use the immediate context object from other threads), and in this case while the engine was executing draw commands on other threads, the RTT code was using it without the necessary safety. That caused a corruption of the context which eventually led in many cases to a freeze or a crash.
FWIW, I tried to reproduce the problem on my system a couple of times but couldn’t, so it must be luck or randomness or whatever, but for sure the problem is valid and hence was fixed (Both issues needed a fix).
-
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
This is good information, but could someone provide a link for this newer version of the (same#) 0.6.3.0 MFDE? I seem to have a very hard time finding it! ( 99% chance it is my incompetence, but nevertheless, a link would help!)
-
This is good information, but could someone provide a link for this newer version of the (same#) 0.6.3.0 MFDE? I seem to have a very hard time finding it! ( 99% chance it is my incompetence, but nevertheless, a link would help!)
Here you go
Greetings Martin
-
Here you go
Greetings Martin
That version looks the same as the old version mentioned by oakdesign to me. It’s got an option for MFD 3 & 4
-
You either have to build it on your own from the source on git or
That’s my version build from the source. It is without installer so unzip and run the exe with administrative rights. No need to deinstall the older version
https://drive.google.com/file/d/177VhX_kTKOSL9vjobD7fzHGk2GupigrP/view?usp=sharing -
Guys, let me try to stop all rumors
There were 2 issues as part of this RTT problem:
1. RTT export itself would freeze
2. BMS itself would freeze and potentially CTDThe BMS freeze was a problem of the RTT export code causing a sync problem with the GFX engine. In short details - The DX11 device context isn’t thread safe in general (i.e you can’t use the immediate context object from other threads), and in this case while the engine was executing draw commands on other threads, the RTT code was using it without the necessary safety. That caused a corruption of the context which eventually led in many cases to a freeze or a crash.
FWIW, I tried to reproduce the problem on my system a couple of times but couldn’t, so it must be luck or randomness or whatever, but for sure the problem is valid and hence was fixed (Both issues needed a fix).
Hello I-Hawk,
I am tired of all the rumors posted here.
Do you have any home remedy for this issue until a patch is released.
I really like the concept of RTT but it freezes all the time after a few minutes.
Please help.Thanks,
-
Until the update is released the only remedy is to disable RTT export in the Falcon BMS.cfg file by changing the 1 to a 0.
-
We use 4.34 U4 until 4.35 U1 is released.
Hopefully it won’t be long until U1, I’d even be happy if it comes with just that fix and a few others (like the tanker).