Doom fatal error failed to read default cfg



Doom fatal error failed to read default cfg

For any LINUX users running into this issue, make sure you’re running steam-runtime and not steam-native, somehow this causes the above issues.

For Windows users. Apparently the Doom files often end up corrupted so doing an integrity verification could help, alternatively you could try running Doom as administrator to make sure it’s not some strange user rights issue.

For any LINUX users running into this issue, make sure you’re running steam-runtime and not steam-native, somehow this causes the above issues.

For Windows users. Apparently the Doom files often end up corrupted so doing an integrity verification could help, alternatively you could try running Doom as administrator to make sure it’s not some strange user rights issue.

Just verify your game files.

Did you manage to fix your issue?

Im having the same problem and tried everything (admin on steam, admin on game exe’s, verify integrity, deleting 2016 files)

Did you manage to fix your issue?

Im having the same problem and tried everything (admin on steam, admin on game exe’s, verify integrity, deleting 2016 files)

Recently with BeamNG I had a similar experience, where actually removing the game from steam and adding it back DID fix it, whereas the verification didn’t help when I tried it before that. So you could try removing the game and re-downloading the whole thing perhaps..

Источник

Doom fatal error failed to read default cfg

For any LINUX users running into this issue, make sure you’re running steam-runtime and not steam-native, somehow this causes the above issues.

For Windows users. Apparently the Doom files often end up corrupted so doing an integrity verification could help, alternatively you could try running Doom as administrator to make sure it’s not some strange user rights issue.

For any LINUX users running into this issue, make sure you’re running steam-runtime and not steam-native, somehow this causes the above issues.

Читайте также:  Python try exception type

For Windows users. Apparently the Doom files often end up corrupted so doing an integrity verification could help, alternatively you could try running Doom as administrator to make sure it’s not some strange user rights issue.

Just verify your game files.

Did you manage to fix your issue?

Im having the same problem and tried everything (admin on steam, admin on game exe’s, verify integrity, deleting 2016 files)

Did you manage to fix your issue?

Im having the same problem and tried everything (admin on steam, admin on game exe’s, verify integrity, deleting 2016 files)

Recently with BeamNG I had a similar experience, where actually removing the game from steam and adding it back DID fix it, whereas the verification didn’t help when I tried it before that. So you could try removing the game and re-downloading the whole thing perhaps..

Источник

Doom fatal error failed to read default cfg

It gives me an error saying:

FATAL ERROR: Failed to read default.cfg

This doesn’t happen on a normal wine prefix so Im wondering what went wrong. I also want to know where the root of the steam play prefix is so I can check the files manually.

I’m having the same issue on latest Solus.
Game works fine with regular Wine.

I’ve tried verifying game files and redownloading the whole game, no change.

It’s not launching for me either on Arch, except the error for me is:

Does not start for me either, how to get debug output?
If I start steam from terminal it doesn’t appear to show anything relevant to Doom starting.
Have installed Doom on a Steam library on an NTFS formatted HDD as my Linux SSD is tiny.
GPU: AMD RX 56
OS: Ubuntu 18.04.1
Kernel: 4.18.3-041803-generic

Читайте также:  Error confidence value 136

Edit:apparently my files are corrupted, on verifying game files it restarted downloading the game.

Источник

Doom fatal error failed to read default cfg

It gives me an error saying:

FATAL ERROR: Failed to read default.cfg

This doesn’t happen on a normal wine prefix so Im wondering what went wrong. I also want to know where the root of the steam play prefix is so I can check the files manually.

I’m having the same issue on latest Solus.
Game works fine with regular Wine.

I’ve tried verifying game files and redownloading the whole game, no change.

It’s not launching for me either on Arch, except the error for me is:

Does not start for me either, how to get debug output?
If I start steam from terminal it doesn’t appear to show anything relevant to Doom starting.
Have installed Doom on a Steam library on an NTFS formatted HDD as my Linux SSD is tiny.
GPU: AMD RX 56
OS: Ubuntu 18.04.1
Kernel: 4.18.3-041803-generic

Edit:apparently my files are corrupted, on verifying game files it restarted downloading the game.

Источник

Doom 2016 Failed to read default.cfg (379720) #16

Comments

brandonegbert commented Aug 22, 2018

Crashes on launch with an error box that says failed to read default.cfg.

The text was updated successfully, but these errors were encountered:

drohm commented Aug 22, 2018

I’m getting the same error.

gcc: 7.3.0
nvidia drivers: 390.77
1080Ti

FedoraTipper commented Aug 22, 2018

Same OS as drohm.

OrdinaryMagician commented Aug 22, 2018

This didn’t happen when I was running Steam through Wine.

Rosalie241 commented Aug 22, 2018 •

Same issue on arch with nvidia

parkerlreed commented Aug 22, 2018 •

parkerlreed commented Aug 22, 2018 •

Problem is introduced with Steam native. use Stream runtime and it works.

kiendang commented Aug 22, 2018

Got the same problem on Antergos but then I got it to work by using Steam runtime instead of native and adding +r_renderAPI 1 to the launch options.

Читайте также:  Error in writing the output log при загрузке

drohm commented Aug 22, 2018

Mine started working after I turned ‘Linux Steam Integration» (LSI) off. I then had to set the +r_renderAPI 1 as a launch option.

Rosalie241 commented Aug 22, 2018

steam-runtime fixes it weirdly enough

cclecle commented Nov 9, 2018

issue is closed ?
I still have it, I tried a lot of config and still «Failed to read default.cfg».
I tied: native / runtime and the 2 availables PROTON version.

Do you think it can be related to my MESA 19-dev build ? It work with other game and this error seams not to be related with mesa.

kisak-valve commented Nov 9, 2018

Hello @cclecle, this issue is currently open as indicated directly below the title at the top of the issue report.

cclecle commented Nov 9, 2018

Hello kisak, sorry I misread the tag..

So I did some more investigations. Apparently it is related to mesa 18.3 OR the way I link mesa 18.3.
MESA 18.3 + GLX 18.3(radeon_si) => ERROR default.cfg
MESA 18.3 + VULKAN (RADV 18.3) => ERROR default.cfg
MESA 18.1.9 (the native one in my debian) + VULKAN (RADV 18.3) => Launch and Run OK
MESA 18.1.9 + VULKAN (RADV 18.1.9) => KO, but it is a known issue
MESA 18.1.9 + VULKAN (AMDVLK 18.40) => Launch and Run but freeze a few seconds after

So th e default.cfg is linked to MESA 18.3 usage, even if it is not really used (VULKAN rendering case).

nobodywasishere commented Jul 10, 2019

Does this issue still occur on latest drivers/proton?

slokhorst commented Jul 17, 2019

It seems to work fine now with «Proton 3.16-9 selected by Valve testing».

By the way, even though I started Steam with STEAM_RUNTIME=0 , it’s giving a bunch of messages about STEAM_RUNTIME_HEAVY . Not sure if that’s related.

Источник

Оцените статью
toolgir.ru
Adblock
detector