Descriptive Problem Summary:
When using pixel movement, if you set a screen_loc on an object that you can also see on the map (ie: yourself) (even if its not in your screen), this will cause graphical lag. This lag is most likely tied to changing the layer of said object once a screen_loc is applied, as discussed in the comments here.
There will also be an undesirable movement effect on the HUD version of the object if you do actually add it to your screen, due to step_x/y.
ID:120105
 Oct 17 2011, 5:20 am (Edited on Nov 10 2011, 10:05 am)
|
|||||||||||||
Resolved
| |||||||||||||
Pixel offsets have no impact on the HUD. Changing screen_loc is the correct way to handle those cases.
| |
Oh, I thought I was doing it half-assed because of a bug. Nevermind then =)
| |
I did not see any lag in action, but the step_x/y issue was a bug. Keeping the same movement state as the original object I think fits legacy behavior and has not been changed.
| |
Lummox JR resolved issue with message:
Screen objects that also used pixel movement on the map were offset by their step_x and step_y values, when instead those should be ignored on the HUD. | |
I'm not sure if this is how it's supposed to act, but I would assume that pixel_x/y have no bearing on an atoms "physical" position in comparison to it's "visual" position. (I use quotations since technically both positions are entirely visual)