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


Forums

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

  1. Can you post a screen shot to show what you mean by the menu screen issues?
  2. If i would like to tdm-graphics more realistic (imho), i would change the following video settings in tdm. (after i created a backup of darkmod.cfg) Video > general: Texture anisotropy = 16 Video > advanced: ambient rendering = enhanced Interaction shader = enhanced Post processing = enabled bloom intensity = highest Object details (lod) = very high Or In darkmod.cfg seta r_postprocess "1" seta r_postprocess_bloomIntensity "2" seta image_anisotropy "16" Tip: I created my settings by switching back/forth from settings to playerview, using a windowed screen and alt-tabbing, After this i enabled the shadow of the player: seta g_showPlayerShadow "1" You can ask the community to create a hq texturepack.
  3. Found the cause of the problem, but still no solution. When the two external monitors are active (DP-0 and DP-1) in extended mode, TDM starts on the laptop screen (DP-3, which had been off until that moment), makes it the primary display and turns the other two off. Even after quitting TDM this configuration stays. I hadn't noticed that before because my laptop was docked with the lid closed. Is there any way to tell the engine to start on the current primary display and not change the configuration?
  4. After a while I wanted to play the dark mod again, I am happy to see the community is still active. I once again got the `black screen' on startup, and I solved it the same way. The get the feeling of the game again I wanted to play the Training Mission, but I got the message on post title. Exploring the source code a little I got the game seek that executable using g_Global.GetDarkmodPath() / "tdmlauncher.linux", and according to the log 'Darkmod directory is /opt/doom3/darkmod/'; so it seems a little strange as the resulting path seems correct. I read about in the wiki, but my dmargs.txt contains only comments (or so I think, it contains only lines starting with #). What can I try? Thanks etb
  5. Ok, the SVN version is running fine. So apparently something is borking with the 2.03 update. Run as admin, still crashed. No default.cfg, only the DoomConflg.cfg. Installed in C:\Users\[...]\games\PC\FPS\Darkmod. In the folder properties, suddenly the "Read only" box keeps checking. I turn it off; click ok. Then open up folder properties again and it's checked again. (i.e., I can't turn it off.) It was not like that the last time I looked into it (like yesterday). Edit: Actually, it's not a check, but a black box, as if some items are "read only" but not everything, maybe. And it's doing that for every folder on my entire HD.
  6. Ok, I tried downloading missions one at a time, and it's a bit more reliable ... but there's something very dodgy about "Crucible of Omens: Behind Closed Doors". It's offered for download, despite the fact I've already got it ... perhaps an update, though the downloader doesn't say so. I did the following: 1. Selected it (by itself) for download after downloading a number of other missions. Game crashed again. 2. Found a complete bcd_l10n.pk4 file (20182 bytes) in the fms directory, but nothing else. 3. Restarted tdm, selected CO:BCD for download again. 4. Jumps straight to 10% download, then sticks on 10.4% 5. I leave it for about 10 minutes, no change. 6. Exit tdm via Back and Exit buttons 7. Control is returned to screen ... but game does not complete exit for at least another two minutes! 8. There's a partially downloaded _bcd.pk4 file in fms (991567 bytes) When the game finally did exit, it crashed: ------------ Game Shutdown ----------- ModelGenerator memory: No LOD entries. Shutdown event system signal caught: Segmentation fault si_code 1 Trying to exit gracefully.. idRenderSystem::Shutdown() double fault Segmentation fault, bailing out shutdown terminal support About to exit with code 11 Ho hum. Is the downloader getting any love for 2.04? It truly does suck.
  7. When recording with OBS and the compass is being used, OBS only records the bottom right corner of the screen. My theory is that OBS's "game capture" (which is the only way that I can get it to record TDM at all) believes that the 3d compass is the game, since it's on it's own layer. OBS version 0.657b using "Game Capture" source The Dark Mod 2.03, code revision 6470
  8. That's weird. Most bits of the hud are on their own layer. I've never heard of OBS, so I can only offer generic suggestions. Have you tried playing in windowed mode (still full screen size) and capturing the specific window?
  9. Here is my system configuration. http://modetwo.net/d...post__p__257367 Is this enough information for you? To anyone who has system issues .... I highly recommend that you monitor cpu and gpu stats while gaming. MSI afterburner and EVGA Eleet can show gpu stats on-screen while gaming. I always display on-screen: gpu frequency,gpu temperature,gpu fan speed,gpu usage, vram usage, and frame rate. cpu usage can be checked in windows task manager. ctrl+alt+del to open and alt+tab to switch to windows task manager while in game.
  10. 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.
  11. Good price for a large screen, I started searching on newegg and found this 14" Toshiba M645-S4118X Windows 7 Home Premium 64-bit CPU Type Intel Core i5-2410M 2.3GHz Screen 14" Memory Size 6GB DDR3 Hard Disk 640GB Optical Drive BD Combo Graphics Card NVIDIA GeForce GT 525M Video Memory 1GB GDDR3 $999 Would appriciate your opinion. Again, thank you for your help. Pete
  12. I got 16000 kbit, but recently my speed is much too low and I'm gonna contact my provider tomorrow May I can help you in another way. What do you need? EDIT: I currently noticed, that some windows are cut off in the secondary window and I can't seem to move them to fit in the window (see screen) See the surface inspector in the left screen??
  13. Mortem Desino, thank you very much for testing this too! Now we see that I am not the only one with this bug. DR is totally fucked up (windows float everywhere over the screen) when I go to full screen mode and change the window settings, it even crashed when I chose the last window setting in line.
  14. Didn't notice that 1.6 is already out - thanks for the hint! I don't know if I tried this already in 1.5 - may the solution lied in 1.6, I am not sure, but here's the solution that may be for interest for bug fixing: I solved the problem by opening DR 1.6 change from full screen to windowed mode close DR 1.6 open DR 1.6 again -- It seems that DR can't handle the two screens when started in full screen mode. I don't use Catalyst Control Centre, I just use the Windows XP 2 monitor settings provided. So this is a DR-related bug in my opinion, which may can be hunted down now. I look forward to your responses on this (but foremost I am so glad and very happy, that I can map again)!
  15. 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.
  16. But... Those are the menu objective lists. They were okay as stated in the first post. The problem was with the 'O'-screen, the objective list which comes on screen like a readable ingame. Not in the menu, the game is running while you look at the 'o' objective list. I think the default for that is button 'O.'
  17. Regarding the Print Screen key on my Win 7 system it only puts the print into the clipboard and I need to paste it into a another program to save it
  18. Try binding another key. Also let's try making it take longer so you can see if its actually doing anything. Try binding it to f So in the console type: bind f screenshot 1920 1200 128 Now when you hit f in game the whole game should pause and the screen should jitter 128 times.
  19. @greebo With the heart mission installed and a folder in the doom 3 folder named heart I created the custom shortcut by cutting and pasting your text (path was correct) and ran the game. The 'Current Mission' dialog still does not show the current FM but clicking Start Mission works and Heart runs. I pre-checked the fs_ variables and they appeared correct from the feedback in this topic. I played a short time and tried to save the game. The save game dialog exits to the active mission screen with the message 'Game Saved' at the top of the screen but going back to Save/Load displays a blank list as if the game is NOT saved. Exiting the program, I checked the 'heart' folder in the doom 3 root and in it the 'savedgames' folder. It contains 3 files: .save .tga .txt reading the .txt file -> contains 3 lines: "heartBegin"... the name I chose for the Saved Game... so I know that this is the 'save instance' I was trying to create. "heart"... I assume the system's name for the game the save belongs to ""... an empty double quote Hope this helps.... I'm sure lost
  20. For mysterious reasons, anti-aliasing never worked for me in TDM. Since I hate it when edges make the pixels of my screen stand out, I would like to change this! The menu option is enabled, and r_multiSamples is saved at the value of 4. I have an ATI Radeon 6870 card, and the free video driver for Linux (MESA 11.0.5). FSAA works in most games although there are exceptions, while MESA is configured to do what the application says in this regard.
  21. They copied the buggy briefing screen code from somewhere? Frankly i thought that the briefing screen code was included in the dark mod.
  22. I ran into two initial problems when trying out TDM. I have a fix for one that I'll share in case anyone else encounters the same issue. TDM Update CrashesRunning tdm_update.exe results in a crash: 'tdm_update.exe has encountered a problem and needs to close.' This happens shortly after the copyright line of text is displayed. A zero length tdm_mirrors.txt file is created. If I manually obtain a correct tdm_mirrors.txt file and run with tdm_update.exe --keep-mirrors, the same crash happens just after 'Fetching checksums from server...'. To workaround this problem, I used the torrent to get the game. Following the wiki suggestion of cleaning out %temp% did not solve this problem. Second start of game = Black screen with sound, invisible menus, and generic grey mouse cursorThe new 'DoomConfig.cfg' created after the first run of the game had a setting that would cause this error. Through trial and error I determined the setting I needed to update: Change seta image_usePrecompressedTextures "0" to: seta image_usePrecompressedTextures "1"
  23. I have just downloaded TDM using the installer/downloader but I'm having a problem that doesn't appear to be listed anywhere. I've searched these forums, I've gone through the installation guide and the FAQ but everything that seems to be for the problem I have hasn't helped. Basically, when I load the mod I get the music playing but the screen is totally black. I can see the mouse pointer and I can hear the sounds as I pass it over the buttons but I can't see a damn thing. When I bring up the console I can see that there were 166 warnings during loading saying 'could not load image', so my guess is that the game can't find the images and so it's just using blank ones instead. I have followed the installation instructions, I am running the 1.3.1 patch, I've added commands into the DoomConfig.cfg file as mentioned in the FAQ, I've also switched the Thread Optimisation off under the NVidia control panel. But it's not working... Any help would be greatly appreciated. [edit] I just thought, someone is probably going to ask for my system spec, so: Intel Core 2 Duo - 3ghz, 4 Cores 4gb DDR3 (that's physically installed memory) NVidia GForce GTS 250 1gb (driver version 197,13) Windows XP Home (32bit)
  24. Apart from multi-screen issues I've touched in an another thread, I've never had any issues with running Darkmod in 64-bit Ubuntu 14.04 LTS either. I've dabbled a bit with DR too, and had no issues with that either - apart from not being able to use it due to user errors, that is... Actually, there still is one: the sound doesn't work if I've got Clementine, my music player of choice, running at the same time - but since you can't really play Darkmod with other sound sources running at the same time, that's not been a showstopper.
  25. 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!
×
×
  • Create New...