ok so i have radiant, for quiet a while
well, i started mapping, and in the beginning all compilations in radiant turned into a crash
except the last one. so i always did that one
Now i am getting in even more troubles
each thing i try is a crash, except BSP -meta, but when i compile a map with that, and then do /devmap myroom , i see awaiting challenge …0 :???: :???:
plz help me, are there other ways to compile, so radiant doesn’t crash? And why does ET doesn’t want to see my devmap???
When you say the compile crashes, does it give you a windows error or something else ?
What version of q3map2 are you using ?
well
the crash happens; i just get: radiant has to be closed of … blabla
but sometimes, windows gives me a nice tehnicaal error and then: The action on the memory (‘write’) has failed
i have never replaced q3map2, just whats with radiant
Never, only the normal windwows crashes, but not like that
i have studied C++ so i know kinda how programming works.
ow since i use linux i have no crashes any longer 
but i haven’t seen radiant for linux so far?
aha? danke, will try that!
but now… look, i hve those errros on both pc’s, and it even crashes with the simplest basic room!
i will now put on coordinates… i hope that works
edit: still crash
Maybe you compile it in wrong order…
First you do a BSP -meta.
If you want to include visibility info, use (single) -vis.
To inlude lighting, try some of the the (single) -light options.
If you’re testing right now, do a BSP -meta only.
There are a few reasons for “choking”, the min/maxcoords are one but that mostly happens only when you try to display the command map.
Check if these commands get run, especially if you’re running a version prior to ET 2.60: ( ETMain 2.60 doesn’t crash on min/maxcoords and won’t bother if you forget g_gametype)
/g_gametype 2
/sv_pure 0
/devmap testmap
ok; i have added the coordinates
everything is still the same
ET 2.55 can’t /devmap my map
Radiant crashes if i do some of the more complete compilation
The target of my map is we can play it on 2.55 aswell… why does this work?
Radiant crashing ain’t normal… unless you’re using 1.5 which is still in beta stage.
Try to (re)install GTKRadiant 1.4, since -vis is needed to optimize the map, and -light to add shading to your compiled map. As long Radiant is failing, there’s no hope for you.
Once that’s done we’ll need to check your settings. Did you execute those commands I posted in the ET console before starting the map?
i always do those commands
and i have those crashes on 2 computers!
i will try linux tomorow 
well
the crash happens; i just get: radiant has to be closed of … blabla
Radiant crashes or q3map crashes :?
Have you tested with just a simple box map, to make sure it isn’t something to do with your map ?
If it is truely radiant that is crashing, you could try compiling with a batch file, or a different front end, like q3map2toolz http://www.quake3world.com/forum/viewtopic.php?t=8903
Your map failing to load may be due to having too many .pk3 files in your ET install. You should use a clean copy of ET for mapping. If you don’t want to have to copies of ET, you can move all the .pk3 files except for mp_bin.pk3 and pak0.pk3 (and pak1 and pak2 if you have the patches) to somewhere other than your etmain.
well i tried a box, and still it crashes
no look, when i start radiant or load a map everything goes fine
but when i reach the BSP menu and hist anything more ocmplicated… auw…
The first thing you need to do is figure out whether it is radiant or q3map that is crashing.
q3map is the “dos” window that pops up when you compile. radiant is the whole editor.
It’s your script. The script is loaded and parsed first before your map and that’s where it’s hanging. Try renaming your script and getting rid of the script_multiplayer thats in the map and see if it will load. the mapcoords for the command map are not causing the problem. As long as you have the team_CTF_bluespawn and team_CTF_redspawn your map will start. Better yet you just need an info_player_deathmatch and it should load as well.