windows partitions need about 10gb (or more maybe, for vista?) just for the OS itself and then you're gonna want at least 2-4gb for your paging file.
you never really notice that when you're setting it up on a native windows machine, but when you're splitting between mac and windows, it becomes noticeable. mind you, mac isn't exactly a lightweight either; i spent a couple of days cleaning out all the useless software on my macbook, but i needed about 80gb for my macos partition to be able to work comfortably.

anyway, on the subject of gtkr, i personally hated the 1.5 version of the program. they changed fundamental UI stuffs in there which made it a lot slower to use (eg: operations that used to take 1 key press now would take 2), so even though 1.5 supports q1 natively, i found it harder to use than to just save a q3 .map and have a batch file that runs a converter first (aguirRe's, i believe, is the most up-to-date) and then compiles.

as for batch files, just make a bunch of them (for different compile levels) and put them on your start menu (or get rocketdock which is essentially the mac dock for windows) and you can just click the appropriate one and never have to touch a command prompt. 

My c: is 80gb 

Yes, I'm gonna keep on beating that dead old horse. 

I'm thinking about installing Quake and GtKRadiant on this new Linux box I've got.

Can anybody point me in the right direction? 

the gtkradiant based off 1.5 that the darkplaces/warsow? guys use. 

Is there a way to make it so I can launch FitzQuake to check out my level without it resizing every window on my desktop? Or is this just a Window wart that I have to accept? 

OK, I guess the answer is to run GTKRadiant in a non-maximized state. That seems to reduce the amount of swearing I need to do each time I test the map... 

if it's fitzquake 0.85, you can run it windowed but with a -height and -width equal to your desktop -- this will fill the screen completely but without your desktop actually switching modes, which might help. 

Ahh. that's something I hadn't thought of. OK, will try, thanks! 

setting sunlight?

good value for day time light?

I don't understand the angle situation. I've just never bothered to. Can someone give a simple explanation of how they'll work? 

No, but just read AguirRe's docs:

http://user.tninet.se/~xir870k/

More and more concise information than you'll need. 

 

Thanks Ijed. I can't believe I haven't read through that stuff already!
Kind of confused about the implementation of 'second suns'.
My basic understanding is that I just put _sunlight2 in worldspawn with a lowish value and it will lessen ugly shadows? 

or take one sun and lighten those ugly shadows with a light.exe -light 15 so the deep darkened places keep their luminance for a degree of 15. Helpfull, while it diminish placing lots of extra lights.
^v^ 

it's really not _sunlight2, it's _sunlightarea_minlight.
it's a different minlight for areas that the sun hits. 

Thanks guys, I think I actually get this now. 

I confirm that this solution to Hammer 3d window selection issue works:
http://www.celephais.net/board/view_thread.php?id=4&start=8179

I have put this file into the hammer directory and the problem on my laptop is fixed.
http://rapidshare.com/files/138119760/atioglxx.dll

Great! I can continue now. 

I just wish there was a similar fix for Nvidia cards. 

It works, but if I look at a face and not all of its verticies are visible in the window then the projection screws up, aligning the last UV coordinate to any other visible vert.

That's a bad description. Basically the UV's are all fucked up. That's better.

And Orl, there will be such a fix for your card, AFAIK Nvidia is much better supported, although to be honest I didn't know there was a WC problem.

What the DLL does is disable stuff, you'll notice there wasn't one there beforehand. WC checks if one exists and if so uses it in favour of the onboard library.

Does anyone have the knowledge + inclination to make one that forces software mode on? In WC1.6a there was an option for this :P 

Maybe I don't understand the problem with UV's that you described, but try to enable Texture Filtering in 3d options window. After enabling this option the textures look ok for me. 

If it works my mapping time will double. 

And Orl, there will be such a fix for your card, AFAIK Nvidia is much better supported, although to be honest I didn't know there was a WC problem.

Unfortunately, I very highly doubt there will be a fix. Basically the problem is, using any Nvidia drivers after version 182.50 in Worldcraft 1.6a in software mode, the 3D view is completely garbled, making it impossible to see anything.

And yet, even the older Worldcraft 1.1a's 3D view works perfectly fine with the latest Nvidia drivers... strange.

For whats its worth, I'm running Vista SP2 with an 8800gt. 

That works; turning off filter textures. Can't believe after pissing about with all those different (non) solutions I missed that option.

So the dll + filter off solves it for me - thanks!

Orl, have you tried 3.3? It might sound like a ballache to switch, but the texture lock alone makes it worth it. The renderer changed a fair bit (which is why I and others have had problems) but maybe its worth a try so you can map. 

textures and wc 3.3

does anyone else have problems converting texture files (not just because of overly large textures) with Bakers wad converter?

I think RT23 had some issues with that too - or maybe he helped me with mine... It's all foggy... ...what year is this? 

But the wads you wanted were weird

I never had that problem until I tried to convert that WAD which you were saying you couldnt manage.

Cant remember if I had to use texmex or wally as well as the supplied util. Its all on this thread somewhere, lol!

Most textures convert fine, it would seem to be some wads which dont (!)