Search the Community

I have just reinstalled TDM and all of the skies seem to have a strange FOV, like you're zooming into them with binoculars. Similarly, when I jump into water my entire vision does this. Water also appears either black on the surface, or with severe visual ripping/artifacts (not sure how to describe). Win XP SP3, Intel T2300 @1.33Ghz (2 CPUs), 1 GB RAM, NVIDIA GeForce Go 7400. Unfortunately I can't update my drivers since it's a shitty Sony laptop that seems to be locked in.

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?

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

oooooo, ok i tried importing one of the prefabs as you mentioned fid, and something DIFFERENT happened! a box popped up with this in it: "Failed to load gui definition guis/readables/scrolls/scroll_calig_medusa.gui. Do you want to open the import summary?" also at this time, the preview window of the readable editor is messed up and shows my desktop or firefox window in it. I answer "yes" and then a window pops up and it says: "Could not open file: guis/readables/scrolls/scroll_calig_medusa.gui" now the window stays open and does not crash DR, but the preview window stays black, and every time i type a character in the title or body section, that first error box pops up with the same message. now what on earth could all that mean?

Actually I love DR and loathe Hammer. It hasn't had an interface update since about 1998. It's clumsy as hell. You have to be in the 'right mode' to do anything and it takes four or five steps to do something that takes 'click and drag' in any Radiant based editor. I finally managed to tinker with the settings to make the font in the program large enough that I could actually read it instead of it being so tiny, but if I have a part of the interface that's just in my way.... my choice is to completely remove it, (if I can find that option) or just deal with it. No moving it to an area that's out of the way where I can still use it if I need it. It's not officially supported by Valve and doesn't seem to be actively being worked on. Personally I'm not sure how anybody makes levels in Hammer. Tiny viewport, no way to scroll that viewport incrementally, (even clicking the scrollbars sends your perspective over by about a third of the screen) and basically none of the aspects of interface design that people have figured out over the last decade or so. Radiant in general (and DR in particular) is an elegant program. I can actually do what I want to do in Radiant without having to fight my tools every step of the way. DR adds more options into that, and does so in the same general way. The models menu? Works. Textures list? Works and I can actually read the name of the texture. Changing my perspective so that I can actually see what I'm working on? Works. None of this is true with Hammer.

Thanks. Gonna try it now. Ok. There has been an improvement. Now it renders normally in DR, and shows in TDM... although completely black. I had double-checked the filename for the bumpmap and compared it to the .mtr file and added the missing 's'. I'll look closer in all my directories in case I still have a .pk4 or an extracted directory which may be conflicting.

I'll look but that should make it appear black. oop, guess I can't look, you only linked the ase. I meant the entire zip so I could check materials/paths/etc..

could also be a bad sector on the harddrive, they also cause crashes to blue screen. or your hard drive might need defragging, as that sometimes fixes ctd's.

I had this at one time with the trainer and also I think for a time during development of my current FM - might have been while I was trying to optimize some big visportals in the city area. I saw black for a few seconds then very briefly the blue screen then reboot. My guess is that it is a normal CTD but also screws up Windows or RAM management somewhere. We used to see blue screens much more commonly years ago but that doesn't mean that Windows is now perfect and traps everything. BTW are you using either of the Alchemist patches and what date did you download (because the combination lock patch was included in an FM update but the spiky ball one remains a separate patch.) The spiky ball bug was the one that CTDed but only on some systems. The combo lock didn't cause a crash just failed to work properly in some situations.

