jfnelson0127

Hello, I purchased the Strike Eagle on release and have noticed significant performance issues when I fly it. I play almost exclusively single player on a curved monitor. Generally, I have pretty solid framerates in DCS regardless of aircraft. However, when I fly a single player mission in the Strike Eagle and then attempt to replay that mission, the second game will have unplayably low framerates. Oddly, if I jump to another aircraft and fly a mission and then come back to the Strike Eagle, playable framerates will return. Essentially, I can't fly missions in the Strike Eagle back-to-back and have to jump between aircraft. I do not seem to have this issue with other aircraft, just the Strike Eagle. Is this a known problem or is it unique to me? Are there any recommended fixes? PC details: DCS (multi-threading version) on Steam Windows 10 TrackIR v5 Installed on SSD Intel(R) Core(TM) i9-10850K CPU @ 3.60GHz Desktop Resolution: 3440 x 1440 @144mhz NVIDIA GeForce RTX 3080 - VRAM: 10 MB Driver Version: 536.40 64MB RAM I appreciate any insight you can offer! I have shared a screenshot of my current settings below. My Nvidia control panel settings are all default except for Negative LOD bias, which is set to "clamp". I have turned both vsync (in-game) and GSYNC in Nvidia controls on and off and it doesn't seem to have any impact on the problem. Thanks

First, let me say I love the update and the continued work to improve the Tomcat. However, what I assume to be attempts to simulate behavior really need to take a back seat to practicality and playabilty. With For example, I'd rather Jester snap the reticle to targets within the LANTIRN field of view instead of mindlessly "searching" in a circular pattern. I understand what you are trying to simulate, but it's eternally frustrating watching Jester circle the LANTIRN reticle around a column of tanks and never actually lock on to one. A real human RIO would easily spot those targets. Perhaps I'm doing something wrong. If so, please let me know how I can better leverage Jester. However, Spudknocker made a similar observation in his recent Jester video, and I have to agree. I'd love to be able to simply have him snap/track targets in his FOV. Yes. Looks like all of my binds are gone. Haven't checked to see if its simply a case of re-binding or if that function has been eliminated. My guess is its the former not the latter.

I'm also still having this same problem with the F-14. Several months now.

Is there a step-by-step for this process for Steam users?

Agree. I love this game and the Tomcat module in particular, but it looks like ED and HB are basically bouncing blame off of each other. The issue as persisted for months. It's really frustrating.

I'm also still having this problem. "- CTDs on respawn or mission reload occur far less frequently, but still occur. This is also an issue that cannot be fixed on our side." Looks like HB and ED are bouncing the blame off of each other? I don't see a solution in any of the threads that are being linked in response to these complaints.

Hello, I am, once again plagued by the 2nd-load crash in the F-14 nearly any time I try to "Fly Again" in a single mission. This happens in both missions I've designed myself in the editor, and with missions that are included with the F-14 module. The game seems to lock up at "1/100" during the loading phase. I am unable to share a crash log because I have to hard-kill DCS using the task manager, and I am not prompted to generate or send a crash log. I'm not running any mods, and I do not have any overclocking on my computer. I am deleting my fxo, logs, metashaders, MG, and Mission Editor files. I am also deleting the "DCS" folder in Local and the "DCS" folder in Local/Temp. I'm running Windows 21H1 and my Nvidia Driver is 466.47. Open to ideas. Thanks, JN

@Flappie I checked to be sure my Windows updates and Nvidia drivers were current. I attempted to fly an F-14 mission and received the same 2nd load crash with the new patch, updated drivers, and the latest Windows updates. I'm fine turning Windows 8 compatibility back on so that the game is playable at the very least. Unfortunately, I use SSAA 1.5, which now causes the clouds to clip the aircraft in game. On balance, this update is a pretty big step backwards for me. I'm pretty frustrated. I don't think my computer specs make me some sort of edge case, but maybe I'm wrong. Please see my latest crash logs attached. dcs.20210603-021453.log dcs.20210603-031742.log dcs.20210603-032317.log

Decided to take the game out of Windows 8 compatibility mode to see if the patch fixed the 2nd load crash. It didn't. See log attached. JN dcs.20210603-011939.log

