So I've started writing some of my own FPI scripts to accomplish things like making lifts that operate after a switch is pressed and secret doors that slide open and then close after a few seconds have gone by.
One thing I've noticed with any script I've written that uses the "move" commands on entities is that the closer I am to the entity when the script is being activated the faster the entity will move. If I'm observing it from a distance then it will move very slowly in comparison.
This leads me to believe that the FPSC Engine processes entities that are closer to the player faster than it does those that are further away and if this is the case then it's going to lead to some problems and I suppose I'll have to edit the engine source.
I just wanted to know if anyone else has experienced similar issues or has studied the engine some and can tell me if this behavior is true or not.
Thanks!
EDIT:
After some more testing and studying of the FPSC Engine source I figured out why this was going on. It's an optimization feature of the engine so that entities which aren't flagged as being important enough to update on a regular basis will not be updated as often unless they are within a certain range of the player.
This is probably already known to many but for those who did not know about it if you check the "always active" flag on an entity then it will ignore this optimization feature and always update regardless of how far away the player is. The map editor actually tells you this if you look at that particular property but I misunderstood what it meant until now.
