Search the Community

Hey Guys, Big fan of TDM, been playing it for a while off and on over the last several years. Never had a technical issue I couldn't overcome until now. I recently rebuilt my rig, re-installed TDM, updated to 2.03, and now I can't load levels. I get through mission briefing/equipment purchase just fine, but as soon as I hit an actual load screen, the game locks up after loading about 1/5 of the bar (see attached images). This happens on every mission I've tried (including the included training mission). There's no error popup, and it doesn't crash, it just hangs forever. I've tried adjusting settings in the game itself (video quality, resolution, vsync, etc) to no avail. I'm stumped. Here's my system specs: - Windows 7 (64 bit) - Intel Core i7, 4.0GHz - 32 GB RAM - NVIDIA GeForce GTX 680 (updated to latest drivers) Any ideas or assistance would be greatly appreciated. Thanks in advance guys!

Hey, i'm using Linux as well. I'm running tdm on my laptop with Ubuntu 14.04. (32 bit) Intel Pentium CPU P6200 @ 2.13GHz × 2 1,8 GiB RAM Intel Ironlake Mobile x86/MMX/SSE2 The performance is far from perfect. In normal indoor areas i get around 20 fps, which is ok for me, but on outdoor areas or if there are any AIs around it keeps around 7 fps, which quite sucks I can also start tdm with wine, but then when i try to load a mission the loading screen freezes. It would be interesting to know your system data as well for comparing to see if the low fps is a linux related problem or just because my system sucks (more probable).

I re-downloaded and it seems to work on at least one map that I got the error on before, but I still can't play NHAT 2 because of it. I tried NHAT2 with a clean TDM but that didn't help, I still can't play it. Also for some reason I often have to click the start button in the objectives screen twice because first the mission loads as usual and then for some reason it just resets back to the object screen so I'll have to start the mission again which means I'll have to load it again too. How should I fix this?

This can be cause by a number of things - the first is please try starting doom3 and putting in the CD key there. If it accepts the key, restart d3 and make sure it doesnt ask again. If this happens chances are that TDM will be fine. If that doesnt work, I remember someone had the same situation regarding gamex86.dll as happens with some people getting a black screen... but try making sure doom3 is happy first. Starting the map directly will skip a lot of 'nice' things, so it isnt really recommended.

I have identified my brand of the black screen problem. Basically, after having gone through the briefings of an appearingly randomly selected number of fms, it gives me a dialogue box saying that the map files cant be found. Which would indicate a problem with the download. I later found out that the problem was caused by me having put spaces between fm names with multiple words when downloading them (i.e. sons of baltona.pk4). Writing sons_of_baltona.pk4 or sonsofbaltona.pk4 completely got rid of the problem.

My turn for a weird problem. Until recently, r_showShadows 1 drew the outline of shadow volumes for me in blue wireframe lines, visible through solid surfaces, which is correct. r_showShadows 2 drew them as pale blue solid shapes, which get hidden by solid surfaces, also correct. Now, option 1 draws them as black lines which are harder to see, and option 2 doesn't show anything at all. It's not any recent change we've made to the engine. I tried it in 2.02 TDM release build and got the same problem. I wondered if the new catalyst beta driver was at fault, so I reinstalled it. No change. I did a clean remove and reinstall of microsoft .NET, no change. I removed all ATI sofware and reinstalled the stable release version instead of the latest driver, no change. I can't think what else to test. Would someone do me a favour please and confirm whether they can see any shadows with r_showShadows 2 turned on? This end, I'm seeing nothing: I'm losing both the shadows and the debug drawings of the shadow volumes. ??? Edit: It turned out the blue colour wasn't correct after all. Edit2: Updated the thread title because this has become a more general discussion since we got past the bug fix.

hi, I tried searching but I couldn't find any topics regarding my problem: i just played st.lucia again on 1.02 and when the obj screen updated this obj with a mark - completed. a little bit later I checked the obj screen again and the mark is GONE although . Now I finished all objectives but when I leave the church I can't end the mission, the mission just continues on...... .... I have a savegame if it helps: http://dl.dropbox.co...457202/luci2.7z PS: thanks for this superb mod, I always enjoy playing it and the updates you provide

