Search the Community

Are you running TDM in a window or in full screen?

Did that, the lighting is totally wrong on my side. https://drive.google.com/open?id=1QTqZkJjlLBZWK6rqAly1-Jig1XwjlhfD ps. Doing vid_restart made the screen become gray and add to forcefully kill TDM as even the console didn't show after it.

I opened my WIP, which I last edited with 2.02. Now, with 2.03 one of my textures appears black (black in color, but with clearly visible bump mapping) in the game, but seems okay in DR. The game complains about missing texture textures/darkmod/stone/brick/blocks_sepia_grey_d It is as if the diffuse texture did not make it into 2.03? Can someone confirm? The texture in question is called: textures/darkmod/stone/brick/blocks_sepia_grey

How do I close the game console to get back to game? It worked but I thought my screen was having some kind of an attack. It went haywire for several seconds then when it stopped Garrett was upside down lol. Since f is a game function should I try to assign f12 instead? Edit: So can I adjust the 128 so that the screen doesn't convulse so long? I'm worried it will have a heart attack

I have a new machine with gtx 760. It does not want to play TDM. I run TDM on 64bit Arch Linux on this new machine and it breaks before starting. (TDM 2.03 is still working on old 64bit Arch machine). It is ofcourse possible that I forgot to install some 32bit lib but maybe it's something different alltogether... Help much apreciated. [whoop@black darkmod]$ gdb '/home/whoop/darkmod/thedarkmod.x86' GNU gdb (GDB) 7.8.2 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /home/whoop/darkmod/thedarkmod.x86...(no debugging symbols found)...done. (gdb) run Starting program: /home/whoop/darkmod/thedarkmod.x86 warning: Could not load shared library symbols for linux-gate.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". TDM 2.03 #6455 linux-x86 Feb 8 2015 10:21:09 found interface lo - loopback found interface enp3s0 - 10.0.0.23/255.255.255.0 Found Intel CPU with Hyper-Threading enabled, features: MMX SSE SSE2 SSE3 CMOV tdm using generic code for SIMD processing. ------ Initializing File System ------ Current search path: /home/whoop/darkmod/ /home/whoop/darkmod/tdm_textures_wood01.pk4 (317 files) /home/whoop/darkmod/tdm_textures_window01.pk4 (345 files) /home/whoop/darkmod/tdm_textures_stone_sculpted01.pk4 (424 files) /home/whoop/darkmod/tdm_textures_stone_natural01.pk4 (123 files) /home/whoop/darkmod/tdm_textures_stone_flat01.pk4 (281 files) /home/whoop/darkmod/tdm_textures_stone_cobblestones01.pk4 (214 files) /home/whoop/darkmod/tdm_textures_stone_brick01.pk4 (440 files) /home/whoop/darkmod/tdm_textures_sfx01.pk4 (64 files) /home/whoop/darkmod/tdm_textures_roof01.pk4 (65 files) /home/whoop/darkmod/tdm_textures_plaster01.pk4 (140 files) /home/whoop/darkmod/tdm_textures_paint_paper01.pk4 (42 files) /home/whoop/darkmod/tdm_textures_other01.pk4 (51 files) /home/whoop/darkmod/tdm_textures_nature01.pk4 (256 files) /home/whoop/darkmod/tdm_textures_metal01.pk4 (465 files) /home/whoop/darkmod/tdm_textures_glass01.pk4 (46 files) /home/whoop/darkmod/tdm_textures_fabric01.pk4 (41 files) /home/whoop/darkmod/tdm_textures_door01.pk4 (171 files) /home/whoop/darkmod/tdm_textures_decals01.pk4 (367 files) /home/whoop/darkmod/tdm_textures_carpet01.pk4 (92 files) /home/whoop/darkmod/tdm_textures_base01.pk4 (375 files) /home/whoop/darkmod/tdm_standalone.pk4 (4 files) /home/whoop/darkmod/tdm_sound_vocals_decls01.pk4 (27 files) /home/whoop/darkmod/tdm_sound_vocals07.pk4 (1111 files) /home/whoop/darkmod/tdm_sound_vocals06.pk4 (688 files) /home/whoop/darkmod/tdm_sound_vocals05.pk4 (128 files) /home/whoop/darkmod/tdm_sound_vocals04.pk4 (2854 files) /home/whoop/darkmod/tdm_sound_vocals03.pk4 (743 files) /home/whoop/darkmod/tdm_sound_vocals02.pk4 (1300 files) /home/whoop/darkmod/tdm_sound_vocals01.pk4 (82 files) /home/whoop/darkmod/tdm_sound_sfx02.pk4 (596 files) /home/whoop/darkmod/tdm_sound_sfx01.pk4 (924 files) /home/whoop/darkmod/tdm_sound_ambient_decls01.pk4 (8 files) /home/whoop/darkmod/tdm_sound_ambient03.pk4 (24 files) /home/whoop/darkmod/tdm_sound_ambient02.pk4 (156 files) /home/whoop/darkmod/tdm_sound_ambient01.pk4 (209 files) /home/whoop/darkmod/tdm_prefabs01.pk4 (556 files) /home/whoop/darkmod/tdm_player01.pk4 (125 files) /home/whoop/darkmod/tdm_models_decls01.pk4 (93 files) /home/whoop/darkmod/tdm_models02.pk4 (1836 files) /home/whoop/darkmod/tdm_models01.pk4 (1915 files) /home/whoop/darkmod/tdm_gui_credits01.pk4 (49 files) /home/whoop/darkmod/tdm_gui01.pk4 (673 files) /home/whoop/darkmod/tdm_game02.pk4 (2 files) /home/whoop/darkmod/tdm_game01.pk4 (2 files) /home/whoop/darkmod/tdm_fonts01.pk4 (696 files) /home/whoop/darkmod/tdm_env01.pk4 (98 files) /home/whoop/darkmod/tdm_defs01.pk4 (166 files) /home/whoop/darkmod/tdm_base01.pk4 (155 files) /home/whoop/darkmod/tdm_ai_steambots01.pk4 (24 files) /home/whoop/darkmod/tdm_ai_monsters_spiders01.pk4 (82 files) /home/whoop/darkmod/tdm_ai_humanoid_undead01.pk4 (50 files) /home/whoop/darkmod/tdm_ai_humanoid_townsfolk01.pk4 (95 files) /home/whoop/darkmod/tdm_ai_humanoid_pagans01.pk4 (10 files) /home/whoop/darkmod/tdm_ai_humanoid_nobles01.pk4 (48 files) /home/whoop/darkmod/tdm_ai_humanoid_mages01.pk4 (8 files) /home/whoop/darkmod/tdm_ai_humanoid_heads01.pk4 (96 files) /home/whoop/darkmod/tdm_ai_humanoid_guards01.pk4 (373 files) /home/whoop/darkmod/tdm_ai_humanoid_females01.pk4 (169 files) /home/whoop/darkmod/tdm_ai_humanoid_builders01.pk4 (91 files) /home/whoop/darkmod/tdm_ai_base01.pk4 (8 files) /home/whoop/darkmod/tdm_ai_animals01.pk4 (80 files) File System Initialized. -------------------------------------- [New Thread 0xf78bfb40 (LWP 1233)] ----- Initializing Decls ----- ------------------------------ ------- Initializing renderSystem -------- using ARB renderSystem renderSystem initialized. -------------------------------------- I18N: SetLanguage: 'english'. I18N: Found no character remapping for english. I18N: 1228 strings read from strings/english.lang I18N: 'strings/fm/english.lang' not found. WARNING:Couldn't load image: guis/assets/splash/launch Couldn't open journal files Couldn't exec editor.cfg - file does not exist. execing default.cfg Unknown command 'use' Unknown command 'console' Unknown command 'next' Unknown command 'prev' Unknown command 'previous' Unknown command 'next' Unknown command 'crouch' Unknown command 'Lean' Unknown command 'lean' Unknown command 'Readables' Unknown command 'spyglass' Unknown command 'compass' Unknown command 'lantern' Unknown command 'maps' Unknown command 'objectives' Unknown command 'keys' Unknown command 'lockpicks' Unknown command 'lean' Unknown command 'Inventory' Unknown command 'Mantle' Unknown command 'creep' Unknown command 'frob' Unknown command 'inventory' Couldn't exec autoexec.cfg - file does not exist. I18N: SetLanguage: 'english'. I18N: Found no character remapping for english. I18N: 1228 strings read from strings/english.lang I18N: 'strings/fm/english.lang' not found. ----- Initializing Sound System ------ sound system initialized. -------------------------------------- ----- R_InitOpenGL ----- Setup X display connection dlopen(libGL.so.1) dlopen(libGL.so.1) idRenderSystem::Shutdown() Program received signal SIGSEGV, Segmentation fault. 0x00000000 in ?? () (gdb) backtrace #0 0x00000000 in ?? () #1 0x082ab812 in GLimp_Shutdown() () #2 0x0814428d in idRenderSystemLocal::ShutdownOpenGL() () #3 0x0805c926 in idCommonLocal::ShutdownGame(bool) () #4 0x0805f2cb in idCommonLocal::Shutdown() () #5 0x0805bc2a in idCommonLocal::FatalError(char const*, ...) () #6 0x0814cc2c in R_InitOpenGL() () #7 0x0814dd95 in idRenderSystemLocal::InitOpenGL() () #8 0x08060fd5 in idCommonLocal::InitGame() () #9 0x080614c3 in idCommonLocal::Init(int, char const**, char const*) () #10 0x082a948e in main () (gdb) quit A debugging session is active. Inferior 1 [process 1229] will be killed. Quit anyway? (y or n) y [whoop@black darkmod]$

