stevec wrote:I'm not sure where the settings are locally stored on a Mac, but creating a folder called 'settings' inside the NetRadiant directory converts the installation into a portable one where all configuration files become stored inside that folder.
The default game configurations are stored inside the 'netradiant/games' folder if I remember correctly, inside xml-style text files, you might have some success editing the default MacOS gamepath inside those.
Also, NetRadiant is the king of all radiants.
Yeah, I don't understand how people put up with GTK as long as they did.....it ...can't do math.....I don't know if any one else noticed, but fine brush point manipulation in GTKRadiant was a nightmare, and borderline impossible, if you moved one point, it'd totally mess up the others, and if you go back and fix those, the other one gets messed up, useless!
and you're right, I'd forgotten about the 'settings' folder trick, I just got a fresh NetRadiant working in snowleopard, so I need to add in all of the things that make it useful again.
Kolossus wrote:
Could you guys tell me about your mapping directories structure?
Where are your files located? Shaderlist.txt?
Sure.
on my compiler, (6-core 4.5GHz workstation running windows 7)
C:\quake3\baseq3\maps
C:\quake3\baseq3\scripts
C:\quake3\baseq3\textures
C:\quake3\baseq3\levelshots
I'm not sure where shaderlist.txt is supposed to go, but I seem to have one in my maps folder, and another in my textures folder, and maybe one in my scripts folder
I feel like it really belongs in the scripts folder, as it point out the names of shaders, which are scripts, but that's just me.
in OS X, I always have /Applications/ioquake3/baseq3
and everything else is the same, maps, scripts, etc
I don't think there's really any "right" way to do it though, the way I do it is just meant to optimize workflow across platforms.
I just compile a map..and I can instantly load it up into quake 3.
I have a friend who likes to compile at C:\ and then goes through the trouble of dropping the bsp file into a PK3 archive, and then manually moves it into his 'baseq3' folder every single time he tests a map. It's not wrong, it just adds extra steps that could otherwise be replaced with pure, unadulterated laziness.
In OS X, for extra laziness, I put hot-links to baseq3 and my baseq3/maps directory in my sidebar right next to things like "Downloads", "Documents", and "Applications". That way dragging and dropping new PK3s or BSPs is literally a file-drag away almost 100% of the time.