Thank you HiddenCoast. I will try this one. Springheel, I really don't know why you struggled with my question. I just wanted you to tell me what you thought was the best way to solve the Black Screen problem. It seems like a simple request. If you didn't have a suggestion then I wanted you to tell me what post from this thread seemed like the best solution again, seems like a simple request. It's true I said I have tried the suggestions in this thread but I also said that I would be more than happy to repeat a suggestion that looked promising to an expert such as yourself in the event that I didn't correctly follow the instructions the first time. I just wanted some Dark Team Mod advice.

You're right, it looked better with the Sikkmod shadow.vp, but it was still broken. Somewhere along the way, we must have lost a line from shadow.vp: MOV result.color, vertex.color; Our shadow.vp doesn't set the vertex colour at all, which is why my lines were black and why option 2 (which uses an additive blend to paint the shadow volume "surfaces") didn't show up at all. Sikkpin's shadow.vp set it to a constant RGB 0-0-1 which is why everything came out blue. But the engine is set up to set the colours itself, using different colours for front faces and back faces, and for different shadow optimisation routines, so you can tell how a given shadow got drawn. It looks much better when you let the engine color it:

It doesn't appear that I'm going to get an answer from the Dark Mod team which is odd since this problem seems too large to ignore. How about this, does anyone know how to fix the black screen problem? I've tried the above suggestions but they didn't work for me. Any help would be greatly appreciated.

Found interesting detail - if I keep only one parallel light, I don't have the issue with brushes not being lit. The problem is that I can't stretch one sunlight to light up both areas. Might have to use a hack - script that moves sun light to a new outdoor area :/ Blocking tunnel with brush doesn't help at all - one room becomes pitch black.

Since upgrading my machine (and switching to a Geforce 8800 GTX) I've noticed a couple times now in TDM where I get a strange flicking effect. At first it just looks like the screen is randomly flickering to black for half a second, occuring every 5-10 seconds. Tonight (the second time I've noticed it) it started happening again, and the frequency started getting faster and the effect more severe--after a few minutes surfaces almost looked like they were z-fighting every two seconds or so. It seemed to be somehow related to the flickering of nearby lights...there were a couple places where the flickering stopped, and it was always where there were no lights. As soon as there were flickering lights visible it started up again. Anyone heard of this before?