Here's another one for you guys- I haven't been able to find anything on this in the troubleshooting section or anything. The first couple of times I started TDM everything went fine. Since those first two or three times, I now get something weird happening on startup. When I launch Doom 3, it starts with the ID animation that ends on the beating heart with the ID logo- While it's doing the animation there is no sound and part of my taskbar is showing- only part because of the resolution change it can only show part of it. I can get little snippets of sound if I click the mouse button. Then when the startup screen for Doom 3 comes up, I'll get about a half second of the music and the enlarged partial taskbar pops up and the whole thing freezes. If I click the mouse, I'll get another half second of music where the taskbar goes away and I can sometimes move the mouse for that half second, but then it freezes when the taskbar pops on top again. If I keep clicking the mouse like this anywhere from 5-15 or so times, it will eventually stay up and not freeze. Then I click on 'Mods' and then The Dark Mod and the whole thing starts over again when TDM is loading. I usually have to click 20-35 or so times to get it to stay from that point. Once I've gotten it to load like that, I don't have any problems at all with playing. No crashes or stutters or anything. I think I might have a bit of a problem saving as it has me re-install the training mission every time even though I've saved a game and done some quicksaves- I'm not sure I'm doing it right because just getting the game going is too laborious right now to play around with it. If it means anything, I've noticed that when I open the console right after the game gets going, there are a whole bunch of lines in red that say things like: "WARNING could not open image/extinguishable/wall lantern/ blablabla" Some say other things, but most of them are could not open/extinguishable/something Anyway, here's the specs of my machine: Windows 7 Home Premium 64-bit ASUS Notebook G72GX Series Intel Core 2 Duo CPU P8700 @2.53GHz RAM: 6 GB NVIDIA GeForce GTX 260M Thanks

No, the condump has to occur after the dmap. Rereading this, I doubt that you'll see the blue screen I was referring to in my previous note. It's too bad we can't tell dmap to dump to file what it's doing as it's doing it, instead of just writing to the console. Having to try to reconstruct events after the fact is a bit difficult. If we had the D3 source, we could debug the problem. I hope we don't have to wait for that to be released before this gets solved.

