greebo

Thanks for these words, I appreciate it a lot. For some things I guess it's better not to look at how it's done in DarkRadiant and to keep an open mind for better architecture , but overall it has come a long way since we forked GtkRadiant. As far as development is concerned, I guess you're already doing a good job, so just keep it up. As usual in open-source development, the most useful fork will gain popularity, so I think we don't need to keep merging back into my upstream repo. But it might be useful to sync up with OrbWeaver's fork over at gitlab.com from time to time, and vice versa. As far as releases are concerned, in the past I just picked a suitable time between a couple of fixes and new features to call it a new release. I have some scripts and installers helping me do the thing on my local machine (but this is all Windows based and probably not of any use for you). There's also the darkradiant.net domain which could go into better hands, I'm still holding the domain account for that. (And before I forget, I've picked up from the wxWidgets release notes that there might be some sort of dark mode implemented for the Windows port, I know some around here might be quite happy about that.)

The website is this Git repo here: https://github.com/codereader/codereader.github.io After pushing something, an automated action will take care of deploying the Jekyll site to github.io. That has all been done out-of-the-box by Github templates, I didn't have to do much other than setting up the DNS. There's an A record and a CNAME which point to github or codererader.github.io, respectively. It's been years since I set this up, but I'm sure there's an up-to-date guide on how to host website content on github.io. I'd almost bet there's a similar solution is offered by gitlab.com, probably it's just the DNS record which needs changing.

@func_klaus Nice additions to DR, Klaus. I looked through all open PRs and merged them, good work. And I love the username, btw. I'm really happy to see that DR is getting some attention. It's obvious that I can't spend much time on anything here. I wouldn't be mad about someone like you taking over the DR repositories. You have everyhing in your fork anyway, the only thing would be the DarkRadiant website which is hosted at codereader.github.io. Maybe this could be handled by OrbWeaver. @OrbWeaver Not sure if you're still around these days, but I guess when it comes to me handing over things, your voice should be heard too. By the way, my phone says it's 2026 - my first commit to DR was on Oct. 9th, 2006. That's almost two decades, a fitting time to pass stuff on after. I wouldn't have believed anybody telling me that the TDM or DarkRadiant would still be used after 20 years, 17 years after TDM had its first release. Kudos to all you mappers, it's all because of you!

DarkRadiant 3.9.0 is ready for download. What's new: Feature: Add "Show definition" button for the "inherit" spawnarg Improvement: Preserve patch tesselation fixed subdivisions when creating caps Improvement: Add Filters for Location Entities and Player Start Improvement: Support saving entity key/value pairs containing double quotes Improvement: Allow a way to easily see all properties of attached entities Fixed: "Show definition" doesn't work for inherited properties Fixed: Incorrect mouse movement in 3D / 2D views on Plasma Wayland Fixed: Objective Description flumoxed by double-quotes Fixed: Spinboxes in Background Image panel don't work correctly Fixed: Skins defined on modelDefs are ignored Fixed: Crash on activating lighting mode in the Model Chooser Fixed: Can't undo deletion of atdm_conversation_info entity via conversation editor Fixed: 2D views revert to original ortho layout each time running DR. Fixed: WX assertion failure when docking windows on top of the Properties panel on Linux Fixed: Empty rotation when cloning an entity using editor_rotatable and an angle key Fixed: Three-way merge produces duplicate primitives when a func_static is moved Fixed: Renderer crash during three-way map merge Internal: Replace libxml2 with pugixml Internal: Update wxWidgets to 3.2.4 Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.9.0 and of course linked from the website https://www.darkradiant.net Thanks to all the awesome people who keep creating Fan Missions! 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!

Thanks for doing the digging. Libxml2 is so widely used, that it's hard to imagine nobody else has this kind of trouble, so I'm still thinking it must be in the way we use it. Also, why just in Linux, it all doesn't make much sense. I agree it's not worth doing more investigations when an easier alternative is at hand. Yes, I'd add them to the libs, and I'm probably going to set the PUGIXML_HEADER_ONLY flag, at least in Windows.

I took the liberty to change the title of the existing issue and link it to this topic here. https://bugs.thedarkmod.com/view.php?id=6472

Oh boy. Thanks for investigating this, reading the issue description I suspected that the XPath queries might be failing, but I thought it was rather due to the libxml2 version used in newer Ubuntus. I recall now that the automated Ubuntu build on Github is not running the unit tests (couldn't get it to run and gave up at some point) - so I missed that this is breaking stuff. I searched around for existing code to find out what to pass for that encoding parameter in xmlReadFile, but I couldn't find anything useful, everybody seems to pass NULL as argument, which I ended up doing too. I'm all for that, I was that close of doing it when I upgraded libxml2 for Windows. As long as it's supporting XPath and XML Tree manipulations, I'd go for the most light-weight one, maybe even header-only. Our libxml2 usage is confined to xmlutil, so it should be possible to switch. edit: I'd vote for pugixml, it seems to be still alive and has XPath support. It's what I've been using in the TDM game code too. But still, if it's the tree manipulations that break the queries, we can either try to find out what we are doing wrong here, or move away from pushing the .game data into the registry trees - it might not be necessary after all, since most (if not all) code is relying on the GameManager interface to get do the queries. For the moment being, I can revert the change to xmlReadFile, so that my repo is functional again. Are you still investigating this? You seem to have gotten quite far already.

You can create shortcuts to DR, passing an fs_game=your_fm parameters to DarkRadiant.exe, e.g. DarkRadiant.exe fs_game=fms/yourmission It will override the setting saved to the user.xml file in your settings folder. Works with fs_game_base as well.

Since a few versions the settings are saved by minor version - so DR 3.7 is storing its settings in a "3.7" subfolder, and DR 3.8.0 is saving them in "3.8". (DR 3.7.1 and 3.7.2 would use the same "3.7" folder.) Settings are carried forward the first time you start a newer version. So, when DR 3.9 first starts up, it will use the settings of the highest previous version available, then store its settings in the "3.9" subfolder to not overwrite anything from previous versions. (This is similar to what's Blender is doing, at least I think it is.) What's correct though is that the "portable" version is not differing from the installed one in terms of where it stores it settings. They both behave the same. One could maybe vote for having the portable version to store its settings right next to the executable. But to support this, we'd need a configurable code path or maybe even a separate compilation for the portable edition.

Don't see much in the dump, I'm afraid. I can see it's been running into a critical failure, but that's it. Can you have a look at your darkradiant.log file, or maybe send it to me? Maybe it tells me something. (You already tried to remove your settings XML files from C:\Users\greebo\AppData\Roaming\DarkRadiant\3.8, I take it? You can back them up if you need them around. Just move the whole contents of the C:\Users\greebo\AppData\Roaming\DarkRadiant\ folder to somewhere else and start DR. In case you didn't try that already.)

The crash can be caused by anything. Do you have a crash dump? Otherwise it's nearly impossible to say what went wrong.

I've pulled in all the recent commits from Orb's branch and adjusted the VC++ solution to compile.

No, I don't have any idea what the cause could be. Even if I had time to work on DR right now, I wouldn't be able to work on this particular problem, since I don't have a matching native Manjaro installation around.

Yes, sorry, didn't look into that yet. I can't make any promises at this point.

I won't have much time for DarkRadiant in the near future, so don't expect to see much from me in the next few weeks or even months. I thought it might be worth releasing all the fixes we currently have in the repo, so there goes version 3.8.0!