"WARNING: Couldn't load image: ..."

[cemeth]

Hi all,

 

I'm so happy that I found this mod again - I totally forgot about it, although as a Thief fan I really anticipated it back when it was first announced.

 

But there's a problem when I launch it. The menu screen is completely black, just the cursor is visible. I hear the menu music and hear when I select menu items, but no visuals at all.

 

Here's the console log (I can access the console just fine):

http://pastebin.com/pzJEG30r

 

As you can see, he was unable to load many of the files/textures/images, including "WARNING: Cannot find guis/mainmenu.gui", so I guess that's the problem.

 

Doom 3 itself (and all other games as well) runs without any problems, it has the required patch, and the TDM updater did its work without a problem.

I have an early Intel Dual Core CPU and an NVidia GTS 450 card, if that matters. Running on Windows 7 x64 with latest updates. Also, latest NVidia driver.

 

I already looked through the FAQ and changed the multi display mode to "Single Display Performance" (since I use two monitors). But the problem persists. Doom 3, on the other hand, always runs, with or without these tweaks.

Furthermore, I ensured that the "darkmod\DoomConfig.cfg" contains these settings from the FAQ:

seta image_usePrecompressedTextures "1"

seta image_useNormalCompression "2"

seta image_useAllFormats "1"

seta image_useCompression "0"

seta image_preload "1"

But that didn't help either.

I also tried changing the resolution from 1920x1080 to 800x600, but as expected that doesn't change anything as well. Was just a try.

 

Any help is very appreciated.

Edited July 23, 2012 by cemeth

[grayman]

Welcome, cemeth!

 

Someone who knows more than me will be along shortly to help get you started.

[cemeth]

Okay, it works now, the settings from the FAQ do actually work, the only reason I had those problems was that darkmod\DoomConfig.cfg got overwritten every time so it had different values again.

After using the exact same settings from the FAQ (see above) in an autoexec.cfg or via command line parameters, it works without problems.

D'oh. :-)

Edited July 23, 2012 by cemeth