[BUG FIXED] RTT Remote - Freezing
-
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
-
Well to conclude my tests after 3hours of digging…
It happens on all blocks and quite fast on training missions HARM and GP Bomb with F-16CM-50…
Switching to A/G seems to help the freeze to occur but I cannot prove it…It happens with all tools actually reading the RTT export from BMS. shared data doesn’t seem to be affected since when I use MFDE to read only instruments, no freeze appears…
So as long as you don’t run any MFD extraction tool (RTT Remote or MFDE with MFDs) you’re pretty much not having the issue.We’ll see what the BMS team can reproduce, I have sent what I could to help for the investigation…
-
Hi.
Its also happening to me. Like you, I export MFDs, DED and RWR via RTTRemote Client and some other displays via MFDE. MFDE does not freeze, nor the displays in the main screen, but exported MFDs, DED and RWR do freeze.
I tried adding "set g_bDoubleRTTResolution 1 " but it didnt help -
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
-
As a follow up to my earlier post.
I tested in both a new 4.35 TE and a new 4.35 Campaign and didn’t have any freeze ups using just MFDE (no RTT client running) with the three recommended lines from Zipgun (noted above) in my config file. Or, if you run just RTT extraction only (no MFDE) say for the MFD’s and DED then no freezing.
If you run RTT and MFDE at the same time you get the freezes, which is what I (up to now) usually did. RTT for the MFD’s and DED and MFDE for the other gauges. (This was to deal with export issues when flying the Mirage awhile ago IIRC.)
I’m going to put in a few more flights to confirm.
I was flying F-16CM-52
-
I have put the RTTClient64.exe file to run with administration rights and everything works like a champ.
-
I have put the RTTClient64.exe file to run with administration rights and everything works like a champ.
To soon find out it is not the issue…
-
Placebo effect…
The real benchmark for which I constantly have locks-up is the HARM training mission… Stay there for 20 min straight without freeze and we’ll see.For me it is a Falcon BMS issue not an RTT Remote issue…
-
I can second MaxWaldorfs thought.
I have the same problem, best to find in the Harm training mission. When I restart BMS the ‘frozen’ RTT remote client will just reconnect and does its job, without the need of restart even.I have no special software running and just displaying left MFD.
Also I tried compatibility modes, etc, did not really helped.
Then I tried Razors lines wtihout success. Also tried to decrease updating interval by factor 10, no change.
Twice BMS froze completely 1s after HARM impact, using the RTT option on. Never happened however when I turnedit off in the BMS config file.also, we tried this in multiplayer, same mission. I was the server, and after 10mins I lost my display, my wingman however, also using rtt remote, had no issues.
-
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