Jump to content
The Dark Mod Forums

Search the Community

Showing results for 'black screen' in content posted in TDM Tech Support.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General Discussion
    • News & Announcements
    • The Dark Mod
    • Fan Missions
    • Off-Topic
  • Feedback and Support
    • TDM Tech Support
    • DarkRadiant Feedback and Development
    • I want to Help
  • Editing and Design
    • TDM Editors Guild
    • Art Assets
    • Music & SFX

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







  1. hi all! this is my first post here, and i want to congrat. with all of the people who work around this fantastic conversion for d3... ok here is the problem, i've enabled the bloom option, via consolle ( r_bloom 1) . but when i come back to game, the screen is flipped up\down...and all movement are inverted-- anyone have idea? my specs. phenom II 550 -->3.6 Gh ati sapphire hd 4780 1 gb win 7 64 bit thX!!!
  2. Another issue: Single pass shadow maps sometimes make the compass render black. r_shadows 2 r_shadowMapSinglepass 1 Quickest replication: 1) Install mission Closemouthed Shadows 2) After the mission starts open the console and type: spawn atdm:playertools_compass 3) Cycle Inventory until the Compass appears With the default r_shadowMapSinglepass enabled, the compass will be black but moving around will sometimes illuminate it. Disabling r_shadowMapSinglepass causes it to remain visible with no artifacts including the issue reported above.
  3. windows 7 updated driver is 391.35 here is my dump TDM 2.06/32 #7400 (7400M) win-x86 May 16 2018 15:57:20 2294 MHz Intel CPU with MMX & SSE & SSE2 & SSE3 Winsock Initialized Found interface: {5540C832-B701-4AEC-B0AC-9786CCD069B1} Microsoft Virtual WiFi Miniport Adapter #3 - NULL netmask - skipped Found interface: {6B342E17-4B02-47E0-B959-38EC80F830C8} Qualcomm Atheros AR8151 PCI-E Gigabit Ethernet Controller (NDIS 6.30) - NULL netmask - skipped Found interface: {1BAA30DE-276A-4A26-A908-B8A900BC43D4} Qualcomm Atheros AR9002 WB-1NG Wireless Network Adapter - 1
  4. Hi. Got the mod yesterday. And so far the only real issue ive encountered is when you have entered all the rooms in the tutorial map the game slows down and get choppy, between 5 and 40fps. In the begining i get the constant 60. Every time i open a door the game freezes a few seconds, guessing it needs to load objects. But i dont remember doom 3 freezing when opening doors. Vista-32 4 GB RAM Q9400 Quad 2.66GHz 4870x2 2GB [EDIT] getting something called "Malloc Failure for 699200" whatever that means. could be the white screen i got just now when i tried to start the mod.
  5. Downloaded the new 2.06 update on laptop. 2.05 worked decently. When starting any FM, the load screen goes for about 5 seconds into progress. When the bar goes a little after the start, the game reverts back to the briefing screen and all sound disappears. If pressing start mission again, it does the same thing, sound still gone. Doesn't matter which FM to try, even training mission. No error message or crashing. No freezing. Tried different settings including performance tweaks in the wiki. What could be wrong? DxDiag_laptop.txt
  6. Hi guys, first of all, GREAT MOD! You guys did a fantastic job on this. I finally got round to buying Doom 3 so I could try out TDM and it's been excellent. However I have one teething problem: TDM keeps changing my resolution every time I quit a session for some reason. I play TDM on a HDTV at 1280x720 (16:9) but TDM will change the resolution in the config file to 1366x768 every time I quit. This is supremely annoying because the TV doesn't support that resolution and if I forget to edit the config file before I load TDM the next time I play, I won't get a display and the only way to exit
  7. My hardware: AMD x2 3GHz (each) ATI RADEON 4850 HD Win Vista Ultimate with maxed out 3.5GB DDR2 RAM 888MHz Mainboard is an M2N I have the most updated drivers and 1.3.1. Doom as ive checked this while running Doom 3 (which runs just fine) The Game Loads then says "Mission Loaded, Please wait" Then the Game will crash saying Doom 3 has stopped responding and as follows with the signature Problem Event Name: APPCRASH Application Name: DOOM3.exe Application Version: Application Timestamp: 45ad459a Fault Module Name: atioglxx.dll Fault Module Version: Faul
  8. https://bugs.thedarkmod.com/view.php?id=5055 There seems to be an issue with shadow rendering in the engine: When enabling both Stencil Shadows and Soft Shadows, shadows get incorrectly mapped and are stretched across the screen in front of the camera. I have no issues when using Stencil Shadows without shadow softness, nor when using Map Shadows both with and without soft shadows. I'm running TDM 2.07 x64. My operating system is Linux openSUSE Tumbleweed x64. Kernel 5.2.14. Mesa 19.1.7 (amdgpu module). My video card is an AMD Radeon XFX R9 390. I attached two screenshots from t
  9. Hi. I've been searching around for help and I've found some similar reports but no solutions. I downloaded TDM yesterday. First time I tried to run it: The game went into fullscreen mode, and my desktop (KDE) was "kind of" showing on the screen- most of the screen was black but a small section of my desktop was all zoomed in and distorted. I could hear the TDM menu options click as I hovered my mouse over them, but could not see any part of the main menu.Googled, someone said to change resolution in the config. So I set r_customWidth and r_customHeight (2560x1440). Saved the config and
  10. As the title says, I have been trying to get TDM 2.0.7 working on two computers with Windows7 32 bit. Both have older Radeon displays, and the best I can get is a Mission Loading screen that crashes to desktop half-way through. I have tried every tweak mentioned on this forum, to no avail. I can get TDM 2.0 from 2013 working on both machines.
  11. I can confirm the 2.06 black screen (with sound) on playonmac (playonmac 42.2.0, Wine 3.18, default wine video settings, vcrun2013) And in that container, 2.05 works fine. Given sollutions in this topic, gives my the same bad results. Do we need install something else beside vcrun2013?
  12. Hi, Guys, I LOVE YOU, okay in a nerdy man way, but OMG thank you so much for making Thief FUN AGAIN. WOOT! Alright, Was playing through Tears tonight, and although it didnt stop me from playing through the level, there was almost always this tiny ....box in the lower left corner of the screen. It would obstruct the view of any weapons that i was selecting and it seemed to update with the visibility crystal in the center of the screen. Just wondering if there was a workaround to get rid of it, or pointing it out if you guys havent encountered it. I'm using a radeon 4850 hd, Intel Quad co
  13. Ok, so I did what freyk suggested and installed the "vcrun2013" component. This time, the game will actually launch - the music starts and when I move the mouse around or hit the buttons it is clear that I am "making contact" - but the thing is, the screen is all black. Any further ideas? Btw, thanks a bunch for the help, I really appreciate it!
  14. Yeah, CTD is "Crash To Desktop"; which is still better than BSD "Blue Screen of Death".
  15. Didn't it used to be that if you failed an objective and the mission ended, that if you brought up the Objectives screen, the failed objective would be marked with a red "X"? Or have I been smoking too much weed? In any case, if the "X" used to be there, it's no longer there in 2.07.
  16. http://bugs.thedarkmod.com/view.php?id=4893 I found a very problematic issue in the engine. I'm running TDM 2.06, 64bit executable, Linux version (openSUSE Tumbleweed x64). The issue is as follows: Previously, if a bad script or definition or missing asset error occurred, TDM would crash back to the main menu and the error would appear in the console. It seems this is no longer the case and something worse happens instead: Errors will now cause the process to freeze, shortly followed by a permanent black screen. The reason why this is annoying is because alt-tab switching still doesn't w
  17. Thank nbhor1more - I've tried the stuff mentioned in guru3d forums and also spoken with Nvidia about the issue - they've no idea... Ended up fixing the illustrator / photoshop stuff myself while Nahoor was reading the manual... I'll try out the colour depth thing - there's definitely some weird lights that flash up every now and then, in older games. The HDR thing oughtn't be an issue... Getting screen tearing scrolling up and down in browsers or pdfs. Something's definitely weird... Can't figure why stuff is fine in windowed, but not fullscreen. At least black is black, white is white, R
  18. A month later. TDM is still crashing for me. I updated again and at least the type of crash changed. Now the screen cycles through four brands of "black screen" (black, black-grey, black, black-grey) and then the game crashes with the same error message as before (in the above screenshot), except the grey part is only a smaller square in the corner. I'm down because I haven't been able to play lately.
  19. Removing TypeInfo removes the compilation error. A source search for r_´╗┐legacyTangents finds nothing, so I can't follow this suggestion. Now, a fresh complete build of the binaries yields binaries that don't even get to the point where they display anything on the screen. A check of running applications shows no TDM. If someone could try a build of the latest binaries and show they create working exes, it would be appreciated. Then I can begin to narrow down what's going on at my end. If no one else can get the SVN binaries to run, then whoever's been making the latest source ch
  20. Hi, This appears to directly affect TDM (or, rather, the "kind of dark mod now"). Win10 pro, v.10.0.15063 Build 15063.726 Nvidia 388.31 (15/11/17 or 11/15/17 for you yanks) - despite this was the same version I already had from October. Win10 updates on this day were KB4849011 and KB4048954 Something about these updates and / or the new Nvidia drivers has seriously up a lot of older games. But made newer games look better... Perhaps in how either DX and/or shader models are being handled. Colour lookup table is not being taken from system - is a "blank canvas". Cannot re-create previou
  21. It might have been common knowledge that D3 engine was not VSync friendly. The TDM community consensus was have VSync off for this or other reasons. Since 2.06 however players have more options vsync off, capped fps, old school gameplay with screen tearing vsync on, capped fps, risk of microstuttering vsync on, uncapped fps, (the new recommendation) vsync off, uncapped fps, Q3 style
  22. I get a massive slow down in 2.06 if my screen resolution is not set to the native ratio and im using AA and/or vertical sync. Try disabling vertical sync and AA then try out a few screen resolutions in both windowed and fullscreen. See if that helps. Are you on a laptop? GTX1080 should do fine with TDM.
  23. All the PC's are Intel ! The computer I've been playing TDM on for the last few years, has an AMD Radeon HD 7700 Series card with 2 GB Ram The others are equipped with AMD Radeon R7-200 Series with 4 GB Ram. But the result is always the same This missions are not playable : CTD 107) A New Job 1) Tears of Saint.Lucia Training Mission 3) Chalice of Kings 12) Business as Usual. 15) Heart of Lone Salvation 17) The Alchemist 19) TP2 The Beleaguered Fence 30) Talbot 2 Return to the City 32) St. Alban 2 (Cathedral) 33) TP1 The Knighton Manor 34) SW1 Flakebridge Monastery 36) TP4 The Transaction
  24. Hello, everyone! I've done some searches in the forums, and looked in the troubleshooting on the wiki, but there's a problem that's been in Dark Mod for the past version or two that's now prevalent enough for me to log in and report. Not sure if it's an issue with the Dark Mod itself or just one model of light that someone developed and is using in more and more missions, but it's driving me nuts. In several missions, electric lights are used and the tone the game has them emanate...well, I'm supposing it's supposed to be a soft hum, but instead it's a piercingly loud sine wave kind of t
  25. I would expect both approaches have roughly similar speed in general, with the exception that stencil shadows are culled to light screen size projection while shadow maps are usually fixed in size. E.g. when player is a room fully lit by a couple lights (Officer Lounge in Fence) stencil light will draw in full screen size twice, while shadow map could draw in 512x512 buffer. But then player is in the street with many small lights stencil could draw each light in a screen region as small as dozens of pixels, while shadow map is still 512x512 (not that there's no way to add LOD's to that as well
  • Create New...