ulf.schroeter Posted May 28, 2012 Share Posted May 28, 2012 Problem Took me some time to realize that engine.world.getIntersection() only finds surfaces if they have assigned materials and properties. While this behaviour for surfaces without material (-> invisible) is quite clear, this is not as clear for surfaces without assigned property. Proposal Add some comments to engine.world.getIntersection() documentation on required material and property asignment. Link to comment
manguste Posted May 28, 2012 Share Posted May 28, 2012 Yes, the number of conditions are checked at the same time: Per-surface Intersection flag is enabled. Intersection option in Properties is enabled. A surface has a material assigned. A surface has a property assigned. A surface is enabled. It's mostly done for faster enabling/disabling of intersections when necessary (disable one of the intersection flags and the surface will be skipped). I've added this into docs, thank you. Link to comment
Recommended Posts