Search the Community

Seems to confirm: https://bugs.thedarkmod.com/view.php?id=5718 does it happen in the latest dev build: https://forums.thedarkmod.com/index.php?/topic/20824-public-access-to-development-versions/

TTLG? That's Through the Looking Glass Forums. A looking glass fan community. Has been around for a long, long time. https://www.ttlg.com/forums/

I just read@motorsep Discovered that you are able to create a brush, then select it and right click "create light". Now you have a light that ha the radius of the former brush. Just read it on discord and thought it may be of use for some people in the forums here too.

https://github.com/HansKristian-Work/vkd3d-proton/tags <- directx 12 wrapper for dxvk https://github.com/doitsujin/dxvk/tags <- directx to vulkan wrappers D3D 9 to 11 eg. dxvk if you want to try it with horizon zero dawn you need to copy out dxcompiler.dll from Tools\ShaderCompiler\PC\1.0.2595\x64 and bink2w64.dll from Tools\bin and place them next to HorizonZeroDawn.exe. then copy over dxgi.dll from dxvk and d3d12.dll from vkd3d and place them next to it to. now fire up the game and let the shaders recompile -> profit.

I think the reason the dev forums exist is to provide a place where the implementation of features can be discussed without getting mixed up with other debates when someone believes what the devs are doing is wrong. We often post public discussion threads for features with subjective elements like the frob outline, because community feedback is very important. But there will always be vocal defenders with strong views for or against certain features, or how exactly it should be implemented in their opinion. At some point a decision has to be made and be carried through, which is what the dev forums are for. Almost all of the threads are very technical, basically explaining and discussing recent or potential code changes with other devs. Its hard to say. Its a hobby the devs do in their spare time, so people come and go when they're in the mood and when they have the time. The team page is mostly accurate except for some relatively newer additions like myself.

I just found this thread on ttlg listing Immersive Sims: https://www.ttlg.com/forums/showthread.php?t=151176

Recently revisiting the forums after a longer period of time I wanted to check the unread content. I don't know if I am doing this wrong since.. ever... but on mobile (visiting the unread content page on my smartphone) you have to click on that tiny speech bubble to go to the most recent post in a thread. If you don't click correctly you'll hit the headline and end up at post 1 in the beginning of the thread. It's terrible on mobile, since not only the speech bubble is really small and was to miss. But also the thread headline is just millimeters away from it so you go right to the first post that was ever made instead of the most recent ones. Am I doing it wrong? I just want to go through u read content a d the to the newest post from that topic.

Judging from Could not open playback device 'default' message, "default" device for ALSA is not configured properly. I hope someone more familiar with ALSA configuration could explain how to change the default.

A@datiswous Ah yeah, well sorry, I was quiet busy and only visiting discord. First time here on the forums since months now I think.. Thank you for the subtitles. I encourage everyone who is interested in using them to download it from here as I'm not sure when I'll be able to implement them myself into the mission. Again, thank you for your work.

So I am running Ubuntu 17.10 (Pop!_OS) and the sound is not working. I've seen lots of discussions on this topic but none of the solutions have worked for me. Here's a small section of the output when I run ./thedarkmod.x86 dlopen(libasound.so.2) asoundlib version: 1.1.3 Alsa is available ------ Alsa Sound Initialization ----- ALSA lib conf.c:3523:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM sysdefault:CARD=0 snd_pcm_open SND_PCM_STREAM_PLAYBACK 'sysdefault:CARD=0' failed: No such file or directory dlclose WARNING:sound subsystem disabled -------------------------------------- ----------- Alsa Shutdown ------------ -------------------------------------- Here's the output when I run aplay -l gilbert@gilbertyoder:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 And here is a few possibly relevant snippets from the Darkmod.cfg file seta s_dsp "/dev/dsp" seta s_driver "best" seta s_alsa_underrun_extrafill "1024" seta s_alsa_lib "libasound.so.2" seta s_alsa_pcm "sysdefault:CARD=0" Any help would be greatly appreciated!

To give some background context on this (based on my own understanding, although I am not an expert by any means): the libasound_module_conf_pulse.so plugin is a compatibility tool that allows ALSA-only applications (like TDM/Doom 3) to interact with modern distributions which use PulseAudio as their audio server (which is pretty much all of them at this point, I believe). The ALSA application opens the ALSA device in the normal way, and this plugin then redirects the audio to the PulseAudio server which of course is using the "real" ALSA devices as its own backend. If this plugin works on your system, it should in theory allow you to control the volume of the application via the normal PulseAudio control panels, as well as redirecting it to a particular sound device. If you can't get it to work, then configuring the game to directly use the low-level ALSA devices is an alternative, but you may in this case need to temporarily disable the PulseAudio server with a tool like pasuspender in order to make the low-level device available for use by another application. The ideal 2018 solution would be to add PulseAudio support directly into the game so that it could work flawlessly on modern distributions, but that would require someone with sufficient expertise to work on implementing it.

