So I did it. :bsuit: Check github.com/UnvanquishedAssets/UnvanquishedAssets for the master repository. I edited my messages above to fit the current state. You can use them as sort-of documentation while waiting for something better on Wiki. :wink: So, what's the story bro? There is some design choi...

I'm fine with changing the package extension to dpk . I agree that our packages are sufficiently different from pk3 to justify this change, given that the current same-name policy actually causes issues. :thumbup: However, I'd like to maintain full debian version strings and debian version sorting....

Here is a pull request to add dpk/dpkdir support in Dæmon engine . It also fixes some bugs that were there because the engine was trying to handle two different behaviors for the same format, it's now far easier to handle two different behaviors for two different formats. So we have now an unmerged...

I had nothing to code to add basic (no deps) dpkdir support to DarkRadiant: http://dl.illwieckz.net/b/darkradiant/screenshots/dpkdir/20170326-062757-000.darkradiant-dpkdir-unvanquished-forlorn.png I just wrote this line in “ unvanquished.game ” file: archivetypes="dpk pk3" And DarkRadiant ...

This a branch that adds pk3dir/dpkdir support in netradiant (based on neumond's code): gitlab.com/illwieckz/netradiant:dpkdir . I'm not a C++ master, I can't say if the code is optimal (and is probably not unless someone unravell the netradiant's spaghetti code first :cyclops: ), by the way it works...

So, to summarize my wall of text, after some talk with @Amanieu on the development channel, my suggestion is: change the extension from .pk3 to .dpk, keep .pk3 support as a "legacy" format reject dpk version numbers that don't start with a number allow dpkdir version to start with a letter...

What's happening? In all projects some early decisions that looked good enough appear annoying later, when more stuff is done. One of these early mistakes was to keep the pk3 file extension when the Dæmon VFS switched from classic id Tech 3 pak format to the newly dependency-based format. Well, bec...

Hi @greebo! Welcome there! My fork is just a place for me to experiment stuff and to share what I'm experimenting with. For sure if one day I wrote something releasable I will submit a PR, I'm not planing to maintain any fork outside the tree. I wrote a tool to compare radiant trees to look for stuf...

Except that texture scaling issue, that looks very good:

As you see, the decorative turrets are rendered in DarkRadiant, something that is missing in-game.