I'm not sure why the condump showed nothing about the somewhere5a map. I hope I'm doing it all correctly: Started TDM. At Menu screen, opened console, did 'condump somewhere' then 'dmap somewhere5a'. Is that correct? When I get the crash, it's just your normal small Windows popup 'Doom3 has stopped working'. TDM is visible behind this popup, but nothing's happening (it's how I was able to type the last visible lines from the dmap earlier). I click on the popup, and TDM closes. Nothing else. Regarding the wornlarge and yellowwarp maps...both of those dmapped fine.

Don't bother, it was only black in the beta version. I thought you had done something to fix it as it turned out fine in the final release. Is it worth providing stripped out map files to try narrow things down (i.e. split the map in two, see if either will dmap, rinse and repeat)? Or is it more likely to be a resources thing?

Well, I have ATI and have had no issues with Rift crashing. Or any other map for that matter. But I have been meaning to look at one texture. The stones up the side of the church tower were black for 2 of my testers, but they are white/speckly to me like they should be. That was the only issue I'm aware of though and nobody else mentioned it. And the only custom thing included was a skin (gold texture on rock).

Out of all the FMs listed on the wiki, there are 3 that I simply cannot get to play. Somewhere Above the City - the mission loading bar completes, switches to 'Mission Loaded, Please Wait' text, and Doom3 crashes a short time after. Alchemist - the mission loading bar completes, switches to 'Preparing Mission, Please Wait' text, and Doom3 crashes a short time after. The Rift - the mission doesn't even get as far as the splash screen/loading bar, Doom3 crashes while still showing the 'Dark Mod' splash screen. All crash with the 'Doom3 has stopped working' popup error message. No other error message. All other missions - and by this I mean, every other FM listed in the wiki - loads and plays fine. I first reported this in the Alchemist thread on these forums. Fidcal and nbohr1more were kind enough to attempt to help me with the issue, but after posting a couple conDump files and my DoomConfig, no answer was found as to why it was happening. I have the proper Doom3 patch. I have tried various graphics settings fruitlessly. System specs: Intel Core2 Duo E8400 3GHz, Win7 (have tried with Aero on and off), 8GB RAM, ATI 4870 (Catalyst AI disabled). I appreciate all help and ideas as to what I might try to fix whatever the problem is!

and that has me running 100% where I want it thank you guys. I assume if I change my screen resolution I need to change the above too but I'll deal with that when/if I need to. thanks for all the help

nbohr1more got it right the first time. boy do I feel dumb for some reason I thought my version of Doom3 was pre-patched. yeah I'm a dummy today. so it is working now, thank you very much for the help but I have another question. I have a wide 18~ish inch monitor and the game doesn't display all the way out to the side. the top and bottom meet up well but there's close to 2 inches of black nothing on either side of the game. my screen resolution is 1680 x 945 the closest I can get the game setting to that is 1680 x 1050 but the black side don't seem to change any from me adjustingz resolution or aspect ratio. the game seem pinched side to side to me. is there any way I can get the game to display fully from side to side? thanks again

I finally got around to installing The Dark Mod 1.02. Been meaning to for a long time. The mod looks superb from what I've seen so far. However, the mod was somewhat tempermental to get running well. At first, I had the "menu is a black screen" problem. It seemed to occur the first time I set the window to be full screen. I've also had the issue with the game crashing after several quick saves. But my main reason for posting was to mention the rendering issues I've been having. I'm mentioning a solution I found to one of them, in case anyone else runs into this specific problem. My setup: Win 7 x64, Althon X2 6400+, 2 GB, Radeon 3870, Catalyst 10.6, 1680x1050 resolution. I was having dramatic framerate drops similar to what's been mentioned in this topic. This happened during the training mission included with the mod, in the practice area where you learn mantling and using rope arrows. My framerate was being annihilated whenever I approached the gas lamps near the beginning of that area, after mantling the crates. I knew it had something to do with the lamps, because whenever I specifically approached them the game slowed to an absolute crawl. While up until that point, everything was smooth even at 1680x1050. After trying countless tweaks, I finally found the solution. For Performance Tweaks on the Dark Mod Wiki, it mentions something to try if you get framerate drops around water. On a hunch, I suspected this same setting might help with the lamps. Sure enough, after creating an AutoExec.cfg file with this command, the massive framerate drops disappeared. I'm not entirely sure how this command is detrimental to the image quality of the lighting that the lamps cast, as I don't notice that much of a change. (I think the lamps aren't casting rays on the walls or self-shadowing?) But without it, the game became unplayable. Unfortunately, I've noticed that using this command causes water surfaces to disappear completely for me. No matter what other settings I change. But it was worth the tradeoff. This topic mentions another problem I'm having. The sky isn't being mapped correctly. But Catalyst AI enabled or disabled, it makes no difference. (In fact, I don't notice a difference in loading times either.) Can't seem to find any solution to this. Does anyone have any other ideas? It's not too big of a distraction, though. Maybe I just need to wait for another Catalyst update. (Staying away from Catalyst 10.7.) Oh, and a new tool that ATI owners may find useful is RadeonPro. It's the equivalent of nHancer, for ATI cards. Lets you control and/or force AA, AF, VSync, Catalyst AI, Triple Buffering, and so on.

I have an update on this front: As I started the new FM Betrayal by Fieldmedic the tearing was back, although I made the vid_restart after loading the mission. I saved, quit and reloaded that spot in 1280x720, no tearing, made vid_restart with custom res, tearing was there. But then I decided to test another custom res (only left possible between the two) and this (1232x700) is working just fine!! No need for vid_restart, just loaded Dufford´s and here no tearing too!!!! Damn, am I glad! Oh, I´m so happy cause the new res is cutting so less from the screen that I now can read the last loot-line that wasn´t possible in 1280x720 and nowhere else I had a feeling of 'cut'. I have a gut-feeling that I got finally and for sure rid of the tearing. No talking of the devil, I know, but that have to be it, I´m sure...

Yeah, yeah, did you really had me to get two negative reps? Anyway, I still would like to know if it is possible to change the gray screen that appears while vid_restart. (I guess it´s the same that shows up a little second when starting TDM)

