Search the Community

AFAIK The only other shader that can be involved is the fullscreen_tri.vert.glsl shader but clamping the first term in the coordinates results in the render occupying a quarter of the screen.

Nope, still doing it, BUT, different behaviour now. When I hit escape to go back to main menu, then go back in game, the screen corruption is gone. But it still comes back if I look at the windows. @stgatilov

Now @AluminumHaste has the same problem: Get weird screen corruption with it on in Flakebridge Monastery.

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, RGB is RGB, by my eye... Shame about the games. // i think i just made it worse... it's like the light at the end of the tunnel...

I want to cover my whole mission in a light fog but as the topic states, I've got problems with particles, especially flames from torches and chimney smoke when these appear in front of skyportals (caulked face with a portal_sky texture in the same leaf). The particle doesn't render in these places. (Left picture below) I'm using a foglight that covers the whole mission and it have the following properties/spawnargs _color 0.06 0.06 0.06 shaderParm3 2000 textures fogs/delta1_fog Everything is nice and it has got the effect that I'm after, but I cannot see the flames/other particles as I want. It's like the fog gets so thick outside the map that it nulls out the skyportal and messes up the particles in front of it... I have tried to start the shaderParm3 on extremely high numbers and then slowly lowered it, but as I go so far that the fog is visible in the mission, the sky parts are greyed out and the flames disappear when the torch moves in front of the sky...The skybox is outside the fog light btw. As a sidenote, if I use the spawnarg "start_off 1" on the light, the skyportal doesn't work (the sky parts are just plain black). I have to remove the light entity altogether to be able to see the skybox, and a clear sky...but I want fog, dammit!

Holy hell that many! I tried "Tears of Saint.Lucia" and add no ctd's but i did noticed one thing that I didn't noticed before, the skybox was pitch black! I saw it because the water puddles reflected a starry night and I looked up and saw black. So i take back what I said about having no problems. Also this is more a suggestion when the intro for this mission starts, after some time, a tip could show telling the player how to skip it, telling him to use the action button, why, because I tried to skip with ESC and add to start the mission again.

Hi, I was wondering why the settings menu for screen resolution has for 4:3 aspect ratio resolution 1280x1024 . This should be 1280x960 . 1280x1024 is aspect ratio 5:4 . If you select 5:4 1280x1024 (this also exists) and restart, it's set to 4:3 1280x1024 and it looks slightly stretched. I tried r_customheight 960 in the console and this made it look better.

Ok, I finally got it to work, but it didn't involve either of the fixes you guys were talking about. First, I would change only these options: Screen Ratio: 16x9 Resolution: 1920x1280 Fullscreen: Yes Are you sure you want exit (Ask every time?) No (in other words, I told it not to ask me every time). Then the next time I started dark mod, black screen. Although I saw the fps counter (which by the way is rather odd in my opinion to have enabled by default..) So I went into my doomconfig.cfg and started changing everything back to default settings. Still black screen. (Weird, huh?) Next, I overwrote the entire darkmod folder with the one I had originally downloaded (unaltered). It worked, but I had the same problem as in the beginning (wasn't full screen, lower res, etc.) So I begun changing options again, restarted, and black screen. Then, I simply the darkmod.cfg from the original, unaltered darkmod folder that I downloaded, and overwrote the one in my darkmod folder, and then it worked! Although oddly enough, it was still set to 1920x1080, 16x9 and fullscreen was enabled when I started dark mod. I thought it would've overwrote it back to default settings (1280x720 and whatnot), but it didn't. Instead, it worked. Although it did seem to forget that I told it not to ask me if I wanted to exit for some reason. So whatever. I'm just glad I got it to work. Although I think something strange is at play here.. Edit: As a side note, it'd be nice if there was a "mods" option on the front end dark mod menu so that I could switch to another mod. I modified my doom 3 shortcut to start right into darkmod, but unfortunately I can't switch to other mods after I do that, so I may just take that out for now and switch to darkmod within another mod.

Hello, I'm new to the dark mod. I just installed it and I can't select any missions. None show up in the available mission screen even after downloading a couple fan missions. It kinda seems like the missions are there, just invisible. But selecting them and clicking the install mission button only restarted the game and didn't do anything. I tried using different versions of The Dark Mod like 2.09, 2.09a, 2.09b, and the latest 2.10 beta and none of them made a difference. If it matters, my pc specs are AMD Ryzen 5 2500u, Radeon Vega 8 Graphics, 8 GB Ram.

