![]() |
|
|
|
#1
|
|||
|
|||
|
Any other 3.0 migration problems?
__________________
Paul Elliott WorldViz LLC |
|
#2
|
|||
|
|||
|
It looks like viz.phys.intersectLine is faster than the old viz.intersect. But, the old intersect would ignore objects that were not visible.
1) Is there any way to tell viz.phys.intersectLine to ignore certain objects? object.disable(viz.COLLISION) doesn't seem to work, neither does turning off visibilty. 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). (This is also where thread 729 ended up). 2) Is there any way to get better documentation on these commands that he skeletal docs in the Vizard Help or in Python help()? Last edited by pbeeson; 09-11-2006 at 11:37 PM. |
|
#3
|
|||
|
|||
|
1) viz.phys.intersectLine() works on the physics simulation level so it only intersects with physics shapes. To have it ignore nodes, remove their VizPhysicsShape with a call to collideNone().
2) Vizard Help is the best option right now. Of course the forum is fairly good too
__________________
Paul Elliott WorldViz LLC |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|