Radiant Crashes On Compile

(mogliET) #1

I am new to mapping so forgive my ignorance, but Radiant crashes everytime I try to compile a map. I get the Windows Generic ‘…encountered an error and had to close’ error reporting box come up, and that is it. I made the map from this tutorial, and I managed to do all of it until the compiling part :P. I had a different compiling problem before about a ‘connection timed out’, but I fixed that by changing firewall settings. But now I have gone on to this :frowning: The weird thing is that it only crashes if I use the (test) BSP options - If I compile it with ‘(single) -light -fast -samples 2 -filter’ it works ok - but the (test)BSP one is specified in the tutorial. What could I have done that causes this error?

Also - other maps that I have made cause Radiant to crash irregardless of what compile option I choose.

(carnage) #2

strange since the compiler and radient are two seperate pices of software

radient makes .map files
compiler turns .map into bsp and lightmaps

try uninstall your radient and other stuff then get radient 1.4 and re install

(mogliET) #3

yeah - i think ill reinstall Radiant. I just wonder, why does it crash? Have I done something wrong with the map?

(carnage) #4

if there is something wrong with the map the compiler will stop and return to the normal editor mode

(]UBC[ McNite) #5

Sounds like you compile right from the radiant. If you do that, I strongly recommend your stop doing that and use a compiling frontend instead (i use q3map2build by bobdev and never had any trouble).
This mainly has 3 advantages:
a) you can get a compile logfile which means you ll find out what s wrong wit the compile much easier because you know when it fails
b) its a HUGE lot faster due to improved use of memory
c) you can set your compile options a lot more detailed than in radiant

I can’t give you much more of an advice as long as I don’t know more about when the compile crashes.[/u][/list]

(mogliET) #6

I’ll have a look for that.
Thanks