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. Goog Evening I just loaded Dark Mod like an hour ago, and got this Problem with the missing Textures or missing dynamic light not shure, and the Smoke being just black squares. And i know there is another thread with about the same Problem, but i have the 2.0 standalone and as far as i understood i dont have to install doom to play this one, so the other thread is not realy helping me either. I tried about every button in my settings and i followed the faq Textures are missing, screen mostly black Look into your darkmod.cfg inside your darkmod folder and check that the following settings are like shown below: seta image_usePrecompressedTextures "1" seta image_useNormalCompression "2" seta image_useAllFormats "1" seta image_useCompression "0" seta image_preload "1" even if im not sure thats the same problem. if that faq entry would be the right one, i looked in the DXDIAG, but there is no way to change anything in there. Textures are missing, shadows are pitch black Try disabling the AGP surface accelerator in DXDIAG. So non of the things i tried did change anything so please help me to fix this. MFG DamKoVosh Edit: P.S. the screen is much darker then its supposed to be, but the only thing u should see is some things having textures, while others havent.
  2. I have similar issues unless I run TDM in the max resolution of my monitor (1920x1200). My former resolutions of 1440x900 and 1680x1050 both display improperly. The nvidia-settings utility used to have options for how full-screen programs were handled...whether to stretch or center the display with black borders, etc. That seems to have disappeared, so I can't test fixing it with that method. BTW. this has been going on for quite a while now and has nothing to do with TDM 2.0. I think it is mostly to do with changes to X, and not the nvidia driver specifically. I normally would not suggest running TDM in Wine. But, some games which act quirky in full screen can be controlled by forcing a graphics setting in winecfg. Example: I recently installed the game "Project IGI" in wine. I had some issues with display sometimes when launching the game full screen. It would sometimes display no graphics, but audio was fine. In winecfg, I made a config for IGI.exe with the following Graphics tab options set: Auto grab mouse = yes Allow the window manager... = yes Allow.... = yes Emulate a virtual desktop = yes and set to 640 x 480 The IGI game itself is set to run full screen in max resolution. Now the game launches to the main menu properly in a small window. Then it goes to fullscreen properly when missions are launched and back again when done. All display issues go away and the game (not) changing resolutions no longer re-sizes my plasma desktop panels.
  3. 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.
  4. Hello everybody, I'm RS-STALKER and I just joined. I have to say what you guys did with this mod is simply amazing, nothing short of brilliant. Every single one of you who worked o this mod is awesome and I simply love it. However I do have some problems and hope some of you guys might help. Some fan missions won't start, I haven't tried all of them but I have run into two fan missions that won't start. One is Alberic's curse where no loading screen comes up, and the mission simply won't start. Another is the mission, Business as usual, the game freezes and crashes every time I try to play that mission, particularly when i press the start mission button. I have noticed though, And I don't know if this might be the problem, that both these missions have a introductory screen with the fancy arrows and "X" at the bottom. No other mission that I've played (that worked) had such an introductory screen, But the mission that I did want to play that did have that particular introductory screen, wont work because the loading screen just won't show. If any of you guys have some solutions I implore to please share it, cause I'd really like to play these missions I have windows 7, 64 bit, nvidia GTX 560 graphics card, core i5 intel cpu, and 8 GB of ram, and currently using the dark mod version 2.0
  5. Heya, I've been playing this great mission by Goldwell and while it was really enjoyable, I've encountered a few minor bugs(at least I hope they're minor O_O), and a major one. 1.) There is a safe in the office of the third floor(one with lion head ornament), which contains some loot. I was able to pick up all of it except a single purse with some spilled coins. No matter which angle I tried, couldn't pick it up for some reason, even after restarting TDM few times. 2.) There is an optional objective of putting a certain orb into a cauldron. Apparently, it should start some sort of cutscene, but nothing happens. 3.) Watched a video on YT by FenPhoenix, in which he put a rat into some sort of stew, and the protagonist said a funny line. Tried to put the rat into stew, but nothing happened, except the rat glitching through the pot, rotating furiously for a few seconds. 4.) The final and most severe one I've encountered. After finishing my objectives(except the orb ritual -_-' ), I appeared in a train after being teleported. The end credits started to roll, and the screen remained black. The mission didn't finish, and I could still hear my footsteps, sound of drawing my weapons, but there was no HUD. Tried reloading bunch of times, but no results. I'll try to dash through the mission again tomorrow, hopefully it'll work. Cheers! (^__^ ) (\_/) <-----crappy whale
  6. Thanks for replying. I was running darkmod.x86 on a 32bit OS (as I mentioned). Have tried the 64bit version on a 64bit OS and it is no different. I do need to set the screen resolution when running full-screen else it locks up. The Darkmod.cfg must be an older one I reverted to after playing with settings. With the correct resolution the main menu displays (on linux, but not XP), but I cannot install a mission. It doesn't crash, it just won't let me start a mission.
  7. Ok, I can reproduce it on my machine on 2.06 x64 build. I simply set "Fullscreen" to "No", then "Screen Size" to something like "1280x720" and click "Restart Game". It restarts and shows a properly sized window initially (for half a second), but then it quickly switches back to fullscreen with original resolution. If I stop the game and then start it freshly, it also does the same: switches to fullscreen. Indeed, the game is alt-tabbable. But it covers full screen and it is not possible to see it alongside other stuff, e.g. DR. This happens for me only when r_useFBO and antialiasing are both enabled. When I disable either of them and restart engine, it runs in windowed mode. The situation is further complicated by the fact that disabling r_useFBO is not easy for NVIDIA user , because he also has to disable soft shadows beforehand (and the only way to guess it is to read the 2.06 release notes ) Given the mess with configurations which we have in 2.06, I think this is not an urgent issue. I'm glad that everything works properly and nothing crashes I suppose that instead of fixing this with introducing yet another hack, we should move steadily to FBO-only renderer with proper multisampling support. On the other hand, this issue is probably worth tracking anyway.
  8. Well well well. I don't know which of those settings made the difference (r_glCoreProfile is set to 2, by the way), but it seems to work properly now. Do you want me to try recreating the problem to determine which setting was important, or shall I just take this as a win? I've attached the console log file, there are quite a lot of warnings on loading, but maybe this is normal? Otherwise looks ok to me. For this log I just started the map, let the conversation finish, saved the game, checked the menu screen was working, climbed up towards the generator and onto the open window ... and fell to the ground while trying to enter the window! Looking forward to playing this properly at the right time. I'll also attach my .cfg file, but there's nothing interesting there, I reset it. darkmod.log Darkmod.cfg P.S. What do those .cfg settings mean and do? I couldn't find anything relevant with a quick use of google. P.P.S. Thank you for the help!
  9. First, please update your video drivers to the latest version. (to, at this moment version 390.65) Then check if the problem still exists. If so, could you post an application log for us? First check if there is a darkmod-log-file in your tdm folder. if so, open the file with notepad and copy its content to this topic in a spoiler-tag. If not, please create one and please post its content in a spoiler-tag. (See wiki article: Debuggin _TDM systemerrors) Tip: use my tdm launcher to load TDM executable with the arguments) And how about running tdm temporary, windowed and/or low sreen resolution? see instruction in topic: running-tdm-results-in-black-screen - entry406879 - edit - Using tdm arguments: +set r_customHeight 600 +set r_customWidth 800 +set r_fullscreen 1 (or select the options in the tdm launcher) We got also a wiki, with some solutions: http://wiki.thedarkmod.com/index.php?title=FAQ#Troubleshooting http://wiki.thedarkmod.com/index.php?title=Installation
  10. Arch Linux, stable build, amdgpu drivers (rx480), GNOME-SHELL DE, primary display 1440p144hz, secondary display 4k 50hz. Upon launching the game, display settings are altered from join-displays to mirrored. Also, fullscreen is impossible when attempting to run the game with the 4k screen as the primary display.
  11. I've deleted tdm_base01.pk4 and run the update again. the problem still appers, only difference is, that the blackscreen is coming a later. for the first 2 or 3 seconds you can see a grey screen now. the driver version is 8.970.100.9001 (see screenshot) I tried to update it but it always says it's the newest one. I really think the only way to solve that problem is to buy a better grapic card.
  12. I've been having a few issues with a dual monitor setup. I first tried playing in full screen mode. This was pretty bad. I couldn't control which monitor the game was shown on and the other monitor was disabled completely. When I closed the game, all of my other open windows were all on the same monitor and I had to put each one back the way I'd had it before. Then I played in windowed mode and made it fullscreen in the windowed menu. This is better: I can choose which monitor to play on and my other windows stay where I put them. However, the video settings are changed for the other monitor. Is there some way to make the video settings only affect the game window? I have some stuff open on the other screen and the colors are all messed up until I close the game. Also, there is no way to release the mouse from the game while a mission is loading. When I am in the menu, I can press the ~ key. This opens the console (which I don't care about) and releases the mouse. When a mission is loading, this does not work. Is there some way to release the pointer while a mission is loading? I am using the GeForce 1060 graphics card with nvidia driver version 390.42
  13. freyk, I performed the following from the link you noted: sudo dpkg --add-architecture i386 sudo apt-get install libc6:i386 libstdc++6:i386 libx11-6:i386 libxext6:i386 libxxf86vm1:i386 libpng12-0:i386 libasound2-plugins:i386 libgl1-mesa-dri:i386 libgl1-mesa-glx libgl1-mesa-glx:i386 libglapi-mesa:i386 libglu1-mesa:i386 wget unzip sudo mkdir -p /usr/share/games/darkmod sudo chown -R nobody:users /usr/share/games/darkmod sudo chmod uga+w /usr/share/games/darkmod exitI moved all of my darkmod files to the new directory (which makes sense), reran 'tdm_update.linux', made 'thedarkmod.x86' executable, and tried to run it again. Again, black screens, which were mirroring each other when I exited the program. I changed the darkmod.cfg as shown in my first post, and ran 'thedarkmod.x86' again. This time, a black window. Here is my new console dump: Any thoughts?
  14. Judging by that particular monitor's response time (5ms) I would say its a TN panel and this is just something that goes along with TN panels in my experience. Regardless if you're using 32bit color output in Windows/Linux, the monitor is limited in its color spectrum as are all 8bit panels. 10bit panels can provide the full color gamut but they are prohibitively expensive. Also, since its an older monitor, it more than likely has CCFL backlight which is something else that hinders proper black color reproduction. LED backlighting is much better at producing black blacks. Looking at your screen shot and owning 3x TN panels myself, I don't personally see anything different about it vs. mine so my advice would be.... get used to it? You can possibly tilt the monitor either UP or DOWN a bit to alter the colors shown on the screen. just my 2 pennies.
  15. according to the inventory script the compass hud model is drawn in its gui window each frame, its probability this that's throwing off the video capture software. would depend on which order the capture software picks up on frame draw order. Although you would think the video capture software would stay on the bigger screen size. Think of all the games that have extra small screen items drawing each frame inside the bigger main screen.
  16. Ok, well although I got it working 1920x1080 in fullscreen at 16x9 ratio, I can't play missions. All my missions show up in the list, but whenever I install one (and tdm restarts), it says Mission Installed: "" i.e - it's blank. However, I have the option to start the mission, but then I get this error. So.. what's going on? I have deleted my entire dark mod folder and replaced it with the one I originally downloaded, but it doesn't make any difference. The FPS counter is still enabled by default as well. Plus, when I try to use the tdm launcher after a mission is installed, I don't see the usual dark mod initial loading screen. Instead, I see the regular doom 3 loading screen (with the planet), but then the dark mod appears to load, but the screen is now black. So yeah.. I don't know what's going on. Sometimes I get a black screen and sometimes I don't, but I can't play any missions regardless.. : ( Maybe simply deleting my darkmod folder isn't good enough? I noticed that there were some additional files installed to my doom 3 base directory, but I'm not sure which ones they are, so maybe someone could tell me how to completely uninstall darkmod? Or if you know what's causing my problem and how to fix it, that'd be great as well..
  17. Nice! I never paid much attention to the render scale option, I assumed it was just something for DPI scaling. We'll still have to grab the screen resolution at startup but everything else should be simplified after that. I'll look at the Windows code for comparison of the logical results. Taking care of this should lead to a better first impression and overall experience on Linux.
  18. Feel free to remove screen resolution change code COMPLETELY and just maximize the window. That's what happens on Windows since a few years ago. The engine now renders 3D in offscreen framebuffer and its dimension is controlled via render scale GUI option. I'm sure the less legacy burden we need to carry on Linux, the better for everyone.
  19. It was easy enough to find the relevant code so I took a first look at this. Here's what I found: On Windows, there's a function to get the current desktop screen resolution and use it on first run. On other platforms that function is a no-op and you end up with an 800x600 resolution by default. Without going into details, this function is called too early in the startup process for it to work on Linux. I've got 2 possible ways to work around this that I'm trying out. The current mode-setting code for choosing a resolution uses the original, old-school X API calls. These aren't very multi-monitor friendly and librandr has superseded these calls for quite some time now. Since the platform-specific windowing code is really self-contained, I don't think it will be too hard for me to swap it out and see if things improve. The same area of the code already sets some X Window hints, I believe I could tack on a few more here to create a borderless mode equivalent as I previously described without much additional effort. It seems like this is more or less what several other fullscreen applications do on Linux too.
  20. I've actually got the same situation with dual-monitors on my Linux desktop. I was recently reminded that this happens out-of-the-box by wiping settings for the 2.08 beta (where it does still happen). The workaround I've always used is to run it windowed at the full resolution of my monitor. Then (in KDE at least, I'm sure others have similar settings), apply window- or application-specific properties to select a monitor, remove the window border, and disable compositing. This also has the benefit of letting you access your other monitor whenever you open the in-game console. I believe there are some window manager hints that we could set to automatically achieve this, this sounds about like the Linux equivalent of "borderless" mode anyways. I don't think the poor experience is a driver-specific issue, just the fact that multi-monitors in linux has always been a pain, and also changing the resolution on the fly tends to ruin your desktop even if the program is nice enough to change it back for you afterwards. It might also be better to detect the current resolution on first run and use it by default instead of resizing to whatever the current default value is. I think forcefully changing resolutions like that was more acceptable back when Doom 3 came out than it is now. As far as X vs Wayland goes, fullscreen is one of the areas where native X vs the XWayland compatibility layer may not work identically. I'd expect XWayland to disallow some of the more invasive screen resolution changes, but I haven't really played with it to know for sure. For reference, here are my relevant specs: OS: Arch Linux Graphics driver: AMDGPU Desktop: KDE (plasma5) using Xorg I could do a little research and see if there are any modern guidelines/best practices for fullscreen on Linux and at least make some recommendations. If I get enough free time I might be able to look at the code as well.
  21. I guess it's also a problem with S3TC: Checking portable OpenGL extensions... v - using GL_ARB_multitexture v - using GL_ARB_texture_env_combine v - using GL_ARB_texture_cube_map v - using GL_ARB_texture_env_dot3 v - using GL_ARB_texture_env_add v - using GL_ARB_texture_non_power_of_two v - using GL_ARB_texture_compression X - GL_EXT_texture_compression_s3tc not found v - using GL_EXT_texture_filter_anisotropic maxTextureAnisotropy: 16.000000 v - using GL_EXT_texture_lod_bias v - using GL_EXT_texture3D v - using GL_EXT_stencil_wrap v - using glStencilOpSeparate X - GL_NV_register_combiners not found X - GL_ATI_fragment_shader not found X - GL_ATI_text_fragment_shader not found v - using GL_ARB_vertex_buffer_object v - using GL_ARB_vertex_program v - using GL_ARB_fragment_program X - EXT_depth_bounds_test not found It's strange because my hardware/software actually supports S3TC. Could it be I would need to install libtxc_dxtn for 32bit? The solution from the FAQ doesn't work: seta image_usePrecompressedTextures "1" seta image_useNormalCompression "2" seta image_useAllFormats "1" seta image_useCompression "0" seta image_preload "1" Besides, I've got a completely black screen, not a "mostly" black screen.
  22. Checked Nvidia control panel, nothing looks forced, things are left up to applications. The updater was crashing instantly so I tried a fresh copy of the game, updated, same problem in the game even with default in-game settings. I can get one or two 1 frame flashes on the pre-mission screen, then just black. If I can find any solutions on my own by messing with things, I'll post it.Found the problem (sort of). Alberic's Curse mission was causing the problem. Other missions work fine, but the pre-mission menu for that one mission causes a black screen. No idea why, I'll try uninstalling it and re-downloading it.
  23. I'm afraid i'll need to find some free screen recording software. In the meantime i've done two screengrabs which attempt to show the issue. Not too clear though i'm afraid. If anyone could recommend some open source screen recording software for windows i'd appreciate it. thanks.
  24. Yes, that was just for the test. You can make it 1. One nice thing about TDM's screenshot facility is you can take a s/shot much larger than your screen. The s/shot does a separate render, it doesn't copy directly from your screen. If you choose a huge size, like 16000x9000, you'll see bits of the scene rendered as separate tiles that fit on your screen. Then it all gets put back together again in your resulting file.
  25. Interestingly, I don't see the problem where Grayman showed it in the training mission. But I see completely unlit pieces of walls behind "Keys and Lockpicks" and "Gamma and Brightness" doors. UPDATE: Doing vid_restart fixes those problematic sections, but breaks different places: they become completely black so that even lantern does not help. This is accompanied with GL_INVALID_OPERATION error spamming in console. I guess vid_restart is broken for a long time already, so no surprise here.
×
×
  • Create New...