featureType = 2, which makes an object always visible, can make the ghost of it, which has no shadow or collision, not even an object, just a resolution LOD.
It is very easy to reproduce with USS Freedoms too.
Description
Description
Details
Details
- Severity
- Minor
- Resolution
- Open
- Reproducibility
- Random
- Operating System
- Windows 10 x64
- Category
- Visual-Structures
Steps To Reproduce
- Go to VR, bottom left (0,0)
- Execute this code
for "_x" from 0 to 15 do {
for "_y" from 0 to 15 do {
createVehicle ["Land_spp_Tower_F",[_x*30,_y*30,0],[],0,"CAN_COLLIDE"] ;
} ;
} ;- Ctrl+N to create new screnario
- You may see one or two solar tower is still present, with no shadow or collision
- Alt+Tab and back may remove the artifact
Additional Information
This can happen with setFeatureType 2 script command.
If we use deleteVehicle to remove the featureType 2 vehicle, will never create an artifact, so I would assume this only happens when a vehicle has been removed in a special case.
flush cheat code will remove the artifact too.
Event Timeline
Comment Actions
At the end of a Eden scenario, all objects are cleaned up, and if their reference count goes to zero they are deleted. And usually at this point an object only has one reference to it.
Eden has a "mouse handler" that checks what is under your mouse cursor, and stores a reference to the object under the cursor.
So, the object that was under the cursor still has a reference in the mouse handler, that kept it alive across the "New scenario" boundary, and afterwards the feature object kept itself alive because it was rendering (tabbing out clears the rendering list which could make its refcount go to zero and make it disappear).
That's a really fun one.
This is exclusive to Eden, there might be similar issues where something else keeps an object alive in a different situation, would need a repro for that situation.