last modified. 05-29lists of things you may run into and should be aware of when building .
potentially destructive.
Packet loss can cause edits made to 'undo' themselves, making building very difficult. better info on the FS wiki.
Using the stretch mode key-bind ( even without making edits ) on objects with materials (normal, specular) can sometimes completely reset the texture mapping of those materials. depends on whether stretch textures is on/off & mapping type. default mapping - resets if ☐ stretch textures planar mapping - resets if 🗹 stretch textures
Attachments need to be re-attached to save edits made. This applies to any attachment, not just prims. ( they get saved at other times too, but re-attaching will ensure nothing gets lost if SL crashes unexpectedly. )
Some z-fighting/flickering prims will not be apparent until re-rezzed. ALSO dependent on altitude, due to a rounding error that affects all objects, mesh or prim.
Unlinking larger link sets can cause flickering, or prevent the user from editing the newly unlinked objects ( fixes itself on relog )
Smaller prims are likely to be missed when attempting to select them with Shift+Drag Click
Pasting materials on medium/large Link Sets can cause intense lag.
Texture mapping behaves differently between PBR and Blinn-phong.
Parameters can be linked to others in not so obvious ways. ex, skew & revolutions
Land impact shown in Build Menu can be slow to update even when the physics shape is changed.
Freshly created link sets show inaccurate link order until re-rezzed
When flexible prims are used as the root in a link set, certain options can be grayed out for the entire link set. ( phantom, physical )
( only have had this happen once hehe ) Texture shown to the viewer is different from what is actually in the slot. when it happened to me, it showed a different texture from the link set.
annoying!!!.
something changed around 04-12-2025 that affected the circle hollowed faces for most shapes. the date is when I had updated my viewer, so not entirely accurate. I got no clue about the change on a technical level . but in my brief testing the Firestorm version 7.2.3 (Legacy) has the old normals, while 7.2.3 (AVX2) does not.