Animating Client.pixel_y/x

ID:1981625
 
Nov 13 2015, 8:03 am
Not a bug
BYOND Version:509* (use Other instead; specify full version number)
Operating System:Windows 10 Enterprise 64-bit
Web Browser:Chrome 46.0.2490.86
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.
Both client and server are running the latest version of the beta, I think client.pixel_x/y is beta, but if I'm wrong, please do forgive me!


Sometimes when animating client.pixel_x/y the viewport fails to render what's beyond the range, but not always? It's very difficult to pin down, but it seems as though in a test environment where certain conditions are met based off your eye's x/y and step_x/y, it fails to render, but moving slightly fixes it.

I'll reply back to this with as much information as I can, but I can't promise it'll be too helpful outside of some gifs of it happening.

        shakeCamera(var/attDir,var/intensity = 20,var/duration = 5)
            animate(client)
            client.pixel_y = (!!(attDir & NORTH) - !!(attDir & SOUTH)) * intensity
            client.pixel_x = (!!(attDir & EAST) - !!(attDir & WEST)) * intensity
            animate(client, pixel_y = 0, pixel_x = 0, time = duration, easing=ELASTIC_EASING)

    verb
        _DEBUGshake()
            shakeCamera(dir,200,100)
Nov 13 2015, 8:08 am


I try using shake whilst facing NORTH, screen fails to render.


I move up slightly, and do the same

Nov 13 2015, 10:23 am
GatewayRa recommended playing with client.perspective, I can confirm it makes no difference the issue still happens. If it helps.
Nov 13 2015, 11:13 am
Lummox JR resolved issue (Not a bug)
Nov 13 2015, 11:15 am
This is a known limitation of client pixel animation that was discussed multiple times, in both the release notes and in development news. Feature request maybe, bug no.
Nov 13 2015, 11:36 am
What's the limitation? Why does it sometimes happen and sometimes not? What's the case I should be avoiding?

Lummox said:

Some additional information might help here
Nov 13 2015, 1:13 pm
The problem is that you're going well beyond one tile. The map on the client does not have any information to work with past a certain point, and the server is currently unable to anticipate the need past a certain point. (Rather, it will try to adjust the map center based on the animation endpoint.)
Nov 13 2015, 1:14 pm
In response to Lummox JR
Lummox JR wrote:
The problem is that you're going well beyond one tile. The map on the client does not have any information to work with past a certain point, and the server is currently unable to anticipate the need past a certain point. (Rather, it will try to adjust the map center based on the animation endpoint.)

So why does it work 50% of the time, even on areas of the map I haven't explored.
Nov 13 2015, 1:19 pm
The times it works, the server has already sent the info you need, and importantly has not removed tiles that need to stay in view. The reasons for that are really too complex to go over in any detail, but the basics of it are that client.pixel animations past one tile simply haven't been handled yet.