Another bunch of CTD's with F-4

[Miro]

I got another 3 Logs, can be useful. Can You tell me is F-4 fault? Or Kola map, or my end?

dcs.log-20240527-154308.zip dcs.log-20240529-173252.zip dcs.log-20240530-092315.zip

[Super Grover]

Thank you for your report. It's awesome that you included your logs - they make identifying the problems more manageable.

Only one of those crashes seems to come from the F-4E. It looks like a crash that is already fixed internally, and the fix should be available in the next DCS update.

One crash seems to come from SRS, but I don't know if SRS is the source or if it's just a coincidence. And the third one looks like a potential mod-related issue or a core DCS issue.

[aaronwhite]

3 hours ago, Super Grover said:

Thank you for your report. It's awesome that you included your logs - they make identifying the problems more manageable.

Only one of those crashes seems to come from the F-4E. It looks like a crash that is already fixed internally, and the fix should be available in the next DCS update.

One crash seems to come from SRS, but I don't know if SRS is the source or if it's just a coincidence. And the third one looks like a potential mod-related issue or a core DCS issue.

"fix should be available in the next DCS update" That's great news. Any information on what the crash pertains to? I've been documenting all of my crashes as best as I can, with the logs, but I haven't heard much back yet in terms of any information on what might be causing it.

Here's hoping my issue's included in the patch. I'm enjoying the F-4 and learning when I can, but the crashes have made it pretty tough to fly consistently, so I've had to shelve it for now. 

[Super Grover]

Oh, I'm sorry I didn't mention it previously. So, the crash from one of the logs was related to damage received after the cockpit part got disconnected from the rest of the aircraft (typically a total loss of control from the pilot being dead). An on-damage callback function tried accessing the cockpit state, assuming that the cockpit is always there. I know that it's not comforting, but you were about to crash anyway, just differently, and the crash to desktop at least made Jester suffer less. Nevertheless, that situation shouldn't have happened, but the code is fixed now.

TBH, given the complexity of the simulation and relations between different parts of the program, the number of crashes from the module is relatively low. I think I can enumerate most of them: the one above - this is the same one as here

, the crash which happens when the Jester overlay opens while the user is alt-tabbed out of DCS and DCS is running full screen (this is a peculiar one), some crashes related to waypoint creation from map markers, and when leaving the LAT/LON empty in Jester Wheel. All of them should be addressed in the upcoming patch.

The rest of the crashes reported seem to be from other parts of the ecosystem. A surprisingly high number of crashes look to be caused by mods, so if anyone experiences constant crashes, I'd advise removing all mods, making sure that there is nothing DCS-related in your Saved Games (you can make a backup and restore the files later), repairing DCS, maybe even repairing it again for good measure, and checking if it helps.

Edited May 30, 2024 by Super Grover

[aaronwhite]

Ha, funny you mention the complexity. I was watching the video for the radar back when that teaser was released and told my friend "This is all incredible, and I can't imagine the work that goes into doing it, but it's got to make sorting out bugs a real headache at times". 

For my crashes (Here's a link, since I forgot to mention it previously) I was noticing a similar issue with the error logs, but not entirely sure how to make heads or tails out of it, not to hijack this thread. 

I tried a few different things in the thread without much luck so far, but I'll keep an eye out for future patches.

[Super Grover]

I'm sorry that you experienced all those crashes. It's a bit of a busy time, but I know that every user report in this section is logged, and we will fix everything ASAP, assuming that the F-4E causes those errors.

[aaronwhite]

1 hour ago, Super Grover said:

I'm sorry that you experienced all those crashes. It's a bit of a busy time, but I know that every user report in this section is logged, and we will fix everything ASAP, assuming that the F-4E causes those errors.

Hey, no worries! Rome wasn't built in a day, and the digital F-4 wasn't either. It's the first time I've really had any crashing issues with DCS, fortunately, so it's just something I'll keep plugging away at until something I do fixes it, or a patch can, assuming it's related. 

I rolled back my GPU drivers just to see if maybe a recent update caused any issues. I'm going to hopefully get some flight time tonight and test it out. 

[SharpeXB]

Another one

dcs.log-20240531-030032.zip

[Super Grover]

22 minutes ago, SharpeXB said:

Another one

dcs.log-20240531-030032.zip 836.77 kB · 0 downloads

This one doesn't look Phantom-related, but the log is so cryptic that I don't know what it can be. We need to investigate it further.

[Miro]

i got another one today, it's F-4 related? My CTD's mostly occur after full startup procedure with F-4 and 30 min. of flying.

No mods, only using lights from mod which one ED adeed last time as part of DCS core, so it's DCS core.

Also mission file attached, it's kinda busy airbase.

dcs.log-20240531-092301.zip

Kola.miz

Edited May 31, 2024 by Miro

[Super Grover]

This one doesn't trace to any of our libraries - it happened in the rendering routines. Although it may indirectly relate to the F-4E, we have no tools to analyse it. Also, it may be completely unrelated to the F-4E. We will pass it to ED for you.