The game and Radiant load files in descending order, this way paks with higher number will always be loaded first, and first registered file with the same name always has precedence over the next one, when it comes to loading contents, but q3map2 loads files in ascending order instead!
Could someone explain, is this by design?
Now this might be not a big issue, but actually, this can bring to some really weird results.
Like here, where pak1.pk3 contains yellow walls, and pak2.pk3 red ones. Q3map2 uses pak1.pk3 to lit the surface, and game loads pak2.pk3 to display the texture!
And Radiant loads pak2.pk3 as expected:
If we leave just pak2.pk3, we would get something we expect to get:
The game and Radiant load files in descending order, this way paks with higher number will always be loaded first, and first registered file with the same name always has precedence over the next one, when it comes to loading contents, but q3map2 loads files in ascending order instead! Could someone explain, is this by design?
The issue appears specifically here: https://github.com/TTimo/GtkRadiant/blob/2d91146b804be2d3176880d1a491dda96c4f92a7/tools/quake3/common/vfs.c#L198 While radiant's vfs does the sorting: https://github.com/TTimo/GtkRadiant/blob/2d91146b804be2d3176880d1a491dda96c4f92a7/plugins/vfspk3/vfs.cpp#L464
Now this might be not a big issue, but actually, this can bring to some really weird results.
Like here, where
pak1.pk3
contains yellow walls, andpak2.pk3
red ones. Q3map2 usespak1.pk3
to lit the surface, and game loadspak2.pk3
to display the texture!And Radiant loads
pak2.pk3
as expected:If we leave just
pak2.pk3
, we would get something we expect to get: