[BUG FIXED] RTT Remote - Freezing
-
I jumped into the HARM training mission and within 5 min the MFD’s locked up. I tried it with just MFDE running and with the RTT client and it locked up within the 5 minutes in both cases.
I then did a 40 min. mission in a 4.35 campaign and had no MFD freeze up.
Are the training missions still 4.34?
-
-
Same problem for me !
-
Try using this parameter in your RTT .ini file RENDERER = 2 and try again . I recommend this utility from AlphaFox (Thanks!!!) [https://www.benchmarksims.org/forum/showthread.php?40725-F4-BMS-4-35-and-Disolay-extraction-with-RTTConfig
Note I dont obtain any freeze in Harm mission and Dogfight at the moment. :rofl::rofl:](https://www.benchmarksims.org/forum/showthread.php?40725-F4-BMS-4-35-and-Disolay-extraction-with-RTTConfig)
-
Try using this parameter in your RTT .ini file RENDERER = 2
Doesn’t change anything RTT same as other Extraction Tools reading from Shared Memory randomly freezing as the FalconTexturesSharedMemoryArea stops getting updated.
For the Harm mission I was able to have a longer non freeze time in the HARM Training mission if I don’t change the initial MFD Pages. But as soon as either HAD or TGP is selected the freeze is shortly after that
-
Ok, here is my RTT problem.
My setup 2x1920x1080 (main screen) and 2xmfd screens 800x600 on computer 1, Nvidia1070 8GB.
Second computer connected through network cable running RWR, RTT client.When is use 4.35 with RTT display and server sometimes after x minutes MFD screens freezes.
Also my main screen freezes, sometimes only MFD freeze. Sound continues but i have to ctrl,alt,del out.When is use 4.34 with the same RTT display an server (version delivered by 4.35 setup) screens do not freeze ! All works fine!
So i was thingking, maybe it is not RTT software but BMS4.35 related.For me now back to 4.34……
My 2 eurocents \martin
-
Sorry for my previous post, it seems that the behavior is very random, what I have been able to verify is that sometimes it works all the time well and others not. For example in the Instant Action mission of AA or in the mission of the Harm when a time passes it hangs regardless of changing from MFD to HAD, TGP, etc. At least that’s what I see, on the contrary in Dogfight its goes well.
PS: I do not see anything reflected in the error log since the simulator does not crash, it is only the extractions of the MFDs. -
Hi
Not sure if that is a real solution but since I have switched to the 32 bit version of RTT it has been working fine - approx 6-7 missions recently.
Also in another thread I found someone suggested to insert this line into falcon.cfg from 4.34 version - set g_bDoubleRTTResolution 1 . Might nothing to do with the issue and recent better behaviour but worth to try. /the lack of this in 4.35 may explain why RTT works well in 4.34 and not in 4.35/Cheers
-
Hi
Might nothing to do with the issue and recent better behaviour but worth to try. /the lack of this in 4.35 may explain why RTT works well in 4.34 and not in 4.35/Cheers
As I do a bit of development around Display exratction from my understanding g_bDoubleRTTResolution has no effect or impact in 4.35 at all.
I have taken 4 image snapshots directly from Shared Memory. These are the images the Extraction tools read and then split in order to Render MFD,RWR,DED(for DED/RWR only if image Rendering is used as F4Sharedmem also has a textual representation of those values)4.35 with g_bDoubleRTTResolution 1 in config
4.35 without g_bDoubleRTTResolution
4.34 with g_bDoubleRTTResolution 1
4.34 with g_bDoubleRTTResolution 0
as Expected the first 3 are identical with a resolution of 1200x1200 only the last one in 4.34 with 4.34 with g_bDoubleRTTResolution 0 is half the Resolution 600x600
So setting it in 4.35 as long as one of the Devs doesn’t correct me has no effect nor anything to do with RTT issues
Not sure if that is a real solution but since I have switched to the 32 bit version of RTT
Same issue with freezing, best tested with the Harm Training mission, turning on HAd and or TGP instant freeze
-
Dear Oak
You are right
It should have no effect and may be there isn’t at all
Most likely the 32bit RTT Client was the solution for me - or mere luck.
Still, another thread found this strange coincidence and seems to work for me. No harm trying.Cheers
Gekko
-
Guys,
It is a BMS issue… You can use as many 3rd party software as needed, that won’t change much…
The randomness of it makes diagnostic very hard but don’t worry, BMS teams are working on it.
For now, I would strongly suggest to turn RTT export off but you can still use your instruments displays using shared memory…
Cheers
-
I did a test and noticed that if I lose the focus of Falcon, for example by clicking on discord I regain fluidity.
I am using Helios extractions.
See my video. Maybe a lead for developers? -
Are you running in full screen mode? I have no export stutters when I set it to borderless (until the export freezes at some point).
-
set g_bDoubleRTTResolution
This option has been removed completely not only from the config, but also from the code. Hence it’s not doing anything in 4.35
-
Let me share my experience too.
I have the same problem no matter if i am running the RTT software or MFDE. When i am in a SEAD mission for example at EMF theatre after a period of time Falcon freezes, both image and sound. I have noticed that the problem has nothing to do with how much time you are in 3D but may has to do when you are sending callbacks in order to hand off a threat for example.
For my convenience i had copied all my setup from the previous version in order to be ready to fly without setting all things from the scratch.
I think that is the problem for my situation. I have putted all the vanilla files in the config folder and that’s it. I managed to be over 20 minutes in the cockpit and verify also that a frigate is able to hit my harms.
So everybody who have the same problem try this and let us know.
-
@Bad:
set g_bDoubleRTTResolution
This option has been removed completely not only from the config, but also from the code. Hence it’s not doing anything in 4.35
This config option certainly affects my install. See post #9 in this thread.
-
This config option certainly affects my install. See post #9 in this thread.
The only way set g_bDoubleRTTResolution could influence is if you had MFDE running in 4.34 running with g_bDoubleRTTResolution 0 resulting in a F4TexSharedMemory image size of 600x600 pixel and then running the same MFDE instance with 4.35 without having the MFDE config options openend and either use the Recover or Apply option or having the BMS Installation Folder in MFDE Performance advanced option still pointing to 4.34. All those would result in using MFDE user.config file in %appdata%/local/MFDEExtractor/Instance subfolder not beeing refreshed and therefore the behavior that MFDE working with wrong coordinates.
In none of those cases adding g_bDoubleRTTResolution to a 4.35 config would have any impactthis is the image MFDE reads from the Sharedmemory and with 4.34 the image could either be 600x600 or 1200x1200 depending on g_bDoubleRTTResolution
So it always includes the HUD and as i explained it’s MFDE reading from the wrong region but the fix for MFDE is NOT by adding g_bDoubleRTTResolution to 4.35 but to let MFDE update it’s user config while running 4.35 -
This post is deleted! -
-
In my case whenever i have this line (set g_bExportRTTTextures) equal with value “1” bms freezes no matter if i am running any extraction tool or not.
Everybody who still have problems try to fly without the export line enabled.