Just do add my personal anecdote, this has been the same for me. The Windows 8 compatibility mode has fixed the 2nd load crashes in the Tomcat. I still get occasional crashes, but they are not consistent as they were before. HOWEVER, I have noticed that compatibility mode makes game shutdown take longer and causes what seems to be input lag in menus. Annoying, but I'll take it over the crashes. I hope ED is making some headway on an actual fix. The patchwork solutions are gratifying in the moment, but I think they may also instill complacency and allow permanent fixes to be pushed to the wayside. The underlying problems won't get solved if people quietly make due with bootstrap fixes. I can't think of another game where I've had to "clear my shaders and fxo" to keep it functioning. That seems like something we've had to do since 2.5 or before. Again, I love the game and appreciate the hard work that goes into it. Just hope we figure out the underlying issues.

Can you periodically delete the .dmp files in the CrashDump folder?

Are there any other distinguishing features of the files you're referencing aside from the date? I recently did a hardware update so all of my files are dated the same. What would the file names be?

I have been away on business for the last week. Figured I'd load up a mission in the Tomcat. The first mission played through fine, but the second load of the same mission crashed to desktop as it has been doing for the past month. Once again, I'm attaching my crash log. I noticed Steam completed a quick update for DCS when I started my computer. Clearly that update isn't addressing the 2nd load bug. Are there any new "fixes" that have been successful for others? Deleting fxo and the various DCS folders in Temp has done nothing to solve this for me. Thanks, JN dcs.20210516-015100.log

So basically, uncheck "disable fullscreen optimizations" in compatibility, and leave fullscreen disabled in the in-game settings. Am I understanding that correctly?

Howdy folks, Someone on the ED Facebook group mentioned a "Band-Aid" solution to the 2nd load crash that seems to be working for me, at least for the moment. After you finish the first mission, instead of clicking "Fly Again", exit all the way out to the main game menu, then click the "Options" tab where all of your settings can be found. Don't change any settings, but simply click the green "Okay" button. Then go back and fly the mission you want. Do this between each mission you fly. So far, going into options and clicking "Okay" between flights has stopped the crashes. It's super annoying to have to do this, and it's obviously not an actual solution, but it's better than crashing to the desktop. Let me know if this alleviates the problem for anyone else. Best, JN

I can also confirm that I was using Reshade and removed it assuming it was contributing to my 2.7 crashes. The removal did nothing. Second-load cashes continue.

I'm running the same driver and getting second load crashes.

Just "DCS" I believe. The executable is located in my "ThisPC>F Drive (my SSD)>SteamLibrary>steamapps>common>DCSWorld>bin

The crashes are constant now. I know I'm getting the "second load crash". I'm getting a bit frustrated because there doesn't really seem to be a remedy for this despite the fact that a pretty wide swath of users are suffering from the same problem. Deleting FXO and my local/temp DCS folders appears to be a fool's errand. I still get the crashes. Log attached. dcs.20210506-011607.log

Thanks Flappie. I don't have DCS.openbeta on my computer. Only DCS. I am running the openbeta however. Is this related to the fact that i'm using Steam?

Thanks Flappie! What's lost on me is how to fix the problem. These threads have become so extended that it's difficult to distill out what the solutions are. What can I be doing? I have tried deleting DCS through "User>AppData>Local>DCS" which has not worked for me. Oddly, I don't seem to have a "DCS.openbeta" folder, just "DCS". I assume this is because I use Steam. Regardless, the crashes have continued. One thing I notice is that the problem is happening mostly with the F-14 module. The F/A-18 seems to be tolerant of second loads. I saw there was talk of a "page file fix". Not sure exactly how that is done. Can you explain that procedure? There is also talk of exempting DCS from Windows Defender. Is there anything else I'm missing? See recent attached log. dcs.20210429-233413.log JN

I upgraded my processor and motherboard this evening. Crashes persist. My system specs: Nvidia GeForce 2080 (not overclocked) Driver 466.11 Intel Core i9-10850K (not overclocked) 32GB DDR4 3000 RAM 1920x1080, 144Hz Attached my log. Any ideas on a fix here? dcs.20210429-131941.log

This is still happening. The issue is really bad with the Tomcat. Latest crash logs attached. Both crashes on second mission load in the F-14. dcs.20210425-222508.log dcs.20210425-223200.log

I'm running the Steam version. Any idea where I would go to check for this file?

Howdy folks. Saw there was an update. Sadly this did nothing for me. Game still crashes to desktop on second load. Hope we are making headway on a fix. See attached log. No mods. No graphics card overclock. Thanks, JN dcs.20210424-030750.log