Page 1 of 1
"opStack corrupted in compiled code" - error
Posted: Mon Aug 11, 2008 1:57 pm
by monaster
Erm... yeah... anyone got an idea? That error popped up when I tried to start a normal tdm map of my own which worked fine a few days ago so I have absolutely no idea what might be wrong with that thing; I haven't changed it since then. It is already in a .pk3, so there's no \devmap stuff to be considered and the game itself runs fine with other maps being nearly the same as the one producing this error.
Re: "opStack corrupted in compiled code" - error
Posted: Mon Aug 11, 2008 9:10 pm
by fKd
according to google
"This error arises in some mods of Quake III Arena (like excessive mod) when pure server is set.
Just go to console with pressing ~ and enter \sv_pure 0"
hope that helps
Re: "opStack corrupted in compiled code" - error
Posted: Thu Aug 14, 2008 2:31 pm
by monaster
Nope, didn't help. Problem is that I already run quake 3 on pure 0 by default sometimes even when I start up pk3s. I've tested the spoken of map with pure 0 and "normal" mode but it seems that the error occurs coincidentially. Sometimes it pops up when I set g_gametype to "4" sometimes it even crashes the whole game that way! Same counts for ffa accessed over the console AND the main menu (using a pk3 for the latter one again) and so on... man, I've been changing pure servers, gametypes and map versions all day long (at least several hours), deleting the pk3 and just starting with "\devmap xxxmap" and vice versa, compiling the maps again and again... that stupid error kept showing up from time to time. Sometimes the map even started correctly and didn't crash even after playing it for 20 minutes (if it crashes it always does at map entry). I could post a few more of my ideas I've tried yesterday but it's always the same: every time, the game either crashes completely (resulting in a windows error) -approximately 50%- or it throws me back to Quake3's main menu -app. 40%- or it works fine - app. 10% of the time. Strangely, "working fine" often included playing a very similar map version first which has been compiled shortly before the problematic one - or is that unimportant?