Guys, I'm having crashes in TDM sometimes. Today was the first time I managed to see a TDM error message (as opposed to just a black screen). It read as follows: IdMovable 'IdBarrel_ATDM:Movable_Junk_WBottle01_Broken_1027': Cannot Load Collision Model Models/Darkmod/Junk/WBottle01/Broken.LWO The crash happened in the third NHAT mission, while trying to open a drawer in a room in the upper floor. Just before doing that, I had snatched a golden bottle from a table on the opposite side of the room. Does anyone have any idea what causes these crashes, or where the error message is supposed to point me to? P.S.: I'm experiencing this kind of crashes in other FMs, so it's definitely not limited to NHAT 3.

Another question: While video_restart there is a gray screen. What do I have to do if I want the screen in another color, like pitch black. Or is even a picture possible, like TDM-logo?

Bit of background first: when I first downloaded TDM v1, I suffered the same symptoms: after the first start or two, the main menu would be always completely black. The music would play, and you could click on the menu options if you moved the invisible mouse cursor to the right spot, but still obviously a game breaking bug. At that time, running the updater fixed the problem, and I figured it was probably a corrupted download. Now the problem is back. Just now I've installed a new FM, and the program rebooted itself to a completely blank black main menu screen. Everything behaves the same way, with one difference: running the updater does NOT fix it. In fact, the updater says my installation is up to date. Help would be appreciated. System specs: WinXP Dual Pentium CPU 4 GB RAM GeForce 9600 None of this has changed since I last played, so I doubt it's a hardware problem. EDIT: I've downloaded the torrent (non-updater based) version and overwrote my previous installation with it. It fixed the problem - at least for a short while. I now suspect the problem is integral to one specific FM, namely Glenham Tower. Will post more if I have anything. EDIT: Turns out the issue was most likely that Total Commander automatically puts brackets around certain (hidden?) directory names, and I thought they were meant to be an actual part of the name, so the installation of the FM went wrong. I think, anyway. Problem no longer around.

But I already bought the expensive one! ... Just kidding. Ah, dammit. That are the reasons why I wanted a console, on a PC there is always something wrong. Hmm, this looks interesting, could be an improvement, right? That price I can afford. Should I buy it? I´ll do everything you say, almost! And my actual cables are three meters, don´t need longer anyway. But the DVI-cable is five meters. That´s too long, considering the 3-meter-cables, right? Maybe I´ll try it tomorrow. And my TV is not the best. On TV-programs I got after five minutes white diagonal stripes over the screen. The better TV of my girlfriend doesn´t have this stripes, so it is my TV that causes it. I guess the price was 700€, not sure because I paid 50€ every month and that´s two years ago. Doesn´t anyone else have this too? Because it is not constant let´s me think it maybe is a mod-problem. Finally tonight I´ll play Doom3 with Denton´s HDR-mod, but I don´t think I´ll see it there, because of the small hallways and good visportals. I´ll see...

I don´t think it´s an overheating issue. Because I have it right after the reboot or when I started the next day and always on the same spots. The V-sync wasn´t simply activated in the widescreen-resolutions. And now I got rid of it, I just have to start the game in a different res and then I copy my doomconfig with my custom res back into the folder and it works fine. I could type in the res manually, too, but I´m too lazy for that. Now I´ll play Builder´s Influence so I´ll see if it somehow comes back during the game. I´m usually spending four hours in missions. So if it´s overheating, I´ll see. I hope not, though. Also, I have a software called 'Vtune' that sets a dynamic Fan speed for my GPU. But I never heard the Fan-speed increase. Is it maybe a reason that I use my Phillipps-TV as the screen? It´s connected via HDMI-cabel and the output is in HD-mode. Because of the HD-mode I had to downscale the res 1280x720 to 1216x692, otherwise the picture was too much zoomed in. Actually I haven´t tried to deactivate HD-mode yet...