This is bizarre and inexplicable:

[Pixelthief]

(you might have to copy/paste the image link)



The middle action- setting "SfxTemp" on my E-shaped object.
Despite the values in the magicdeque and referenced global being valid, this "SfxTemp" is set to completely incorrect values.

When it should return 430, it returns instead 1091567616



Experimenting with it, I found that removing the absolute value on the function- the abs() term- causes it to function properly. IE now it returns 430.


I've been testing it out though, and virtually anything I wrap around it causes it to return garbage values. Using a Floor() function does the same thing- returns 2^30 size integers. Int(), Ceil(), etc. I tried breaking up the code- setting the temporary value, then operating on it. Same result- it creates more garbage values.


So I basically have equation that looks like this:


(X - Y) = 430
Abs(X - Y) = 1091567616
Floor(X - Y) = 1077936128



(I'm just using generic values- it operates on all sorts of numbers not just 430 and does them fine without the function calls, and each time its a different integer).




Does the magicdeque return some kind of float that MMF2 doesn't recognize? Is there some kind of type-casting error going on here, where its trying to use a wrong format float as an integer? Why does subtraction and addition work fine, but function calls- even when used on stored, parallel copies of the value- return bizarre numbers? Whats going on here

[LB]

What happens if you convert it to a string?

[Pixelthief]

String displays the same thing.

I'm thinking its a possible flaw with the "Change Value" function of the magicdeque object. If I store that same equation in a *different* object like a counter, it displays the right value. But if I store it back in the deque, all future calls to that same position return garbage.

So its telling it to change value to the correct value, but future "Get value at element/array" calls are giving the garbage

[Pixelthief]

heh, thanks LB ~_~
your saying "string" made me notice something:









I think I found the culprit. There seems to be a typo in the "Change Value" option of the magicdeque object- its using the string type! Looks like he accidentally made 2x change string options. So it must be passing a string into whats supposed to be an integer, and lord only knows how the type conversion works.

I should email him that bug or summat