solved NS 430 Still Causing CTD

[Daemoc]

As per title. No mods.

I have been testing the NS 430 since the update today and it has been still acting up.

The first flight I was using the Persian Gulf map, about a 30 minute flight with 5 waypoints. Frame times would spike to over 500ms about every 30 seconds or so. I kept playing with the terrain mode and if finally quit. Made it through the flight.

The second flight was Nevada with 8 waypoints that was supposed to be a 45 minute flight.

The frametime issue never came up this time, but I had a CTD about 8 minutes in. Just as I was going to hit waypoint 2.

When it crashed, Steam and the DCS crash window started fighting each other. (this has never happened before) I had to end task via task manager to get control of my computer again so I did not get the crash log. I do have the video though if you think it would help?

I will try to get this to crash again and attach logs/tracks. I just wanted to give you the heads up and see if anyone else has experienced any issues.

 

Also, the terrain view is still all black until I change the range setting. I will have terrain color until I takeoff then it goes black again for some reason. I noticed I changed the range from 10nm to 5nm about 5 mins before I hit waypoint 2 and the terrain color came back for a second. Maybe this caused the crash?

 

[Flappie]

Hi @Daemoc. You should still have the zip files from your crashes in your Logs folder. Can you please attach them?

[Daemoc]

Sorry for the late reply, I have been been super busy.

I have been doing a lot of testing, and I think I fixed it with a shader wipe. I have not had the issue since.

[Flappie]

Good! Thanks for your feedback.

[evanf117]

On 5/25/2024 at 3:29 AM, Flappie said:

Good! Thanks for your feedback.

i believe my CTD's as of late are caused by it
dcs.log-20241002-180442.zipdcs.log-20240928-053606.zipdcs.log-20240927-130747.zip

[Flappie]

2 hours ago, evanf117 said:

i believe my CTD's as of late are caused by it

Yes, indeed. "jsAvionics" points to the NS430 module.

There are tracks in your zip files, which is a good thing. I'll see if I can reproduce these crashes.

2024-10-02 18:04:41.713 INFO    EDCORE (Main): try to write dump information
2024-10-02 18:04:42.339 INFO    EDCORE (Main): # -------------- 20241002-180442 --------------
2024-10-02 18:04:42.339 INFO    EDCORE (Main): DCS/2.9.8.1107 (x86_64; MT; Windows NT 10.0.19045)
2024-10-02 18:04:42.340 INFO    EDCORE (Main): E:\DCS World OpenBeta\CoreMods\services\jsAvionics\bin\jsAvionics.dll
2024-10-02 18:04:42.341 INFO    EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ffcc6a94dea 00:00000000
2024-10-02 18:04:42.390 INFO    EDCORE (Main): SymInit: Symbol-SearchPath: 'E:\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'dyeva'
2024-10-02 18:04:42.390 INFO    EDCORE (Main): OS-Version: 10.0.19045 () 0x100-0x1
2024-10-02 18:04:42.392 INFO    EDCORE (Main): 0x0000000000034dea (jsAvionics): ed_on_mission_pre_start + 0x4C6A
2024-10-02 18:04:42.392 INFO    EDCORE (Main): 0x000000000003534b (jsAvionics): ed_on_mission_pre_start + 0x51CB
2024-10-02 18:04:42.393 INFO    EDCORE (Main): 0x00000000000bf800 (jsAvionics): simSdk_UpdateServer + 0x71510
2024-10-02 18:04:42.393 INFO    EDCORE (Main): 0x00000000000b6515 (jsAvionics): simSdk_UpdateServer + 0x68225
2024-10-02 18:04:42.393 INFO    EDCORE (Main): 0x00000000000b7691 (jsAvionics): simSdk_UpdateServer + 0x693A1
2024-10-02 18:04:42.393 INFO    EDCORE (Main): 0x00000000000717c0 (jsAvionics): simSdk_UpdateServer + 0x234D0
2024-10-02 18:04:42.394 INFO    EDCORE (Main): 0x000000000007180a (jsAvionics): simSdk_UpdateServer + 0x2351A
2024-10-02 18:04:42.394 WARNING LOG (16956): 2 duplicate message(s) skipped.
2024-10-02 18:04:42.394 INFO    EDCORE (Main): 0x0000000000074f59 (jsAvionics): simSdk_UpdateServer + 0x26C69
2024-10-02 18:04:42.394 INFO    EDCORE (Main): 0x0000000000014ed2 (NS430): cockpit::G430::avGNS430::release + 0x862
2024-10-02 18:04:42.394 INFO    EDCORE (Main): 0x000000000021f69e (CockpitBase): cockpit::avDevice_BasicTimer::NextEvent + 0x1E
2024-10-02 18:04:42.394 INFO    EDCORE (Main): 0x00000000000045eb (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x3EB
2024-10-02 18:04:42.394 INFO    EDCORE (Main): 0x0000000000004c12 (World): wSimCalendar::DoActionsUntil + 0x262
2024-10-02 18:04:42.394 INFO    EDCORE (Main): 0x000000000090cfca (DCS): SW + 0x421F5A
2024-10-02 18:04:42.394 INFO    EDCORE (Main): 0x000000000090cca1 (DCS): SW + 0x421C31
2024-10-02 18:04:42.395 INFO    EDCORE (Main): 0x00000000009325c2 (DCS): SW + 0x447552
2024-10-02 18:04:42.395 INFO    EDCORE (Main): 0x00000000008ecb14 (DCS): SW + 0x401AA4
2024-10-02 18:04:42.395 INFO    EDCORE (Main): 0x00000000008ee243 (DCS): SW + 0x4031D3
2024-10-02 18:04:42.395 INFO    EDCORE (Main): 0x00000000022b5c64 (DCS): AmdPowerXpressRequestHighPerformance + 0x1227C60
2024-10-02 18:04:42.395 INFO    EDCORE (Main): 0x0000000000ccde52 (DCS): SW + 0x7E2DE2
2024-10-02 18:04:42.395 INFO    EDCORE (Main): 0x0000000000017374 (KERNEL32): BaseThreadInitThunk + 0x14
2024-10-02 18:04:44.379 INFO    EDCORE (Main): Minidump created.

 

[Flappie]

I've just tried all three tracks but could not reproduce the crash.

@Daemoc Can you please give @evanf117 the precise steps you took in order to get rid of the crashes?

[Daemoc]

I just deleted all files in the two following locations.

C:\Users\Name\Saved Games\DCS\fxo

C:\Users\Name\Saved Games\DCS\metashaders2

This was a few updates ago though. I have not used the NS430 in a while. I will try to get some time in with it tonight. I will give those tracks a try and see if I can reproduce the crash as well.

[Daemoc]

Yeah, the NS430 is broken again. I have attached a log file.

I purged the shaders and created a new mission with 8 waypoints. I could tell right away it was broken though. My frametimes where all over the place. Sometimes up to 3 second lag spikes. Empty solo mission.

I am at work so I can't do much more testing here, but if you need something else let me know.

dcs.log

[Daemoc]

Here is a video of what is happening on my end...

https://youtu.be/ZKlRGk5hrQ8

This is using my primary DCS computer at home, but this is exactly how it was behaving on my laptop at work that supplied the log posted above.

Sorry for the delayed takeoff, but I have not used this module in a while, I was a bit rusty. The real problems started once I was airborne and you could watch in real time what happens when I switch nav mode on and off. If I would have continued flying it would have crashed DCS, but the amount of time it takes is random.