Glitch with Alterable Variables and Set Position

[Corlen]

I found another glitch with MMF. It works in and out of HWA. Both objects that move have the same copy of the code and everything except one is set to go the opposite direction and yet one travels further. This makes coding stationary sinewaves from scratch impossible obviously and would subtly screw up platform engines built from scratch when it comes to jumping if they used this method which just about everyone who does this does.

[Sheexy]

I found a way around this a while back.

What is happening is when you set it to the position its alterable value is at it will Floor() the value every time.

That works fine when you are working with numbers greater than 0, but when you start going lower than zero flooring it makes it go down way further than it should.

The way I've gotten around it is by making it Ceil() the values if you're trying to move it to a position lower than it currently is.
Here is the file with a work-around. I just added a Ceil() call around the positioning of the one moving negatively.


I don't think I've explained this very well, but hopefully it makes sense. Maybe someone else can explain it better.

Definitely a bug I think.

[Corlen]

Ah thanks for the info. I imagine it probably was unintentional.