Mesh objects can be set as reflection probes via script even though UI is disabled
complete
Cain Maven
While it is NOT possible to set a mesh object as a reflection probe manually, it does work when calling llSetPrimitiveParams() with the PRIM_REFLECTION_PROBE parameter. The resulting probe works correctly.
Reverting back to a regular object via script also works; the UI is of course disabled.
The behavior should be the same for scripted and manual operations.
Log In
This post was marked as
complete
Maestro Linden
tracked
There seems to be general consensus among the Lindens that if we're going to change something, it should be simulator that changes to match the build tool behavior. Which in this case means that meshes can't be set as reflection probes, and that non-mesh prims will automatically have their PRIM_TYPE changed to a default sphere or box (depending on the status of the PRIM_REFLECTION_PROBE_BOX flag).
Cain Maven
Maestro Linden That makes sense -- I don't think we need mesh probes :)
Maestro Linden
under review
Maestro Linden
What is your expected behavior here? That enabling PRIM_REFLECTION_PROBE should fail if the prim is a mesh or that the viewer should allow enabling of the "reflection probe" flag on a mesh even though it's unable to set the prim type to box or sphere?
Cain Maven
Maestro Linden I don't think it makes much sense to allow mesh objects to serve as probes. Given that the shape cannot be changed to either box or sphere the object can have a visual shape and a functional shape that are different. This is inconsistent and confusing.
Additionally, the UI issues an error message if you try to change the shape type -- for some reason the remaining UI controls remain enabled even though the main check box is disabled.
I think enabling PRIM_REFLECTION_PROBE should fail if the prim is a mesh.