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. Here's the latest.. If I run darkmod as Administrator, I can contact the server, I can install/uninstall a mission, I can load a mission until it says press attack to start and I cannot start the mission. It isn't hanging as the esc key works as does F5 and F8. I just can't start the mission. The cursor is also missing from the screen. Am I alone with this problem? Is it unique to Dell? What?
  2. Did you delete the training pk4 first? If the only thing listed in the New Missions screen is the Training Mission, but you're getting St. Lucia, then something is quite wrong with your installation. I'd delete the entire fms folder and run tdm_update again.
  3. Still having troubles with no dynamic lights and black squares instead of some particles. I've write about it here (http://forums.thedarkmod.com/topic/14199-solved-more-108-weird-behaviour-crashes-graph-problems-gnulinux/page__p__298356#entry298356) but the solution I've get is not acceptable now. So, I try to run "Old Habbits" mission. It runs without lights, crashes with segfault after exit. In console:
  4. Okay, I just found out what the problem was: Right after the installation of Windows I changed the readability to 150% (at highest resolution it was pretty hard to read anything at the standard setting). Since I changed so many settings after that (common when you set up a new pc) I didn't think of that anymore. Eventually I got back to that setting by accident and tried out the standard settings just to be sure. Suddenly the title screen of TDM was okay. When changing it to 150% at the very beginning I didn't realize it could affect anything beside the readables. Thanks anyways. At least I got my cfg file with your help
  5. I updated from 1.07 to 1.08 using the updater and then deleted the fms in the Doom3 directory leaving those in the darkmod directory I first tried running St Lucia and noted a problem with the torches - black squares moving toward me behind the torch. I then tried old habits with the same effect. I tried thecreeps next and received this error message - see picture I tried the trainer and again the torch problem was there - see picture As I am the only person having this problem what steps should I take to sort it My system is Windows 7 64 bit, 4GB RAM, Nvidia 8800GT graphics with an old driver 197.45 To add I deleted Old Habits and reinstalled it using the games downloader and I have the same problem with the torches looking a bit further the tdmlauncher log contains this but I don't have a file tdmlauncher.exe just TheDarkMod.exe Path to tdmlauncher is D:\CD Games\Doom3\darkmod\tdmlauncher.exe Darkmod directory is D:\CD Games\Doom3\darkmod\ Darkmod directory after normalisation is D:\CD Games\Doom3\darkmod Trying default value for engine executable: D:\CD Games\Doom3\DOOM3.exe Found engine executable in D:\CD Games\Doom3\DOOM3.exe Engine path after normalisation is D:\CD Games\Doom3\DOOM3.exe Current FM is: deceptiveshadows Using the following argument vector: #0: +set #1: fs_game #2: deceptiveshadows #3: +set #4: fs_game_base #5: darkmod Starting process D:\CD Games\Doom3\DOOM3.exe +set fs_game deceptiveshadows +set fs_game_base darkmod Closing logfile.
  6. The really awesome feature in Linux is that you can move windows by holding Alt and clicking anywhere on them. This comes in handy if part of the window is not on the screen and you need to move it quickly. I use it constantly.
  7. Okay, so I couldn't run the game in fullscreen mode: it would just reset the r_fullscreen to 0 every time it loaded. Turns out it was an arg on a file inside the package: contents/MacOS/Doom 3 automatically sets r_fullscreen to 0, which is annoying if you want to play the game in full screen. Looks stable otherwise. I'll go test some missions now.
  8. I already tried running the game on single-screen only and it didn't change a thing. Even deleted the config-file completely and ran the game at whopping 640x480 with all settings off and nothing changed. EDIT: My hard-drive is a reqular one. It's quite fast though.
  9. I'm pretty sure Tels added this for v1.06. Not very prominently documented: http://wiki.thedarkm...new_in_TDM_1.06 http://wiki.thedarkmod.com/index.php?title=Resolutions Someone needs to tell the Wide Screen Gaming Forum: http://www.wsgf.org/...hp?f=64&t=26703
  10. Maybe the problem will just go away for me too, or maybe it only happens with certain levels. Either way it isn't a big deal. Also, when I checked my screenshots, I was surprised to see that they were the same brightness, even though the screen was bright when I took some and dark when I took others Seriously, I really would like for someone to teach me how to post pictures in the forums. Thanks
  11. Inspired by a thread on a here a little while ago I bought a cable to connect my dvi socket on the computer to the hdmi one ( marked to dvi on my Samsung 42" set ) . Unfortunately , I get a lovely picture on the set but no way I can use the keyboard. As soon as I plug the lead into the set my computer reverts to just the wallpaper screen with no way I can use the computer keyboard and mouse. I therefore can't even go to control panel to adjust settings etc. The graphics card is an ATI Radeon HD 4300/500 series. Can anyone please give me a clue to what adjustments i have to make to get started / point out where i'm going wrong.Thank you !
  12. I am just going to go ahead and assume this is user error rather than and actual driver error. I mean AMD pulled of a lot of crap ( ), but I doubt they failed so hard that usb devices are disabled when a secondary screen is plugged. So, use windowskey+P to cycle through different desktop extension modes. Set it to "Computer only" and adjust your settings on your computer monitor afterwards the way you want to.
  13. Indeed. When this happens to me, I do the following. I swing my mouse around until I see the pointer (if the computer is trying to do a spanned desktop and I can't see the first half). Then I right-click and select change resolution/properties. Then, if the window doesn't appear (it went to the other monitor), I press alt+space, then down arrow, and then enter to select "move". This allows you to move the properties window around, even though you can't see it. Then I tap the right/left (usually right) arrow key until it comes on screen. Proceed as usual from there.
  14. I find the light gem too large, especially on my massive monitor. Also when it's bright I loose definitiions in the blacks making it harder to see in dark areas. Any way to shrink it? I made a mod for Deadly Shadows that shrank the HUD and moved elements to the very edges of the screen so it wasn't so "in-your-face", I'd like to do the same with The Dark Mod, including the tips pop-up box - this needs to be smaller too.
  15. Yeah. This is good advice and thus it did the trick. If you've been playing for a while (since the "beginning in my case) you will know this by the way things have developed; the earlier missions were not so complex and huge-epic as manymost lately. So back then we'd get a slight delay after the "loading progress" bar filt and blipped-away. Then other, bigger FMs came and took a bit longer... and on... and now it does become the kind of thing that really might put a lot of newcomers to ~panic~. I hope that the team will look at making the loading screen more truthful about the progress. And maybe even best of best to allow some of it to happen with briefing or somesuch happening on the stage? In the meantime this known known about the expected delays should be bespoken and advised about aloud. It should be mentioned in the docs and down at the docks... and maybe even right next to each "loading progress" bar.
  16. I only set the samples to 4x (and anisotropic filtering to 4x), and the ingame config has it listed as 4x as well, so I don't think that is the problem. I created the game log file like you said: http://pastie.org/8452547 . Interestingly, opening up the console brought the game out of the gray screen and back to the main menu with no problems. OP, you might try this yourself and see if it helps you.
  17. I've run into a similar problem. When the game automatically restarts after ex. installing or uninstalling a mission, the game shows only a grey screen, then hangs. I first noticed this after setting up a video driver profile with RadeonPro to control Catalyst AI and antialiasing, but removing the profile didn't affect the problem. This doesn't have any serious effects on the game, but it is annoying to have to kill the application and manually restart it whenever it resets.
  18. . . . ok. . .well that stinks. Especially as nothing I read said anything about that. It just said 'Doom 3'. Seems odd, too, when everything *ELSE* seems to work fine. Just those. . .odd spots. Well, I'll see if I can put up playing with black blobs. And if not, I guess the whole mess can go in the trash and I'll hope you all can get the stand-alone version going sometime so I can try again. How disappointing.
  19. Hiya, I've just downloaded the TDM 2.0 - excellent work everyone! Looking awesome and a true successor to the work of Looking Glass. This really is an outstanding piece of work. Anyway to my issue - The Tears of St Lucia crashes every time I try and continue on from the equipment purchasing stage. Once I hist Start Missions the loading screen appears, gets about 40% of the way through then quits to main menu. I've run the tdm_updater several times to check the files are not corrupted but it said everything was clean. Mostly the crash just takes me back to the main menu, with no error message, but once the game crashed it gave me the "hips" error that another poster ran into. I've also deleted the mission and re-downloaded it, but same issue. This is a clean install of TDM (I had previous versions on my other computer). I'm running a Haswell Core i5-4570 with 8GB or RAM and a GTX 660 on Windows 7 64 bit. It isn't too big a deal for me as the tutorial mission ran fine and I'm going to crack on with trying other missions, but I wanted to report the issue in case it was a more general thing. If there are any log files that someone could point me at I'd be happy to post them (I'm a former games developer and studio owner so I'm not afraid to get techincal!). Just to repeat: Awesome job - hats off to you all for producing such a great game and it fills my Thiefy heart with joy once more to rope arrow and pilfer with freedom Cheers, Slerbal
  20. I have small secondary monitor left of my large primary monitor. When I start thedarkmod fullscreen it starts in the left most window not the primary window as I expect it should. When I disable my secondary monitor in nvidia-settings it starts thedarkmod in the large monitor but in the bottom only filling a portion of the entire screen (tried various resolutions in thedarkmod video settings). Running Arch linux 64 bit with nVidia grahics Any ideas? Awesome project b.t.w.
  21. I don't have any knowledge about this, all I know is I tried 2 or 3 FMs and there is something wrong with the light, most obvious is about torches: you can see the flame (some black squares above supposed to be smoke but that's OK) and no light. I guess it should be one of these http://wiki.thedarkmod.com/index.php?title=Standalone_Progress
  22. This pertains to TDM 2.0 and also I have the Use Item key bound to the "C" key. I don't imagine that is pertinent to this issue but I'm just mentioning it. When ever you have a readable in-game that you can NOT pick up, you right click to read it. Then to close it you can either walk away from it which will drag it off your screen until it closes automatically or you can press the Item Use key which will close the book. If you press the Use Item key to Close the book instead of walking away from it, the Use Item key also activates what ever Item you have currently selected. Shouldn't it recognize that you have an open book and only or at least first close the book? The problem happens when you have a consumable item selected. Whenever you access a a page/a book in-game that will not go in to inventory and only opens to be read after just picking up a consumable, i.e. health potion/holywater/etc., when you hit the "use item key" to close that open book it also activates whatever item you have selected. It should close the open book first, THEN activate current item if pressed again. Obviously you can quick select lockpicks or whatever prior to reading any books that don't go in to your inventory but you don't always remember to do that. Having any item selected and closing a "non-pick-up-able" readable will use that item as well as closing the book. The game should recognize when a book is open and first close the book prior to using the item. I don't know if there is already an issue open in the bug tracker on this.
  23. The black squares are missingparticles (either the definition or the texture). Can you please open the console (^ as key, left of the "1") and type "condump tdm.txt" and then post the contents of tdm.txt here? (Put them in spoiler tags please)
  24. Restarted Old Habits and this time I looked backwards in the sewer and saw a lot of black squares coming out of the pipes - I assume that there is a leak of something there which is being corrupted (note picture has been lightened so they can be seen)
  25. Ok, can't get it to work on native without black textures errors. Probably need a symlink in that /usr/local/games/doom3 folder like you PranQster. BTW, i agree that the button recognition is buggy in linux. I had problems with other buttons. Wine works with the same install so it should be not being able to find the resources without them being on that system path (ughhh). edit: it was that, i symlinked the base dir there. Anyway to set a 'toggle run' instead of 'always run'? 'always run' prevents the creep button from working.
×
×
  • Create New...