Hmmm... OK, for starters, try modding my snippet and try again.
You should be able to see where this fits...
Code:
...
	if(my) 
	{
		sys_marker("se6");
		void* temp_data=NULL;    temp_data = ent_getmesh(me,0,0);
		if(temp_data==NULL)   {  error("ME has no mesh...dead?");  }
		sys_marker("se7");
		BMAP* tmp_bmap=NULL;     tmp_bmap = ent_getskin(me,1);
		if(temp_bmap==NULL)   {  error("ME has no skin...dead?");  }
		sys_marker("se8");
		ent_remove(my);	//will also stop sc_ent_shieldImpact
	}
	sys_marker("se9");
}




Now, as for the error occuring in enet_ent_remove() as well... interesting.
We are going to need an enet guru for help on this, cause Ive never used it.

But is it POSSIBLE that the MY causing the error (in the first problem) is somehow being removed
by ENet itself? That is, do you ever give 'this' entity to enet for any reason?

Because, at a GUESS, it may be that if ENet removes an entity, then MAYBE the
acknex scheduler doesnt know that it needs to shut down any actions used by that entity...
Just a hunch...


Let us know how the first test goes...


"There is no fate but what WE make." - CEO Cyberdyne Systems Corp.
A8.30.5 Commercial