Howdy,

I use gs3d physx in my project and when I kill an enemy (registered as PH_CHAR / character -> pXent_settype(my, PH_CHAR, PH_CAPSULE);) I want to unregister or disable it so it becomes passable. However as soon as I either do pXent_enable(my, 0); or pXent_settype(my, 0, 0); , all other enemies becomes bugged and rotate randomly and move different directions than they normally would. Any idea how to solve this?

Sounds like a memory leak to me. Usually 3DGS handles the removal of physx ents himself. Have you used on_ent_remove anywhere?

Ty for replying. I dont have any on_ent_remove's. Also it seems like I have it only for the characters, e.g. when I register e.g. a crate as a PH_CHAR and unregister after a wait it doesn't seem to cause any problems. So I think I am making a mistake in my character code somewhere but I dont know what.

Some outstanding code:

But I unlink them through NX_IGNORE_PAIR before unregistering.

Also when I unregister I also set the following (dont know if this matters):
set(my, PASSABLE);
my.emask &= ~DYNAMIC;

Hmm for some reason the doing following before registering as PH_CHAR does make it more stable (but still can bug out enemies after a while):

Anyone know what is happening here?

I've used pXent_settype(my,0,0); also in a test level with enemies and didn't have that issue, although I didn't reset the dynamic flag afterwards. maybe the problem is related to resetting that flag?

Ty for reply, I tried that but it doesn't seem to make a difference. Also maybe important to note: only the enemies bug out but never the player actor (even while they share alot of functions). I tried comment the AI only lines out but doesn't seem to make a difference to. Only the 'player' pointer is different ofcourse.

Also you run Shade-c evo right Painkiller? So that should not be it than.

yes, I'm running Shade-C too. Maybe you are using any global variable for the enemies that causes a conflict between them? or a memory leak issue?

@Painkiller, in your tests, did you use pXent_move?
After exhaustive testing (with stripped down code, no player and only a couple of enemies and terrain) it seems there becomes something wrong with pXent_move only, the rest seems to work well. Also I think that pXent_move bugs out enemies/player only during the frame(s) the enemy get unregistered, hence why the player rarely bugs out cause pXent_move is not constantly triggered for the player but is for enemies.

I use forces to move the characters, so yeah maybe it could be an issue with pXent_move

Ditching pXent_move and pXent_rotate seems to have solved the problem and is also much cooler imo being able to push away enemies etc.
What function do you use to move entities around? pXent_addvelcentral? Movement is still a bit floaty even though I have set pXent_setdamping to 100%.