Well if you want to prove that theory then it will not take long, open the map.pak file (it's just a renamed zip) and look in the scripts folder for the shader file, in your quake directory make a folder called scripts. Look for the texture file (use photoshop or similar) that is used for the graphic that's causing the issue, in the shader file look for a reference to that image/tex file and remove the lighmap entry for it. Upload the modified shader file and put it in the scripts folder then restart quake3.
I'm probably going to make a full memory overhaul since I learnt a lot of new tricks while working on the OG Xbox port.
It doesn't run on 32 MB of RAM. It's running on 64. But I managed to get my OG Xbox port to run Team Arena as well as all Q3 maps with bots on that console.
Congratulations! It has become a fine, stable port. Looks better than ever, specially on the CRT. Playing a quick round of Quake III every now and then without having to turn on the PC, is awesome.
but to be clear that was me intentionally trying to see how far the memory optimizations go by trying to overload the Wii - that fact that it didn't go into a loading loop or die on a black screen is a good sign! I'm going to keep testing how far the Wii can go with custom content but for now it seems as good as it was before with the added bonus of looking way better, definitely your finest release yet!
The only optimization I made was to slice in half the textures and make the console decode them on load (so a 512x512 texture would be 256x256 without sacrificing quality). The exploding polygons is sort of weird but if I have a pic or a screen I could investigate further.Oh yes, the decals are working exactly as intended now and I would say this is a commercial quality release! I tried stress testing the memory optimizations by loading a custom level with a lot of custom skins and ended up with a exploding polygon mess
EDIT - OpenArena might not be able to load all assets and large maps though, at least without enabling "force player model", I tried loading one of the bigger maps "OA_Thor" with bots but it failed to load without forcing player models (it didn't load in any previous build without forcing player models though) so keep an eye out for that one if you guys wanna play OA on the Wii, most of the other content loads fine though.
, it wouldn't be the first time a piece of custom content either worked before or almost worked and now refuses to work again on this port although those situations are very few and far in between. I was able to get the "Save the Universe" mode of the Hunt mod working exactly 4 times on either the first or second release of the mod loader build (on official maps and very tiny custom maps) before it just refused to load anything ever again, regardless of anything (deleted everything, clean install etc). I didn't report this earlier because mod loading is just a cherry on top of an awesome port so I fully expected to be touch and go but if that's something you're interested in investigating, those are two notable problematic mods that technically should work and I have photographic evidence of working but can't get working anymore.
Open Arena runs in Interpreter, prior to last update it ran in JIT. Going native will make it effectively work.
I'll investigate the maps you mentioned as well as the Mod Selector with a debug build.Ah so it's not enabled on OpenArena? I think that would help a lot especially since it's more or less a FOSS version of Team Arena rather than just vanilla Quake 3, with the added weapons and larger maps and all. Also that is a brilliant memory optimization! I was going to ask what you did to make larger stuff fit and that's just genius - it also helps menu assets not visually break while trying to load custom thumbnails which was a persistent issue in earlier versions, now it works fine and looks so much better.
EDIT: I'll also try to recreate the same exploding polygon situation although the level I was testing it on (OXODM6) now doesn't load at all and just crashes the game regardless of bots or lackthereof
EDIT 2: Also I should note my SDXC card isn't exactly stable either, I've had issues with it suddenly being read only when inserting into my computer and I know storage mediums have been a problem with this port before so before I say something definitively doesn't work I'll try these tests again on another SD card before I report things being an issue or not.
