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. ah, reinstalls get so frustrating. I just reinstalled Doom3 and patches to 1304 , then with the HD issues I re-installed windows. Now when starting Doom3 it starts and goes in game fine. When starting TDM it hangs on the TDM screen, and my cursor arrow appears. I remember this happening before but not what I did to fix it. The paths are correct. this is my log Path to tdmlauncher is D:\Doom 3\darkmod\tdmlauncher.exe Darkmod directory is D:\Doom 3\darkmod\ Darkmod directory after normalisation is D:\Doom 3\darkmod Trying default value for engine executable: D:\Doom 3\DOOM3.exe Found engine executable in D:\Doom 3\DOOM3.exe Engine path after normalisation is D:\Doom 3\DOOM3.exe Could not find 'currentfm.txt' file in D:/Doom 3/darkmod/currentfm.txt Current FM is: Using the following argument vector: #0: +set #1: fs_game #2: darkmod Starting process D:\Doom 3\DOOM3.exe +set fs_game darkmod Closing logfile. I did delete currentfm.txt, but was getting the same thing before that. before that with creeps installed Path to tdmlauncher is D:\Doom 3\darkmod\tdmlauncher.exe Darkmod directory is D:\Doom 3\darkmod\ Darkmod directory after normalisation is D:\Doom 3\darkmod Trying default value for engine executable: D:\Doom 3\DOOM3.exe Found engine executable in D:\Doom 3\DOOM3.exe Engine path after normalisation is D:\Doom 3\DOOM3.exe Current FM is: thecreeps Using the following argument vector: #0: +set #1: fs_game #2: thecreeps #3: +set #4: fs_game_base #5: darkmod Starting process D:\Doom 3\DOOM3.exe +set fs_game thecreeps +set fs_game_base darkmod Closing logfile. I've always had the space in Doom 3, no issues. Please tell me I don't have to reinstall doom because I reinstalled windows (messed up reg?) Doom 3 works fine.
  2. I've encountered some strange things on these curtains: http://min.us/mbcQjnDAPQ NOTE: There are two screens in this link! (w/wo error) If I am far away, they project the texture of a new model (which has to be on the screen too) to itself. This only happens if you are some steps away from the curtain and is visible best, when in dark (it kinda lights itself). Did anyone encounter this too? The console prints no object related errors (see ) The object has 1.300 Polys and was finished with Turn To Poly (maximal polygon size: 3) and Edit Poly. It was created from a Plane. I am confused.
  3. Hi, everyone. I've got a problem with resolution in full screen, it seems to be always 640*480, whatever numbers I choose in the game settings or put in config file. When I start or restart DM it may be set to 1280*1024 or any other I set previously in the settings, but actually it's 640*480. In the window mode the's another problem - resolution is ok, but part of the window is not seen, as if it's beyond the display. Win 7 x64, NVIDIA GeForce GTX 460 SE., DM 1.07. Any ideas?
  4. Yeah pretty much everything is caused by the whole 'Surface Format Optimisation' setting, since it flips cubemaps and loses rotation on RTT. Hence why the sky moves in the wrong direction and the screen is painted upside down. The problem is that sometimes the setting is triggered by a profile, and other times it's the setting. If you're lucky just disabling the setting will be fine (it also makes things look a bit better). This miiight be fixed in 1.08, just having trouble finding a way to test it on my boxes, without quick testing it's hard to fix it in the most correct way. I have a tester lined up to test nearer release, so don't need offers or anything — just letting you know why it's hard to provide a Yes/No.
  5. In many cases resolution settings won't stick unless you create an autoexec.bat with them. What screen resolution and aspect ratio? Do you have your video drivers installed properly? Post your cvars so we may review.
  6. Baddcog, note that there are two screens in the link. One near the model without error and one with another model on the screen which projects its texture onto the curtain. I made a note in teh first post now, so everyone can see that there are two screens on the page The curtain was made out of one plane which I modified via "noise" and "FFD box". Then "Turn to poly" and "Edit Poly" like in every other model I made. Even for the .dds textures I didn't do anything special. I can't figure it out by myself. I looked in the edtior: The model isn't duplicated. I tried the DDS Utitlitys but they don't seem to work correctly. Whoa this is all goin' to hell
  7. For the record, I've never had any problems with screen captures before, but trying to do so just crashed on me last night in 1.08.
  8. This is happening to me. After extracting the archive I got from moddb, I run tdmlauncher.exe and it works correctly. But, even if I don't mess with the configuration and I just quit, every subsequent time I launch the game it starts at a smaller resolution than the first run and everything is black except the fps. Edit: I made md5s of the files before and after running and DoomConfig.cfg and gamex86.dll were both modified. Edit: Yeah, so I replaced those two files from the downloaded archive and it fixed every launch thereafter. I had to modify the DoomConfig.cfg file in the training_mission directory in the root of the doom 3 install directory in order to change the resolution settings. I thought that was kind of odd. It seems to work anyhow.
  9. That patch got me in, thank you. I tried the training mission a few times - but the game freezes every time I go to black jack someone. I'll search the forum her and at TTLG to try and find an answer and write here again if I don't find one.
  10. 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.
  11. Dang it, problem setting tags Well it looks like the boost problem is fixed on Linux as of TDM 1.07 but now I have a new issue. When the game tries to restart the mouse cursor get's stuck in the top left corner of the screen which activates the new Gnome 3 (aka Gnome Shell) menu and there's absolutely no way for me to get control back other than to restart X or go to a VT and kill the doom.x86 process. Any ideas? Thanks, Richard
  12. No it doesn't work for me, here is what I did: Uninstall old ATI driver Reboot Uninstall everything from ATI left with Driver Cleaner Pro Reboot Install only the Display driver (newest ATI version 11.12) Sky is turning like mad (it makes me puke). Post Processing turns screen upside down. Game is running fine without post processing and with the no_skybox.mtr file.
  13. 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?
  14. 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.
  15. 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..
  16. I'm having an issue in only Doom 3, where when I move the mouse slowly the cursor doesn't move on the screen at all. This happens in Doom 3, DM 1.06 and DM 1.07 and SVN version. No other OpenGL or DirectX game exhibits this behaviour. It also occurs while in the menus and in game. I've deleted all the ini files in the directories and let Doom/Darkmod re-create them, no change. Has anyone else experienced this?
  17. Thank you, that second link had the answer, apparently when going between windowed mode and full screen mode Doom 3 gets all wonky. Just closing and opening Doom3 repeatedly seems to have corrected the issue.
  18. 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?
  19. 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).
  20. Putting it down to performance doesn't help for me, still reversed screen with post processing, and reversed sky without.
  21. Hello, I want to share with you my knowledge regarding this issue. I couldn't fix this problem with spinning sky and upside-down screen on newer drivers for a long time. ATI tray tools and Radeon pro solutions didn't work for me. I was frustrated and quit playing TDM. Then I found somewhere that all you have to do is to set in control center Catalyst A.I. option to PERFORMANCE. The wise man said: "Performance = off". He was right. It wasn't logical to me but it works. Try yourself. Regards
  22. Ah ok :-D I presume that the NVpanel sense a CRT because I use a classic VGA connection, i think the problem it's not there. Nothing too with fixed "aspectratio" line :-( Even more strange: if I run Doom3, all it's normal, the screen it's always full a well scaled with all the resolutions selected.
  23. The control area is listing it as a CRT from ASUS in your screen-shot though... How about some screens of the sub-menus for some of those options in the tree on the left ? (edit: BTW... did you see the fixed configs above... )
  24. Mine it's a flat panel screen, not a crt :-) (it's simple a LCD 24'')
  25. That's strange indeed. But give this a try... Run 'nvidia-settings' and go to the settings for your monitor under GPU0 > DFP-0 (most likely)... it is just below 'PowerMizer' setting. You may want to try tinkering with the GPU Scaling Method settings. Mine defaults to Force Full GPU Scaling (checked), and GPU Scaling Method = Stretched. You may want to try 'Centered' or 'Aspect Ratio Scaled', to see how the screen will display then. My guess would be that yours somehow got set to 'Aspect Ratio Scaled'... but that's just a guess. See this screenshot:
×
×
  • Create New...