solved DCS MT won't launch; Authorization fails for all modules, and DX11Renderer-Error

[XCNuse]

Game won't launch anymore; Just get these errors and then it sits in the background doing nothing forever.

Ran last weekend just fine, now it doesn't run at all, only updated to latest OB.

Have not updated GPU drivers.

 

Log is referencing a folder that doesn't even exist?

G:/shaders isn't a location that exists.

 

And for the record; I have zero mods, this is vanilla.

 

 

dcs.log

Edited March 19, 2023 by XCNuse

[draconus]

38 minutes ago, XCNuse said:

G:/shaders isn't a location that exists.

It might be temporary during rendering or hidden.

Does it apply to you?

Try the usual repair, clean, new profile...

Edited March 19, 2023 by draconus

[skypickle]

It is a bug in the steam api. go to the eagle dynamics website and revisit 'transfer licenses' page. Recheck the licenses.

[draconus]

51 minutes ago, skypickle said:

It is a bug in the steam api

In standalone?!

[skypickle]

^Yes, standalone with transfers from steam will fail. He didn't specify so I assumed he is using the standalone with license transfers from steam

[Flappie]

@XCNuse  Try a DCS repair in slow mode.

[draconus]

8 hours ago, skypickle said:

^Yes, standalone with transfers from steam will fail. He didn't specify so I assumed he is using the standalone with license transfers from steam

Fair enough but that wouldn't trigger D3D errors.

[skypickle]

his log shows two types of errors. First there are a series of aircraft specific errors like I used to get due to failed authorization. And at the end after it loads the graphic options it throws another error that is the D3D error. That is most likely a driver error.

[XCNuse]

Took a rather astonishing near 2 hours for the "fast" repair to do whatever it was doing, only utilizing like 10% of my install drive.

But it appears repair fixed whatever was wrong. What's weird is the log of files to fix/delete however were just in the .downloads folder.

Which is funny; as I had to do a repair literally last week after the MT release as well; where the slow mode... took like 10 minutes!

 

Certainly a strange error.

For what it's worth, this was indeed after updating, launching the ME, closing, then going to launch MT, where this issue popped up.

Edited March 20, 2023 by XCNuse