Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

m_appliedImpulse in gContactProcessedCallback #335

Closed
velkyel opened this issue Mar 1, 2015 · 2 comments
Closed

m_appliedImpulse in gContactProcessedCallback #335

velkyel opened this issue Mar 1, 2015 · 2 comments

Comments

@velkyel
Copy link

velkyel commented Mar 1, 2015

there is a lot of question about zero value m_appliedImpulse in gContactProcessedCallback on forums (it's probably best value to start playing sounds etc.).

I think actual call gContactProcessedCallback in btPersistentManifold::refreshContactPoints() is too early for many cases. Final right value m_appliedImpulse get manifold point in btSequentialImpulseConstraintSolver::solveGroupCacheFriendlyFinish(). So call gContactProcessedCallback should be somewhere after that.

I have modified my bullet fork which is too different to make pull request with same patch.

@erwincoumans
Copy link
Member

thanks for the feedback, I'll consider it.

@erwincoumans
Copy link
Member

It won't make it for Bullet 2.83, but possibly in the next release (I really need to push out the 2.83 release, it has been delayed way too long)

@bulletphysics bulletphysics locked and limited conversation to collaborators Apr 26, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

2 participants