It's before it gets to the main menu. You never even see it. It crashes during the grey screen.

All right, I guess I didn't wait long enough ... I'm used to missions having a loading screen.

I just downloaded The Dark Mod and as soon as it finally downloaded I ran the application; my screen went black and this window popped up. Im a newb and don't know what to do.It says that it can't find some of the files. I've ran the updater a couple of times and it says that it's up to date.

r_mode -1 just means to use the custom height and width only. You can still set the aspect ratio to one of the three available modes: seta r_aspect 0,1,2 (4:3, 16:9, 16:10). Try setting a custom resolution that falls into one of those apects and see where it gets you. IE set the vertical resolution to the vertical res of your main screen then use probably 16:9 ratio to get the maximum horizontal res. Exceeding one of the available or set aspect ratios will probably just give you a black screen or crash.

I had this when I was in windowed mode, but full screen worked fine. I needed windowed to work and managed to get rid of the black screen by disabling post processing in the advanced video options. Don't know if either of you are running windowed but it's worth a try disabling post processing. Edit: re-read the earlier posts and realised it affected the GUI not just in game as in my case. Ignore my advice, PP shouldnt affect the main menu at all.

Is the game going fullscreen but only rendered in the top left corner, so the rest of the screen is black? If he's using onboard graphics like intel, he might have keep aspect or don't scale option set. Man there's so many things that it could be.

