PG map crashing without a crash log

[Zyll]

Hi team,

 

I've been tracking for quite a while now the incidents that the Persian Gulf map just closes on me, without any crash log, and no real pattern to what might be causing it. I fly the Hornet on multiplayer maps, and when the issue occurs, DCS just closes, I'm sent back to my desktop. The last line in the dcs.log is not indicative of a core dump or anything, it can be anything really. Here's the latest example:

 

2019-05-01 03:39:21.783 ERROR_ONCE DX11BACKEND: texture 'mig-29c_tex01_spec' not found. Asked from 'NGMODEL'

 

Anyways, this is the history of each occurrence. Wondering if others have seen similar behaviour?

 

2/27 4:50pm - PG map, viewing external friendly maverick fired by player

3/1 5:43pm - PG map, fiddling with SA and attack radar MFDs

3/16 4:46pm - PG map, cycling external views from MIG29s to SU25s

3/30 1:50am - PG map, just flying formation way up north with Hornet and Harrier

4/6 12:33am - PG map, switching from AIM9X to guns on SU25

4/10 12am - PG map, Gulf Fury, just flying to a WP

4/14 5:38pm - PG map, just flying towards air targets, checking radio on 31.000

4/26 11:52pm - PG map, looking at F10 map

4/27 2:43am - PG map, external view sitting on the carrier

4/28 3:53am - PG map, belly landing and crash at Dubai

4/29 - deleted fxo and metashaders2

4/29 12:39am - PG map, looking at F10 map

[Zyll]

worth mentioning that this NEVER happens on Caucasus. If I crash flying Caucasus, I always get a crash log, along wit the prompt to send the info to ED.

[NineLine]

Can you supply your dxdiag file?

[Zyll]

Will do the next time it occurs. Thx 9L

[Zyll]

doesn't the dxdiag.txt log only get generated when there is a crash? I checked and I don't see it in the logs folder, only in an older zip file from a previous, unrelated game crash.

 

regardless, here's the latest one I have on my machine from last month, hope it helps

 

https://drive.google.com/open?id=1s7hq3WYta0WJWWzFEBzuVAQqySbAKUXR

[NineLine]

Here is how you can create one yourself:

https://support.microsoft.com/en-ca/help/4028644/windows-open-and-run-dxdiagexe

[Zyll]

I just got another exit to desktop w/o crash log. Here's the dxdiag immediately following:

 

https://drive.google.com/open?id=16WX1Lp-r9p1qhugGwfvzFTPDhR55t_LU