But those logfiles dont show any video startuplines. So i keep advising to use the arguments. Its nice to hear you get tdm running, but I (or we) want to see how tdm loads your video driver How about the following command: thedarkmod.exe +condump mylog.txt and post the content op mylog.txt a tutorial to get tdm with startup the arguments running: hit the keyboard combination "windows + r", enter the following line and click on ok: c:\games\darkmod\thedarkmod.exe +condump mylog.txt +quit (assuming thats your location of the darkmod folder) or hit the keyboard combination "windows-key + r" (or search for "cmd"). a new window will apear, enther the following command in that window an click on run: cmd a new black window will apear. navigate to your tdm gamefolder by typing the following line in the black window and hit enter-key: cd c:\games\darkmod then enter the following line and hit the enterkey: thedarkmod.exe +condump mylog.txt +quit this will start tdm, generate a logfile and close tdm. open your windows explorer go to your the dark mod folder, search for mylog.txt, open it and copy its content in a new forumpost.

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 previous "look" no matter what settings for brightness / gamma / contrast. Also, Nvidia DSR (ie, squeezing 4k resolution down into 1920x1080) now totally screws TDM. Can't even get onto the menu to change the resolution to native. Had to fix resolution down to native via config files. Have noticed issue in several older games, notably Farcry2. Game appears bleached out, unless xml edited to start game in windowed mode and and alt+enter to make full screen, resolution changed back up to native or 3840×2160 for DSR, DX 10. No vibrance. Some contrast can cause black spots, specular and shadow-cast affected. Draw distance for certain things (eg, certain lamps) has changed. Splinter Cell appears to be more vibrant, have higher contrast (very dark shadows and very bright lights). Inside TDM, this has resulted in some very weak shadows with very sharp edges. Can be difficult to discern light/dark areas (esp. for players like me who play without light-gem) Colours are more vivid, that's for certain. Screenshots appear normal - it is only "live" that this occours (like the migraines it induces). Same for all the games. Worse, it's affected colour reproduction in many graphics applications. Either that or my screen is broken and my printer profile has decided to turn 50 shades of darker in the past few days. For some reason it's also thinking I have two wacom tablets attached to the machine, instead of one... Think it's windows more than Nvidia... Icon cache is screwed on desktop - need to f5 to see new files. File explorer windows are resized after exiting affected application / game. Some processes need killing through task manager and refuse to exit... Might nuke the installation - no-one else appears to have noticed it. Checking if anyone else has (win10 insider with nvidia 980ti that used to have perfect colour profile).

I run MSI afterburner and have a gigabyte graphics card. It is a good app for capturing video,screen shots or overclocking and displaying real time data on the screen for the active graphics card/cards and will work with most cards. I have found one weird bug where if I select the compass in TDM the OSD ( on screen display ) moves the OSD type on the screen temporarily as if I changed the display resolution. It does not seem to effect anything really but it's curious and needs to be seen. I tried to take a screen shot and it's not working properly. This is what I end up with but not what is displayed on screen during play: https://skydrive.live.com/redir?resid=F7539D361BD41522!188&authkey=!AIBZiw_9kt8S8Mc

I've been optimizing my map to boost fps from in a lot of cases 25-30 to 45-65, doing this systematically. I have a newbie perspective, this being my first FM - so .... be kind. First off, when building the .map I began by dropping in shadow/no_shadow lights with zero care - just looking to light the areas being worked on. Same for entities, dropping them in with little care except for aesthetics and creating shadows for the player to hide in. That procedure made for a very unoptimized map. So, what's been the optimizing plan? First, clean up the geometry. Second, go thru' the map section by section, setting shadow/no_shadow on entities. There's a tradeoff: complexity of geometry multiplied by shadows gets out of hand, so a lot of care needed here. With a first pass on that done, redo the lighting. I eliminated all the small ambients I'd put in, whether shadowcasting or not, leaving just those lights attached to fixtures of some kind, which I wanted to be in general shadowcasting. I reset these shadowcasters to not overlap so far as viable. I was amazed to find that this made for a much much better looking map coupled with much more acceptable frame rates. I use hide_distance on entities sparingly as I don't like the pop-outs. Not at all! My map has a lot of transparent windows/doors. I use func_portals with hide_distance set on every one of these. Controlling pop-outs caused by func_portals is fairly simple. The func_portal pop-outs tend to be marked by abrupt lighting changes. These are very ugly and getting rid of them or making them unobtrusive is a priority. I cant see using any kind of light pop-out/pop-in spawnarg. Rather, I could see using a shadow/no_shadow hide_distance setting, which could be used more universally and quite unobtrusively. If that's possible now, please tell me how! Also, I could see using a fade-to-black hide_distance on lights, so there'd be no lights a popping.

Using the latest dev build, I'm noticing some of the default assets have issues with missing shaders or skins even certain meshes. Some entities appear as black boxes in-game whereas certain skins for good models come out as transparent white surfaces instead of a proper texture. I figured I should make a thread for reporting these seeing the issue is rather widespread to quite a few of the default models and entities. Here's one to start off with: Create an atdm:ai_mage01 then give it the skin plain_robes. The outer coat looks fine but the inner clothing causes ghosting.

@duzenko Yup, now the mirror is working, but the shading issue has also reappeared on the silverware (I'm not sure if that is something you've been working on or not): Another thing which I could mention (which is completely unrelated) is that my system mouse cursor is visible and overlayed on top of the game and if I move my mouse in any direction, the camera stops when the cursor reaches the borders of the screen.