I would like to add my problems report too! - The new shadows simply dont work at all, they just create fields of black spots. I have an onboard card, so it might just be a compability thingy, old shit n stuff. - The rope arrow is suddenly broken... As soon as i climb on it, it freaks out and lashes itself into the first wall it can find. Unclimbable. Thats all i care for :3 The update brought alot of new performance! And the SFX update really made a huge entrance <3 thx

I had tried deleting the "doomconfig.cfg" file alone but I still encountered the Black Screen problem and not until I deleted both the "doomconfig.cfg" file and the "gamex86.dll" file did I have any success in getting rid of the Black Screen problem. I realize a new "gamex86.dll" file is created each time the game is launched. I'm assuming that the first "gamex86.dll" is somehow corrupted after the first launch and that's why it needs to be deleted so a new and clean "gamex86.dll" can be used on subsequent launches.

I disagree, I think it is the same problem. Just because people are finding different solutions to the problem it doesn't mean that it's not just one problem with a few different solutions to fix that one problem. I do research for a living and I often find there can be numerous ways to a problem but usually there is an easy way to fix the problem and many hard ways to fix the same problem. Yes, I have run TDM without any other Doom 3 Mods installed and still had the same Black Screen problem. I also completely uninstalled Doom 3, patched it, and installed TDM but I still got the Black Screen. Why don't you just tell me what you think is the best solution to this problem? Of all the solutions posted in this thread which one seems like the best solution? I assume with your knowledge you can easily weed out the good ideas from the bad.

Thanks Myagi for the suggestion. Were you also experiencing the Black Screen bug and did this fix your problem? It seems like there are a lot of people experiencing this same Black Screen problem. There is a lot of speculation and a bunch of different ideas but does anyone have a definitive solution to this problem? Again, we all seem to be describing the exact same problem so it seems fair to think that there should just be one solution to this problem. I've tried the solutions listed in this thread but haven't been able to get TDM running. I might have missed something so is there one solution listed here that really should work?

Looks like scaling ought to be able to fixed using the monitor's setup menu: https://www.kitguru.net/peripherals/james-morris/samsung-cf791-34in-quantum-dot-curved-monitor/3/ Looked at a lot of software config stuff, but said nothing about the hardware setup - and it looks pretty irritating interface for that monitor. 110-degree FOV will mean you get the same view as any 16:9 res, scaled to 21:9, but might stretch prevent the GUIs stretch. Another option is to run the game in a window, clip the border off with borderstripper (http://winborderstrip.sourceforge.net/) and alt+enter it, same as stretching out other old games from the last millenium. Might get some letterboxing, might not. Idk - only purpose I can see in having a super-widescreen monitor is to be able to have 2 "fullscreen" applications running at the same time on the same screen. Like Photoshop and Lightroom or bitmap2material, Illustrator and Aftereffects and Premiere- so you can just drag between them and still have all the space to be able to work effectively, or stick it on its side and be able to read a bunch of dll or notepad++ (or a long forum thread on a monitor) without scrolling. Have you still got the receipt..?

