crash in dNewtonTransformManager::UpdateTransformKernel

[Slick]

dBody is returned NULL from Getuserdata. I don't think that I have even used setuserdata that would set it to an invalid value.

Could it be a thread issue?

12-9-2013 12-42-42 PM.png (67.81 KiB) Viewed 2847 times

[Slick]

I tried m_World->SetConcurrentUpdateMode(FALSE); to disable threading and it seems to be ok.

I am guessing it is related to me destroying a body but the thread isn't synched that it is destroyed? Is there a standard way to destroy bodies to avoid thread issues?

I could be wrong about the cause and will test more.

[Julio Jerez]

did you call WaitForUpdateToFinish(); before you delete the body?

[Slick]

No I don't think so. Should you call that before every deletion on a body? That would be a lot of calls throughout code but maybe required?

[Julio Jerez]

the end app has to do it because the the call is not reentrant, if I call it and soem one else callit, it will lock indefinittle.

you should not call that after every frame because it defeet the purpose of asyncronous update.
in the demos there are some example of how I use it.

for example when you hit space key, for spawing a body, or when hitting the F3 key.
look at function void DemoApplication::OnRenderUpdateEnd(dFloat updateParam)

[Slick]

Yep I understand to not call every frame.

Does this mean whenever you create or destroy a body you should call WaitForUpdateToFinish(); ?

[Julio Jerez]

yes.

[Slick]

Would it make sense to put the waitforupdatetofinish call in the constructor and destructor of OgreNewtonDynamicBody/OgreNewtonScenebody etc?

[Julio Jerez]

not because when the contructor and destrucotr are called the base class is already called,
so that will do nothing because the NewtonBody is create in the base class

it sodul not be that complicated.