Can you post the changes that occur between the DoomConfig.cfg where your screen is pitch black, and the default one? (Since it looks like you're on Linux, a unified diff (use diff -u) would be grand. )

I'm having the same problem on Windows 7 and a GTX280 on 195.62. It starts fine but defaults on 1920x1200, when I set my resolution and restart I just see a black screen.

Yeah, you "agreed" to it... so... yeah they can do whatever they want. I don't know if Demagogue has looked at that EULA but I would be curious the opinion of an actual lawyer on that piece of writing. The language is exTREMely open ended/un-specific and I understand that a certain amount of that is for, "Cover Thy Ass" insurance, against numb-nut idiots and people trying to exploit the OS. The issue is, this open ended language ultimately permits, whatever they want, while we KNOW they are bringing targetted advertising in to the OS. Its like a one-two punch to the gut of the consumer (with their hands tied behind their back). I personally don't think MS is up to anything malicious (particularly) and isn't out to get you or any bullshit like that. I just think they're trying to unify a system that doesn't want or need or can be unified. Phones/tablets/portable touch devices/smart home appliances/console game devices/ etc. I think can all be grouped in to one ecosystem but PCs are not and have never been one of those devices and should not ever become one. PCs used to be about what a USER wanted to do, what ever it is. If they want to do this, they can do this. If they want to do that, they can do that and more importantly if they DON'T want their PC to do something, that PC follows their orders. They're the USER. Software and Hardware are made for them to use to do the things they want to do. Losing site of the USER and worse, using the User to pull ad revenue, in a place that has always classically been the User's domain, the PC, is just.... really really sad. The fact that MS has gone this direction, for me at least, speaks to the lack of direction, originality, and creativeness, in their company. I personally have no issue with anything in Windows 10 save for one thing. If you have the "Pro" version of the OS you should, as a user, be able to disable ANY FUNKING THING YOU WANT. If it breaks the OS, that's because you meant to. You can fix it. If you have stable drivers loaded for playing a game or regression testing, you don't want your OS coming in with a god fist and undoing your work only to have to remove and reinstall what you were using and then blocking temporarily (explicatives!) some update that should never be pushed to the box in the first place. More importantly, you shouldn't EVER have to think about this in the first place! The OS should be transparent and unobtrusive! From Windows 7, I'm all for regular, Critical updates, being installed automatically no matter what. If there's a problem, you should be able to remove that problem and block future issues. For drivers though, particularly from a "regular user" who doesn't have any idea what they're even using, or what "right clicking the task bar" even means, auto-updating drivers is the worst idea in the history of man (exaggeration). "My computer won't come on..." Um... did you try and boot in to safe mode? "What's that?" Um... click. I can picture the support calls now. I think Windows 10 should install all the latest greatest hardware drivers on initial install and then either should not install another driver ever, OR should give the User a freaking checkbox to say, "NO THANK YOU!! I'M THE USER AND I DON'T LIKE BREAKING MY PC AT REGULAR INTERVALS". /rant In summary, Windows 7 is on my Personal Computer. It does what I tell it to. Its not on an appliance, toaster, refrigerator, phone, point-of-sale device, tablet, gps, car computer, or any other touch screen enabled anything. Windows 10 wants to be but its made for dumb devices and people. It has nothing to do with a conspiracy.

I don't believe UV alignment region shifts are applicable to models but it is well known in the black art of "brush carving" that change the texture alignment slightly will cause dmap to split tris and correspondingly split draws when rendered. This is a boon in cases where you don't want a surface to be hit by too many light passes but obviously a problem where texture alignment is changed for artistic reasons and there's no rendering reason why new draws should be generated. I'm still looking for more CPU skinning engines in the wild. From what I can see, there's a few more out there than I originally reckoned but the examples thus far are mired in proprietary Intel SSE dependencies.

Hi and thank you for the replies and suggestions so far. @Fidcal I haven't played St Lucia on this machine. @Serpentine I had the 9.10 driver and I have now updated to the 9.11 driver, no change. @New Horizon I realise your second last reply was meant for Noisycricket but with the new driver I have again gone through and tried both the default (My default) config as well as the change you mention and after that didn't work I tried the other changes as well. @Noisycricket I haven't fiddled with DOOM 3 settings at all and the game had detected as Ultra, I changed that to High instead, changed seta image_useCompression back to 1 since it got set to 0 when I changed my DOOM 3 settings. I still have a black screen. image_useallformats makes no difference whether its set to 1 or 0. Uncertain if this is relevant, but my resolution settings don't seem to have any effect on the game. Low res even though I've got the config set to 1920x1200. Regards,

Those lights are a material shader problem. There's nothing wrong with the screen shot beyond the self lit glass in the lights. It's up to the map author to decide how much ambient light they want lighting their entire map, we make some suggestions on the wiki I believe, but the light level I'm seeing here doesn't look too out of the ordinary in your screen shot. On my laptop monitor it looks just right, and on my older CRT monitor...it's almost too dark to see anything. So I think it's ok. I've seen Thief 2 scren shots that looked far brighter than that.

After a few minutes, the training mission crashes and never in the same place: so far object room, lockpick room, archery range, central room, and even outside. The game however, doesn't actually crash, it just hangs for a second, goes to black screen and I have to go to the task manager to end the game (without the use of my mouse as my pointer refuses to move). I have the correct Doom version (followed the patch link on the Dark mod wiki) and I have steam loading up dark mod directly (-applaunch 9060...). I am running a gateway PC with Vista 64 bit OS, intel quad core, Nvidia GeForce GTX 285, and I think 4 Gb of Ram. I've already tried dropping the resolution down to widescreen (16:10) 1080 x 600 and standard shading with all of the other setting off or low. Any ideas what the problem might be? Conflict between Doom and the quad core or the drivers of video card? Edit: updated my video drivers and no luck, still crashes PS From what I have played so far, I love it. Esp. the jumping and mantling mechanic, a far side improvement over T2, but similar enough that I don't have to adjust hardly at all to jump effectively.

One of the main reason I went back to Win7, as it was obvious this situation was going to happen sooner rather than later - After installing the KB3081424 update - Downloads, reboot to install. Gets to 30% and reboots. Gets yo [sic] 59% and reboots. Gets to 59% again and then states something went wrong so uninstalling the update. Wait a few minutes and reboot. Back to login screen This happens without fail, every single time. Since updates are automatic and mandatoryWindows will try to install the update again later, forcing another reboot and locking the user in a endless loop. A potential fix is to remove the security identifiers that no longer exist in the Windows registry, however, hasn’t worked for all.Micro$oft release a tool for removing unwanted updates, but as KB3081424 is a security patch the tool does not seem to allow users to block it.It’s the second update glitch to hit Window 10: update KB3074681 came days before the big launch and crashed file explorer while there were also problems with Nvidia drivers. I would like to know when MS will release a patch that will give control of windows update back to the end user.

Every so often when I make a savegame TDM crashes. It seems to occasionally corrupt a save in that it put underscores in when I hadn't. When I try to load one of these saves I get some message about "bad cache". Also, everytime I start TDM it has the screen resolution set at the lowest even though I set it to 1600 x 1200. Finally, I get very bad frame rate and occasion momentary freezes, but that's probably due to my sorry a.. Intel HD chip! One more thing - is there anything like ctrl+alt+shift+end to go on to the next mission in a campaign? (I tried it and it didn't work!)

Yes, I do. ATI Radeon X850. I tried the game again and it locked up and went to a black screen again after about the same period of time as before, but this time I didn't get control back. I had to shut off my computer. This time, I was not moving around when it crashed, I just walked forward and started reading the book, and it crashed while I was sitting there reading - it's as if it happens after a set period of time, not when I trigger something. I guess I should try some of those performance tweaking suggestions (or all of them). Any suggestions for ATI cards specifically?

I think this is the one you need ("textures missing, screen black"), others will correct me if this is the wrong one: http://modetwo.net/d...en_mostly_black

No sound from any XFI sound card, despite driver installed and the card set to default sound output - the fix, is to set bit depth set to 16bit / 44khz Related: SB Z series drivers will be out this month or next for Win10. Based on everything I've seen and read on Win10 and with Skylake (at least for someone running triple screen resolutions) being what I would call a total flop vs. the aging 2600k Sandy Bridge, what could have been a really exciting year in technology seems to be fizzling out. Oh well, I guess Sandy Bridge E is out next year and maybe they'll get Win10 sorted in another year as well...

same problem for me... but i dont think that doom3 is replacing the dm-cfg... cause the darkmod folder is READ-ONLY on my sys. after downloading and extracting the "newest" tdm file from moddb ("2009_10_18_thedarkmod_v1.0_beta.zip") into my doom3 directory (D:\doom3), i start the "tdmlauncher.exe"... all i get is a black screen and a mouse button (the normal d3 mousebutton, not the tdm one). i can hear sounds and melodies (even the "click" sounds when moving over buttons - as it seems) but nothing more will happen... tried anything, but can just quit via "alt+f4" or console. in console there are some red errors, that the game couldn't load the background images and stuff. some screens are below.. system: vista home premium 64, 4 gig ram, 8800 gtx (using driver 86.18 cause newer ones got problems with some older games i still play) don't have any problems with other mods for d3 or the original game... PLEASE HELP!!! wanna play (waited for YEARS, and just got d3 because of your mod) thx. edit: i checked your FAQ and other forums, no help.