If you set the resolution you do not have to set the screen ratio, the code will compute it on its own. Dunno if this is the root of your issues, though.

Hi. I've got the same problem here. The Dark Mod runs fine first time, tried to change the resolution and restart, and I get the Doom 3 loading screen, then a black main menu. The Dark Mod music plays but the screen is black. The console still works, and it shows 161 warnings related to being unable to load various assets for the main menu. On a more positive note, I loved the music, and the artwork I briefly saw on the menu was very atmospheric. I'm really looking forward to working this little bug out so I can see some more I think I might try the Linux version tonight...

I unpacked the contents of the zip file to my darkod directory. The main screen works both ways, r_fullscreen 0 or 1. I have successfullystarted the training mission and it looks like this https://we.tl/t-ME5PVgzRWg Abayo.

The OpenGL programmer in me thinks that looks like the underwater effect is supposed to be rendered to an FBO for some post-processing to be applied, but the FBO is not being bound correctly and the render is happening to the screen instead.

Okay, I deleted the game files using Steam, deleted all of the remaining files including dark mod stuff, installed doom3 and now it is freezing without doing anything to it. (oh and the steam version is the latest version...there is no patching and never supposed to be any patching required for steam games - manually anyway) Edit: looked at the steam log, and apparently the game goes to a black screen because it has stopped recieving any new frames....which makes sense as the game halts, monitors blacks out (no display), and then I get a black screen (display).

Realtek High Definition Audio and EAX is and has been off. oh and FYI, the music continues without a problem when it goes to a black screen. Edit: I decided to check the version of room (which is correct), but I noticed where it gave me 12 warnings of being unable to load images related to extinguishable light. Would cause this kind of the issues I'm having? Here are the warnings or at least the 11 that it would show me and yes that period warning is what it gave me: Couldn't Load Image: . Couldn't Load Image: extinguishable/lamp_shaded Couldn't Load Image: extinguishable/lantern_oil_hand Couldn't Load Image: extinguishable/lantern_oil_hand02 Couldn't Load Image: extinguishable/round_lantern_sitting Couldn't Load Image: extinguishable/round_lantern_unattached Couldn't Load Image: extinguishable/streetlamp/roundstreetlamp Couldn't Load Image: extinguishable/streetlamp/roundstreetlamp_02 Couldn't Load Image: extinguishable/wallight2 Couldn't Load Image: extinguishable/wallight_3_unattached Couldn't Load Image: extinguishable/wallight_outdoor3 Edit2: nevermind, I tried Doom3 and it crashes right when you are about to be bioscanned...only this time the screen goes grayish white instead of black...go figure. Edit3: Dang it....looks like I'm going to be the odd one out from here on, no Dark mod missions for me.

So I fiddled with this last night and found that I'm not able to properly validate vsync. It seems that my monitor must automatically do some sort of buffering of it's own. I was not able to get screen tearing no matter how much I punished my FPS and turned off all vsync. It's a crappy little LCD TV that also can be used as a monitor and it has a resolution of 1366 x 768 but it's defacto input resolution is 1080p which it auto-downscales so I'm guessing there's all sorts of funky DSP manipulation to the HDMI input I'm sending it. Going by FPS alone, both r_swapInterval 1 and -1 cap FPS at 60 but seem to allow it to fall to lower values without going to 30 FPS automatically... which is apparently what Adaptive Vsync should do. Disabling in-game vsync in favor of Adaptive Vsync in the driver produces the same result. Someone who has a monitor which exhibits tearing without vsync will need to test r_swapInterval -1. As for me? No vsync needed until I get a new monitor I guess.

Yeah, looks like it. The only things that can be done are: r_finish 1 (super slow but forces correct buffer management) Adaptive Sync: Recent GL drivers implement a new WGL/GLX extension called EXT_swap_control_tear. This extension brings "adaptive vsync" as featured in modern gaming consoles to the PC. Adaptive vsync enables v-blank synchronisation when the frame rate is higher than the sync rate, but disables synchronisation when the frame rate drops below the sync rate. Disabling the synchronisation on low frame rates prevents the common problem where the frame rate syncs to a integer fraction of the screen's refresh rate in a complex scene. Adaptive vsync can be enabled with wglSwapIntervalEXT(-1) or glXSwapIntervalEXT(-1). https://www.khronos.org/opengl/wiki/Swap_Interval https://www.khronos.org/registry/OpenGL/extensions/EXT/WGL_EXT_swap_control.txt I wonder if r_swapInterval takes -1 already...

I can't repeat that compass background bug. Please attach your .cfg and if easy a test map or a map name where this plays up. I can see however a compass offset on the screen with r_fboResolution < 0.