Page 2 of 2

Re: Problem when upgrading

PostPosted: Thu Dec 27, 2012 5:12 pm
by ganesha
In all of those cases you are still creating the objects on a separate thread though?

No, the same.

How many threads do you use?

Just the one calling update, i.e. not an new thread.

Are you creating separate threads for each object created? What exactly are the threads for?

I am not creating any threads my self.

What happens if you disable your use of threads entirely or is that not easily possible?

I must still call update. I have no other threads in the examples above.

Re: Problem when upgrading

PostPosted: Thu Dec 27, 2012 10:59 pm
by slembcke
Wait. To be clear, you were using threads, but now are only using the main thread and the issue still persists? If you weren't using threads before, what was the @synchronized block for?

Otherwise, I don't know of any bugs that would cause objects to not collide. Forgetting to return a value from a begin or preSolve callback is a good way to have random collision issues, but you said you disabled your handlers... Hrm. Other than checking to make sure the other collision filtering parameters (layers, groups) aren't ignoring the collision, I don't really know what to recommend.

Re: Problem when upgrading

PostPosted: Fri Dec 28, 2012 8:15 am
by ganesha
I probably found it. The group value of my objects was set by a singleton utility class that didn't behave as expected. I removed all groups and I canĀ“t replicate the error any more. It seems to work now.

PS. Looking forward to you multi screen auto geometry project.

Re: Problem when upgrading

PostPosted: Fri Dec 28, 2012 1:29 pm
by slembcke
Ah, good. That was going to drive me a little nuts otherwise.

I'm hoping to get the new autogeometry example mostly finished by the end of next week.