Q-Ball

Seems like they could save a lot of heartache by appending the file once, rather than inserting at the beginning every time by default. I didn't change the code, just where in Exports.lua it appeared.

FWIW in the Radeon Software under Gaming, I only see the Steam games I have installed (assuming they are auto-detected). The DCS Standalone doesn't show up there, but it's possible that there could be separate settings for DCS if the player installed it from Steam.

I would concur with that assessment, since there was no noticeable change as I was moving things around aside from the WinWing bit.

Thanks, Flappie, that was very helpful info. I think I've got it sorted acceptably now. For whatever reason, re-ordering the Export.lua also results in the FPS increase (I made sure to disable the automatic SimAppPro updates to Export.lua). SimAppPro putting itself as the first item in the file looks to have down-stream effects, at least in my case. Further observation: It appears turning FreeSync back on introduces a slight penalty on the maximum FPS (5-6 FPS lower than without), but that's not entirely unexpected. Worth noting for other FreeSync users who have done similar troubleshooting. The real upshot here is that my FPS indicator with RIGHT CTRL + PAUSE now shows GPU-bound, instead of CPU-bound, and I'm seeing peak FPS on the test Instant Action mission in the mid-40s. Using the F-14 module for all these tests. For reference, I've attached my updated Export.lua with some added comments for clarity. Export.lua

Yep, that did it. FPS increased into the upper 40s/low 50s after renaming the file. So something in the Export.lua is causing it? BTW I do have WinWing devices, but I'm not sure that would be related if not mentioned in the Export.lua (or would it matter?)

Export.lua

It's off. I've also done a "factory reset" of Radeon settings. No change.

I hadn't checked my FPS performance in a while, but since MT hit Open Beta I wanted to see what sort of difference it made, and noticed that in-game, my FPS seems limited to 30, no matter the settings changes (Normally play 1440p/High preset, but I lowered to 1080p/Medium and still topped out at 30fps). I use a Vega 64 GPU with a FreeSync-capable display, but I have turned off all possible vsync settings (in-game, driver) and even went so far as to disable FreeSync on the monitor, but no change in behavior. When I run RIGHT CTRL+PAUSE, the fps will hit the limit of the monitor (65hz) in menus, but drop to ~30FPS in-game and stay there, unless it drops lower. In MT it says I am CPU-bound, but that does not seem correct, considering I have a Ryzen 7900XT. I feel like there's an in-game setting I am missing, but I am mystified as to what that might be. This thread suggested a few things in Graphics.lua, but there was no 30fps limit there: I have attached my dcs.log and dxdiag results to the post. DxDiag.txt dcs.log

Just got a Stream Deck and was experiencing laggy response as well. Set ExportScript.Config.ExportLowTickInterval = 0.5 and that fixed it. Thanks for taking a look at this!

I guess that settles the question of whether or not it should be a pushbutton. This is probably just something that fell through the cracks, then.

Hi, HB Team, I'm just starting to learn the RIO Pit after a long time in the front seat, and as I was going through the manual and binding buttons to my controls, I noticed that I cannot push the RIO's Master Caution button, although the manual suggests that it is supposed to be a button that can be pressed. A thread from around the EA release date mentions that this is a known issue, so I am wondering: Is the Master Caution light supposed to be a button as well? I have bound it to a key as a workaround, but having it as a clickable button would be very convenient, if it is supposed to be one.

I don't think the proposed fix solved the issue. We re-ran "In_Crash_We_Trust.miz" again last Friday and all but one Tomcat (out of six) crashed.

In the original mission, we did not use any AI. However this past Friday we created a mission (attached) specifically intended to force a crash of the clients. Tomcat AI, tankers, and two CVs. All four Tomcat pilots crashed (only my human RIO did not). This is in contrast to our previous test attempts, where at most we saw the crash of a single client. However, the first crash did not happen until about 45 minutes in. This seems like something that consistently happens later in a mission (in our experience), for whatever reason. I know you said that large track files are a pain, but I'm including what I have, in the hope that it's useful. Of course, none of the client crashes produce a track file. Server Track RIO Track In_Crash_We_Trust.miz

A bump on this and also linking to a thread over in the DCS 2.7 bug reporting with similar issues. I don't know if track files other than my own client file will be helpful, but we (my squadron) are happy to try to keep reproducing this and assist any way we can. However, we are not flying with F-14 AI.

Was this SP or MP? Edited to add: I am not sure I've ever run SP long enough recently to notice, but all of my problems with this freeze/crash behavior have been in MP.