I got the latest Microsoft Visual C++ Redistributable, installed and rebooted but both sims continue to fail upon starting with the same message. I'm out of ideas.īy the suggestion of pieperjohanns I've found in the logs that the issue gives the following errors: I did he clean install, manually removed even the whole Euro Truck Simulator 2 folder from My Documents and I still get the same error message.

So now I'm trying to figure out how to do a clean install of these without losing progress. I've done the DDU (using DDU from Guru3d to clean uninstall graphics driver) wipe of drivers in safe mode, reinstalled Nvidia drivers manually, everything works except ETS2/ATS, it still presenting the same error message. I'm kinda convinced that something is up with the Nvidia thing though because when I go to the Nvidia Experience and try the 'Optimize games' feature, it says 'Unable to retrieve settings, try again later' also when I go to 'scan for games' it says 'scan failed' I tried the Nvidia clean install, it didn't help. In which log the following two lines standing out to me:Ġ0:00:03.936 : Failed to create swapchain! (0x887a0001)Ġ0:00:03.936 : failed to initialize device! (dx11)īefore anyone asks why I didn't post a bug report, it is because as per bug report rules I can't post reports on profiles that ever had any mods and I've had improved rain and roads on, but both ETS2 and ATS worked just fine prior to the Windows upgrade. You can find the history of my 'research' into the matter of trying to solve this issue below, plus here is my rig:Īnd my over on : The values should correspond to Table 3 of the supplemental doc.So my Win 8 updated to Win 10 after which I was unable to launch ETS2 and ATS.Ĭorrection, I can launch them in OpenGL mode only (which looks like crap) and now at every launch that isn't OpenGL the crash report is saying something like ' There was a problem and ETS2 can't display graphics on your computer because can't find valid graphical display'įrameworks and Nvidia drivers are up to date and double checked. The values should correspond to Table 2 of the supplemental doc.īytes for card name. RID as specified in part 3 supplemental doc from PC/SCīyte for standard. Lower nibble indicates the size of the historical bytes. Higher nibble indicates only presence of TD1. Lower nibble indicates the size of the historical bytesįor ISO14443A: The historical bytes is from the ATS responseFor ISO14443B: The historical bytes is from ATTRIB (ATQB) ATR format for ISO14443-4 cards Byte offset Please refer to PC/SC spec for more details regarding the ATR format. The ATR formats for different NFC card types are listed below.

Ats escan driver error