ID:1661135
 
Not a bug
BYOND Version:506
Operating System:Windows 7 Ultimate 64-bit
Web Browser:Chrome 36.0.1985.125
Applies to:Dream Seeker
Status: Not a bug

This is not a bug. It may be an incorrect use of syntax or a limitation in the software. For further discussion on the matter, please consult the BYOND forums.
Descriptive Problem Summary:
Previously, an animate() call worked properly to animate the pixel_y of a screen object. Some time later, having updated BYOND and now resuming the project, the same code as before does not work.

Numbered Steps to Reproduce Problem:
Run Program.

Code Snippet (if applicable) to Reproduce Problem:
/Menu/TitleScreen/Input(var/Control)
if (EnterEnabled && Control == ControlEnter)
EnterEnabled = FALSE
animate(Text, alpha = 0, time = 6)

world << "TitleGraphic pixel_y is [TitleGraphic.pixel_y]"
animate(TitleGraphic, pixel_y = 64, time = 13, easing = SINE_EASING)


spawn(14)
sleep(0.3)
world << "TitleGraphic pixel_y is [TitleGraphic.pixel_y]"
//TitleGraphic.pixel_y = 0
//TitleGraphic.screen_loc = "3, 12"
spawn(15)
var/Menu/M = Config.Menus.CreateMenu(Client, /Menu/GameMenu)
Config.Menus.SwapMenu(Client, M)
Config.Events.FadeOut(Time = 13, FinalAlpha = 128)


Expected Results: TitleGraphic object animates upwards 64 pixels

Actual Results:No animation occurs, and no change to pixel_y is observed, however the change is applied server-side, as the debug lines specify that the pixel_y is 0 at first, and then 64.

Does the problem occur:
Every time? Or how often? Every Time
In other games? N/A
In other user accounts? N/A
On other computers? N/A

When does the problem NOT occur?
Is previous build of BYOND (unknown which build specifically)

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)

Workarounds:

Nadrew resolved issue (Not a bug)
Screen objects were never meant to properly animate(), their ability to was actually a bug in itself as it didn't work as expected in most cases.
More information in this topic
Screen objects were never meant to properly animate(), their ability to was actually a bug in itself as it didn't work as expected in most cases.

Screen objects do animate() just fine, provided you use transform, not pixel_x/pixel_y. Pixel offsets were what was never supposed to work with screen objects.
Oh right, it's overlays that can't animate() (unless you constantly add/remove them from overlays and force them to refresh their appearance, which defeats the whole purpose anyways)