Search the Community
Showing results for tags 'settings'.
Found 4 results
Hi, If I change the setting "Edit" -> "Mouse Settings" -> "Camera View" -> "Paste Shader Natural" to SHIFT + AUX1, I cannot use the Paste Shader Natural functionality. AUX1 is the button used for 'go back' in browsers. It works in other programs. It seems to be the same issue for AUX2 ('go forward'). I also tried changing other MMB bindings to AUX1 (Pick Shader, Paste Shader Projected) with the result that they did not work. Also tried with another mouse, with same result. If I set it to something else, e.g. shift + right mouse button, it works as expected. On Windows 10, 64 bit. DarkRadiant 2.6.0 x64
PJMaybe posted a topic in TDM Tech SupportIs it possible to copy the file with the settings info on so I don't have to configure controls when I re-install? Which file would it be? Thanks
How to configure the sound system on Linux
MirceaKitsune posted a topic in TDM Tech SupportEver since I first installed TDM on my Linux machine, there has been just one problem that would never let me enjoy the game in peace: The audio system. Sound will either simply not work, work but constantly flicker, or lag behind as the game goes on. Every now and then I had to adjust the sound settings to get better results... and in doing so I got a hang of what the possible configurations are. I decided to share this info here, for others who are struggling with untangling the buggy sound system. In essence: If you are running The Dark Mod on Linux, you have 3 options for sound, each with its own potential set of problems: PulseAudio, ALSA, or OSS. PulseAudioThis is what TDM will try to use by default, when s_driver = "best" and s_alsa_pcm = "default". This is theoretically using ALSA, but the PulseAudio device instead of specifying your own. Sticking with this option should guarantee that the correct audio device is used, but it has one problem: Sound flickers and lags. Solution: The only easy solution is increasing the PA latency for the console you're running TDM in, by modifying an environment variable. Simply run the engine as follows... you can also put this in a TDM.desktop shortcut to do it automatically: "export PULSE_LATENCY_MSEC=60;./thedarkmod.x86". ALSAIf the above doesn't work out for you, the second best option is selecting your ALSA device manually. It should guarantee that there are no sound issues and you get the best playback. The downside is that pointing it to the right audio device can be tricky and might not work at all sometimes. Solution: First make sure that s_driver = "alsa". Then up open bash and type "aplay -l" or "aplay -L" to get a list of your audio devices. Identify the name of the one you wish to use, then set s_alsa_pcm to it. For example, you will want to have something like this: s_alsa_pcm = "front:CARD=Intel,DEV=0". Alternatively you can use device numbers directly, such as "plughw:0,0" or "hw:0,0". Simply using "sysdefault" instead of "default" is also said to have solved the problem for some. You might have to try all of these options and devices until you find the one that works. OSSIf both of the above options fail, OSS is the third path to take. The good part is that it might work at all... the bad part is that it's mostly deprecated nowadays, meaning your distribution might not support it or it can produce sound issues of its own. Therefore this should be considered the last resort. Solution: Set s_driver = "oss" in the settings. You must also run TDM through aoss for audio to work now, so set your TDM.desktop shortcut to: "aoss ./thedarkmod.x86".
Render Quality Tests
delatroy posted a topic in TDM Tech SupportI've got an Nvidia GTX670 and I'm wondering what affect the Nvidia application settings via the Control Panel has on TDM render quality. In TDM everything is maxed - 16x AA and TA with the resolution set to my monitor's native 1440x900. I then did a few tests using the following settings on TheDarkMod.exe in the Nvidia Control Panel as follows: Default - nothing changed - everything left on "global setting" Only one setting changed - forced 32 CSAA - presumably this overrides the 16x setting in game All application settings overridden and set to their max I took a screenshot from a saved game on each setting and zoomed in 200% so you can see better what's going on (zoom out to 50% in your browser to see the images to original scale). Look to the far right of the image to see the biggest differences. Results are shown here: It's subjective but my feeling is that either the default setting or 32CSAA gives the best results while everything maxed looking the most rough. If you keep your eye on the lower edge of the black step, you can see jagged black and white edges on the maxed settings. Perhaps the forced AA and TA isn't actually working for some reason even though we've told it to max. The 32CSAA setting appears to smoothen everything overall while losing detail which you may or may not prefer on the whole. I may need to play with default and 32CSAA to get a feel for them before deciding which I prefer.