slow intersect call

[pbeeson]

I am getting 80ms with just my "indoor" environment, which is pretty simple. Maybe I should try to separate the walls from the ceiling and floor and add them both to vizard since I never care about intersecting with the seiling or floor.

[farshizzo]

Unless your floor and ceiling contain a lot of triangles, it's probably not going to make much of a difference. But if you want to try it out, you don't need to create separate models for them. Simply specify the name of the floor/ceiling mesh when disabling collisions. Example:

room.disable(viz.COLLISION,'ceiling')
room.disable(viz.COLLISION,'floor')

Also, do these intersections tests need to be performed every frame? If not, you can offload the intersection tests onto a thread that performs them at a lower rate.

[pbeeson]

I noticed in version 3 that viz.phys.intersectLine() is much faster than viz.intersect(), but viz.phys.intersectLine seems to have some problems:

1) It returns intersections for non-visible objects (object whose visibility is set to off), which is different that viz.intersect()

2) It ignores the viz.disable(viz.COLLISION) command. Is there a way to get it to ignore certain objects?
I can run viz.phys.intersectLine(begin,end,True) to get a list and then check object IDs, but I don't know if there is an easier way (especially considering that if you have many objects, it might be an optimzation to not check for intersections with particular objects at certain times, e.g. if you are casting rays from within an object).

3) As I said earlier, I am casting 180 "rays" from a virtual laser range finder. When I do this, viz.phys.intersectLine() is much faster than viz.intersect() (Even if I set the all flag to True), but viz.phys.intersectLine actually misses some intersections with the closest objects, while viz.intersect() does not. I'll post two picture to illustrate my point.

[farshizzo]

Originally Posted by pbeeson

I noticed in version 3 that viz.phys.intersectLine() is much faster than viz.intersect(), but viz.phys.intersectLine seems to have some problems:

1) It returns intersections for non-visible objects (object whose visibility is set to off), which is different that viz.intersect()

I just fixed this. Setting an object to non-visible will automatically disable physics on it.

Originally Posted by pbeeson

2) It ignores the viz.disable(viz.COLLISION) command. Is there a way to get it to ignore certain objects?
I can run viz.phys.intersectLine(begin,end,True) to get a list and then check object IDs, but I don't know if there is an easier way (especially considering that if you have many objects, it might be an optimzation to not check for intersections with particular objects at certain times, e.g. if you are casting rays from within an object).

I just modified the physics intersectLine/Node commands so that they ignore objects which have physics disabled on them. viz.COLLISION will still only pertain to the old viz.intersect() command.

I know this really doesn't help you now, but we will probably release an update within the next few days.

[pbeeson]

Originally Posted by farshizzo

I know this really doesn't help you now, but we will probably release an update within the next few days.

It doesn't help me even when I get the update. In 2.53, I could have a body that represented the "viewer". That body could be not visible, so that intersect() would not see it, but collidingwith() still did see it. But, I get by with calling phys.intersect(start,end,True) and then removing points that intersect the viewers own "body".

[farshizzo]

Originally Posted by pbeeson

It doesn't help me even when I get the update. In 2.53, I could have a body that represented the "viewer". That body could be not visible, so that intersect() would not see it, but collidingwith() still did see it. But, I get by with calling phys.intersect(start,end,True) and then removing points that intersect the viewers own "body".

So you want an object to be invisible, but still allow phys.intersect to work? Then just disable rendering on the object:

object.disable(viz.RENDERING)

Sorry if I misunderstood your question.

[pbeeson]

Originally Posted by farshizzo

So you want an object to be invisible, but still allow phys.intersect to work? Then just disable rendering on the object:

object.disable(viz.RENDERING)

Sorry if I misunderstood your question.

I don't care if it is invisible. All I know is that by doing avatar.visible(viz.OFF), in version 2.53, viz.intersect() would never return an intersection with the avatar, but viz.collidingwith() WOULD work if the avatar collided with antoher obstacle.

Maybe THAT was the bug, and now it is fixed. It's just different.