DarkRadiant 3.7.0 is ready for download. What's new: Feature: Skin Editor Improvement: Script Window usability improvements Fixed: Hitting escape while autosaving crashes to desktop Fixed: Def parsing problem in tdm_playertools_lockpicks.def Fixed: DR hangs if selecting a lot of entities with entity list open Fixed: Float Property Editor's entry box is sticking around after selecting a float key Fixed: Spline entities without model spawnarg are unselectable Fixed: Entity window resets interior sizing forcing resize each time it is opened Fixed: Spline curves should not be created with a model spawnarg Fixed: Newly appended curve control vertices aren't shown at first Fixed: Light entities are zoomed out in preview window Fixed: Entity inspector spawnarg fields not always updated by UI windows such as Model Chooser Feature: Skin Editor (see video) Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.7.0 and of course linked from the website https://www.darkradiant.net Thanks to all the awesome people who keep using DarkRadiant to create Fan Missions - they are the main reason for me to keep going. Please report any bugs or feature requests here in these forums, following these guidelines: Bugs (including steps for reproduction) can go directly on the tracker. When unsure about a bug/issue, feel free to ask. If you run into a crash, please record a crashdump: Crashdump Instructions Feature requests should be suggested (and possibly discussed) here in these forums before they may be added to the tracker. The list of changes can be found on the our bugtracker changelog. Keep on mapping!

Ignoring is somewhat inadequate as you still see other members engaging in a discussion with the problematic user, and as Wellingtoncrab says such discussions displace all other content within that channel. Moderation is also imperfect as being unpleasant to engage with is not in itself banworthy, so there is nothing more to do if such people return to their old behaviour after a moderator had a talk with them, except live with it or move away. I'd be more willing to deal with it if it felt like there were more on-topic discussion, i.e. thoughts about recently played fan missions or mappers showcasing their progress, rather than a stream of consciousness about a meta topic that may or not have to do with TDM. I guess the forums already serve the desired purpose, or they just compartmentalise discussions better.

Yes, it does. Which makes it interesting that you yourself explicitly said that it's interesting nobody had complained here on the official forums: I did, which is why it stood out to me so much that even though you yourself had personally been involved you would reply claiming nobody had complained here on the official forums. I'm not colorblind at all. Does that make people pointing out that almost no modern games have proper colorblindness support hyperbole? Just because it doesn't affect you, or you choose not to pay attention to the discussion of something, doesn't make it hyperbole. Pick pretty much any modern FPS and you will find plenty of discussion about the near universal disregard for FOV and camera movement as accessibility issues. Denigrating those as hyperbole because you personally don't feel the affects is as bad of a look as demeaning people who bring up the importance of valid allergen warnings like gluten or colorblindness and deafness support.

I think it is a good idea! Our ingame mission downloader and mission view has long been subject of multiple improvement suggestions. Due to the sheer mass of missions that have been released in the last 15 years, things got really cluttered and especially newcomers will have a hard time finding what they want. However, improving the ingame guis is quite a task, so a web-based application might really suit this scenario well. Maybe we could even add a linke to it from our ingame menus, so user can access it quicker. Some more things to think about Would users be able to add custom tags and downvote / upvote certain tags, much like the system of Steam? This would also allow to add tags like "beautiful", or "difficult". Actually, the more users can contribute to this system, the better, because it will be automatically maintained then. The browser should also contain a flag for whether the FM belongs to a connected series of FMs or not and have the capability to go to the previous or next FM in that series. There should also be a flag for fully fledges campaigns. Some might like a flag whether or not an FM is "ghostable".

I feel like a dumbass: installing pipewire-alsa fixed it, now I have sound. Sorry for wasting your time and thanks for the help!

I tried some, namely oss, pulse and alsa but it didn't help. I tried looking online and came across the openal-info command and something strange happens when I run it: If i run it without sudo it gives off a few errors, but lists a lot of information and even finds the correct audio outputs of my system, however if I run it with sudo it displays what TDM already showed me and doesn't find the correct outputs (running it with sudo outputs pretty much the same things TDM does). I've attached the output of both commands (Note that I manually added the error messages as they would not be redirected to the file). On a side note, I stumbled upon a reddit post of someone having a similar problem in minecraft and the solution was apparently to change ownership of the game files because it runs as root and it couldn't connect to the pulseaudio daemon which was running as the local user. I doubt that's my case (I never run TDM as sudo), but it left me wondering if there's a similar problem with priviledges and permissions on other things. openal-info-sudo.txt openal-info.txt

Ah yes: Copying alsoft.ini to an alsoft.conf makes the changes there matter. I've been playing around with some of the settings now. So if I use anything other than "drivers = alsa" I get no sound. ALSA seems to be the only one it will work with, or the others need to be further set up. Preliminary testing shows some great news: I may have found the culprit! The issue appears to go away once I set "period_size = 64". Going at the other end, "period_size = 8192" also doesn't seem to do it oddly, but that causes a huge delay for all sounds. The issue is when I set it to a middle value like "period_size = 1024" to "period_size = 4096", that's what seems to cause it almost constantly... the distortions differ slightly based on this value. I can even add other improvements like "frequency = 48000" and it works! I'll update if I still encounter it with these changes too. In the meantime please consider if based on this results, it might be a good idea to change the default value of period_size to something lower, seeing how this helps solve the problem. Any reason why it can't be 64 by default? The problem only seems to occur from 512 (very rare and brief then) and up (almost always starting from 1024), even a 256 should be safe if a slightly higher default is needed for other reasons.