New feature clarification: Animation/transformation

ID:1376474
 
Sep 14 2013, 6:43 am
This is probably a question for lummox:

Older object pixel transformation features (pixel_x and pixel_y) seem to increase view-distance buffering once they pass a certain threshold. Is this also the case for animation and transformation translation?

(I'm hoping it isn't.)
Sep 14 2013, 7:58 am
They would have to, or they wouldn't be visible if their tile was significantly off screen, wouldn't they?
Sep 14 2013, 8:19 am
I wonder how aggressive this is, then, because I'm using transform for a parallax background. Albeit it's in the client's screen, so I don't think it should affect it.

screen_obj
    parent_type = /atom/movable
    starbackground
        icon = 'starbackground.png'
        screen_loc = "1,1"
        layer = 0
        var
            offset = 0
            moving = TRUE
            screen_obj/second
        proc
            parallax()
                var/matrix/M1 = transform
                var/matrix/M2 = second.transform
                while(moving)
                    sleep(world.tick_lag)
                    if(offset==239)
                        M1.Translate(0,240)
                        M2.Translate(0,240)
                        offset = 0
                    else
                        offset++
                        M1.Translate(0,-1)
                        M2.Translate(0,-1)
                    transform = M1
                    second.transform = M2
        New(var/client/c)
            ..()
            second = new/screen_obj()
            second.icon = src.icon
            second.screen_loc = src.screen_loc
            second.layer = src.layer
            second.transform = matrix(1,0,0,0,1,240)
            c.screen += src
            c.screen += second
            spawn()
                src.parallax()
Sep 14 2013, 8:48 am
I would imagine that client.screen doesn't do any culling, and so your code won't really affect it. Maybe Lummox JR can confirm that.