crash on the Kola map

[jackd]

game got stuck on this tester: Christen Eagle Kola Test 01_JJ.mizdcs.log

 

[silverdevil]

21 hours ago, jackd said:

game got stuck on this tester: Christen Eagle Kola Test 01_JJ.mizdcs.log

 

hello

i found a post with a reference to the "dcs render time exceeded allowed slice" error. the post also states an f14 livery may be the cause.

your log

2025-11-20 16:13:43.154 ERROR   EDCORE (11576): Drivers errors while mounting coremods/aircraft/f14/liveries/f-14a-135-gr-early/.gitkeep:
2025-11-20 16:13:43.154 ERROR   EDCORE (11576):     ZipDriver: Failed to open zip archive coremods/aircraft/f14/liveries/f-14a-135-gr-early/.gitkeep.
2025-11-20 16:13:43.154 ERROR   EDCORE (11576): Drivers errors while mounting coremods/aircraft/f14/liveries/f-14a-95-gr/.gitkeep:
2025-11-20 16:13:43.154 ERROR   EDCORE (11576):     ZipDriver: Failed to open zip archive coremods/aircraft/f14/liveries/f-14a-95-gr/.gitkeep.

also this post

just a quick test for you would be to change out that livery. i can also try it on my system.

when does the mission hang? do you ever get the mission start?

[jackd]

Thanks, been a while since i used DCS fully, now in a conflict where it starts and closes real slow, probably obliged MT move related.  E-cores on / off and stutter problems to boot.

The mission runs, but i'll experiment this evening a bit more and will report back later if i find anything.

[sleighzy]

3 hours ago, jackd said:

E-cores on / off and stutter problems to boot.

You have core parking enabled. Use the ParkControl software, or registry key update, (check your log afterwards to ensure that the below log line no longer appears) to disable core parking for your power management profiles.

CPU HAS PARKED LOGICAL CORES (this can be source of stuttering and reduced performance especially on hybrid CPUs with P/E-cores)

You've also added a core affinity (params for your shortcut, or something else???) so have disabled a whole heap of cores on your CPU. No idea why you would do that. Remove it.

system  affinity mask: 11111111111111111111111111111111
process affinity mask: 11111111
CPU: Intel(R) Core(TM) i9-14900K [1x L3 caches]
CPU has uniform cache size 36 MB (per cache)
all CPU cores have the same efficiency class 1
all CPU cores have the same performance class 1
common cores: {4, 5, 6, 7}
render cores: {0, 1, 2, 3}
IO cores: {}
unavailable cores: {8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31}

 

Title of this post is "crash on the Kola map", but no crash in this log. Do you have an actual crash?

Edited Saturday at 08:22 PM by sleighzy

[jackd]

Formerly it was advised to park the e-cores, worked well for a while.Maybe not any more?

added: I enabled all cores now, and it seems fixed ...

Edited Saturday at 08:46 PM by jackd

[scommander2]

23 minutes ago, jackd said:

added: I enabled all cores now, and it seems fixed ...

Really? Wow..., good to know... Intertesting... 

[jackd]

DCS and problems, always there's someone with a fix somewhere ... 

[sleighzy]

2 hours ago, jackd said:

Formerly it was advised to park the e-cores, worked well for a while.Maybe not any more?

added: I enabled all cores now, and it seems fixed ...

Glad to hear it's fixed.

That post is also almost a year old. Process Lasso help(ed) some folk on older versions of Windows (non-Win 11) that didn't support P/E cores all that well. Depended on what their symptoms were as well, was not a one-since-fits-all tool, like anything in DCS problems can be due to numerous different reasons.

[jackd]

ADDED info, the crashes did not happen again.

I still had some screen shaking, now fixed with a new 9070 XT driver update from AMD direct, not from the Gigabyte site, latter was older.