Publish shock (again...)

I found out the hard way that the known "memory leak" is much worth then i thought...(23:00 to 8:00 with AI)


Only the published version will crash (without error message or acklog-entry) if you play for at least 5 minutes and reloading the level 5-10 times!
First of all i hate that the published version of every Acknex project acts different in 1000 ways to the sed start, but sadly thats not new.

I tryed everything...i did manage to call level_load only once(thought level_load itself is the problem in combination with shadec), building the map by script manually (yes, terror), managed the nexus by hand via
level_mark and level_free etc...still crashing. I guess the problem is deep in the shadec connection between Acknex and DirectX. Boh's "sc_reset" and "sc_destroy" functions
just dont work(!) if you call them once after you called sc_setup.

It seams not possible to end shadeC evo if it started once...because its engine-pointers are "async" to GPU for one frame.
I tryed to end it with new functions: it always ends in "invalid memory area" or "script crash in sc_forward_destroy".
It seems to be a fundamental problem with the connection between Shadec and DirectX. I'm just guessing.


The only possible way to use shadeC with massive "world reloading" / level switch seams to use a extern process (like my starter app) to control level switch from outside
of Acknex.
The only way i see to really clear the "corpses" from shadeC in the GPU: end engine - restart engine in new level/with new content.
Without another process it could be done via exec and -nwnd option i guess...
Anyway...its a ugly hack!


3run did modify shadec evo once, i dont know if he came to the same results. Would be interesting what he modified exactly in his shadec evo verson back then.


Maybe im wrong, but i say ShadeC evo needs to be rewritten from scratch to get rid of this "destroy" problem.
I guess the mastermind Boh_Havoc did not test massive reloading/level switching in a published version. It seams like shadec was only tested like a techdemo in a
single WMB with not much happening around it.

Just wanted to let you guys know.