Solved (sort of)! There is evidently a minor bug in the way skybox tdm_sky_starry1 works with portal sky. The somewhat different tdm_sky_starry2 doesn't suffer it. The bug is not typically visible due to ground structures and clutter. To reproduce the problem: 1) Start a new project, with a hollow box as a room (e.g., 512 units per side) 2) Texture the sides with portal sky, except give the floor a typical (not too dark) texture. 3) Outside the room, create prefab nature/skybox/tdm_sky_starry1.pfb 4) In the room centroid, create entity Lights/sources/atdm_ambient_world. As usual, extend its scope to all the room. 5) For easy bug detection, change its colour spawnarg to be something too bright, e.g., RGB(255,255,255). 6) Set the player start, then save, dmap, run. 7) Run the player around the floor perimeter, with the black sky to the player's left, and the player viewing the floor. As you move the player around, look for a small square in the lower-left corner of the screen, when that corner is over the portal sky texture. It's as if it's the view of a high-contrast security camera (attached to the player's chin?)

When a user run the updater, the developer of the updater inspects the user that uses a stable to internet and tdm mirrors. You could create code to download files from a mirror, change the weight of some mirrors in the the tdm-mirror list. Does the tdm updater for linux, generates screen-output, a tdm-mirror file and tdm-log? If so, check the screen output, content tdm_update.log. And change mirror selection in the tdm-mirrors.txt. (dont forget to use the startup arguments of the updater) My advice is to read the installation manual on the wiki, check my code on my github page for the deb/rpm packages, look at the needed dependencies & write permissions. Compare all this with the aur (and the excistings aur's). Also look into other archlinux topics in this subforum. Manual for installation tdm on linux: http://wiki.thedarkmod.com/index.php?title=Installer_and_Manual_Installation#Linux http://wiki.thedarkmod.com/index.php?title=The_Dark_Mod_-_Compilation_Guide I have some experience by trying to create linux rpm/deb packages, but its not much to help you.

Last issue I'm personally aware of, please report any others here if you've seen them. In the bushes category there's one entity called atdm:nature_bush_large_3 which has an invalid model and appears as a black box. All other bushes are fine on my end and it's just this one that has a problem.

With a currently .tga background and default darkmod.cfg cvars from updating to the main menu beta: Can't see an image_compression cvar in my darkmod.cfg, and the console doesn't seem to know it. My other seemingly compression-related cvars are: seta s_decompressionLimit "6" > seems to be something for audio files (max uncompressed sample length), so I didn't experiment with it seta image_usePrecompressedTextures "1" > setting this to 0 has no effect on the background and turns pretty much everything else into black rectangles/screens seta image_useNormalCompression "1" > setting this to 0 has no effect seta image_useAllFormats "1" > setting this to 0 has no effect seta image_useCompression "1" > setting this to 0 cures the problem. As sharp as ingame. Yes, I tried it in .tga, .dds and .jpg and made sure I didn't have both a .tga and a .dds in valid locations simultaneously.

So I tried the newest beta driver for 6850 (I only tested with the WHQL the first time) Honestly I expected the same black GUI but AMD managed to get over their assheads with that one It just... crashes on qglGetProgramiv(... GL_LINK_STATUS ...) with the manylight shader Thank you, AMD, for setting the eternal gold standard in shit baths driver quality reputation

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)

Under which exact circumstances does the game crash? Does it crash before you see loading screen, while you see it, or after you "click attack to start", or somewhere in game? Does it happen on New Job mission? The condump that you attached does not witness the crash itself. It would be great to get condump with everything up to the very point of crash. The only way to achieve it is to open Darkmod.cfg, find the line with logFile, and change it to seta logFile "2" (UPDATE: it seems it is already set in your config file). Then run the game on New Job FM and reproduce the crash. Then find the log file at fms/newjob/qconsole.log.

Yet another reason to not mess with desktop screen resolution

I edited my previous post with the updated log. I can only dump the log when I'm on the first screen after loading the mission. The console won't open when the screen goes black.

I (and we) have not read your darkmod logs yet, studentmaniac. And i still want to read them, because capability check written in them and can show other things. (and if there is a driver issue, we can also see that in the log. Than we have proof) "I'll not go fiddling with codes and notebook as I am naïve and technologically illiterate when it comes to these things." Please hold on! Then I write some easy instructions for you, which i did also for other people. instruction: open the file explorer and go to your darkmod folder. open file darkmod.cfg (right click > open with > notepad), look for value for setting "seta logFile", change the value "0" to "2", and the save the file. open file "currentfm", change its content to "training_mission", and the save the file. open a command prompt/powershell window in the tdm folder: In file explorer > click on menu "file" > open in powershell. Or in file explorer, hold your shift-key on keyboard and right-click in a empty space (shift+right click), > in the quickmenu select "open powershell / command prompt" here Or hit windowskey+r to open the execute window. input "cmd" and run.This wil open the black command prompt window If the game is located at c:\games\darkmod, enter the following line and hit the enter-key: cd games\darkmod Then run the following command by entering the following line and hit the enter-key: .\TheDarkModx64.exe +condump tdmwontstartlog.txt +map training_mission +quit this automatically start tdm, create logfile tdmwontstart and quit. This create a file "tdmwontstartlog" and we want to see its content. Open the file and post its content in the topic, or attach the file to the topic. (You can also look if there is a qconsole file in your fms\trainingsmission folder, but i doubt it.) end.