LarryG on 28/2/2016 at 18:47
It took a full day to track down why one 'vator was traveling faster than another when they were set up "identically." By "identically" I mean that their respective TerrPts had the same data for the speed their 'vators should travel, only they were traveling at different speeds. You don't want to know all the wrong headed things I looked at before I finally noticed that one of the 'vators, for reasons unknown, had somehow acquired a Door>Rotating property. I'm sure I never put it on it ... In any event, somehow having that property on a 'vator messes with the way that StopAtWaypoints determines the speed to move the 'vator. Removing that errant property from the 'vator fixed the speed issue.
Takeaway 1: Door properties are evil. Only doors should have them. Only doors have the necessary juju to keep them under control.
Takeaway 2: Door properties can appear out of nowhere to mess with you. So whenever something weird starts happening, remember to look for unexpected door properties.
Takeaway 3: DromEd appreciates a goat sacrifice every now and then, and will take steps to remind you should you go too long between goats.
john9818a on 3/3/2016 at 20:26
I'm still trying to figure out why all of my lights acquired a joints property. It's easily fixed but when I load older missions the spot lights are wagging their tails. :p
Nameless Voice on 5/3/2016 at 03:04
Ah, door properties.
I have vague recollections that door properties used to "corrupt" objects. If you added one by mistake, it was somehow permanently on that object even if you removed the property again. I seem to recall having pathfinding constantly crash on me and having to binary-sort-delete half the map at a time to figure out which object was the culprit. I had to clone that object (which made a fixed copy) and delete the original before things worked properly again
I have no idea if that bug is still there in NewDark or not.
