[solved]Change or transform an image already on the screen?

[angelicdreamweaver]

Can I refer to an already shown image that is constantly panning and change the tint afterwards at a specific point in the story?
Because of the panning, I cannot simply hide the image and show it again with the new tinting values.

So far, I came up with this, using an invisible white tint as a timer - but I don't know how many seconds the reader needs to arrive at the place where it should start to get darker around him.

Code: Select all

show bgroom at pan:
	linear 60 matrixcolor TintMatrix("#ffffff00")
	linear 10 matrixcolor TintMatrix("#fa8e60")

[m_from_space]

Because of the panning, I cannot simply hide the image and show it again with the new tinting values.

Actually, you can. Just use the "animation" keyword, so the panning animation isn't restarted.

Code: Select all

transform atl_tint:
    # make sure to put this here first, before changing it
    matrixcolor TintMatrix("#fff")
    # now change it
    linear 10.0 matrixcolor TintMatrix("#fa8e60")

transform atl_pan:
    animation
    xoffset 0
    # put your pan code here, e.g.
    linear 5.0 xoffset 500
    linear 5.0 xoffset 0
    repeat

label start:
    show myimage at atl_pan
    "Here we didn't arrive at the point in the story."
    show myimage at atl_tint, atl_pan
    "Now we just did..."

So far, I came up with this, using an invisible white tint as a timer.

The alpha channel is not touched with TintMatrix(), so there is no invisible tint. It's just that tinting with "#fff" (white) means no tinting at all.

[Ocelot]

Fun fact: order of transforms at the second show is important. If you change order of those two, you will have problems.
Here is some information on replacing transforms and transform order: https://www.renpy.org/doc/html/atl.html ... transforms

[angelicdreamweaver]

Actually, you can. Just use the "animation" keyword, so the panning animation isn't restarted.

Nice, thank you! It almost works, though there is a noticeable jump forward by perhaps 100 pixel or so in the panning.
I am using "linear 333.0 xpan 360" and not xoffset. Adding the "xoffset 0" above didn't help, the two animations are not quite aligned in the timing - but almost. Weird...?

[Ocelot]

What I wrote in previous post is very important. Are you sure that previous image pan is replaced be a new image pan? If for the original image pan was the last transform applied, then for newly showed image it should be last transform applied too.

[angelicdreamweaver]

What I wrote in previous post is very important. Are you sure that previous image pan is replaced be a new image pan? If for the original image pan was the last transform applied, then for newly showed image it should be last transform applied too.

Well, I changed the order of the two transform calls behind "at" - and the result is the same: Both work well, the tint begins correctly, but both have that jump before.

Code: Select all

transform pan:
        animation
        subpixel True
        linear 333.0 xpan 360
        repeat

transform gettingdarker:
        matrixcolor TintMatrix("#fff")
        linear 10.0 matrixcolor TintMatrix("#fa8e60")
        
show bgroom at pan

### (some lines of narration)
        
show bgroom at pan, gettingdarker
# works the same: show bgroom at gettingdarker, pan

[m_from_space]

Both work well, the tint begins correctly, but both have that jump before.

The reason is that you didn't set a default value for that property you are changing. You should always do that (the same reason you're doing it with the matrixcolor property). xpan wants a float by the way.

Code: Select all

transform pan:
    animation
    subpixel True
    xpan 0.0 # default value is important!
    linear 333.0 xpan 360.0
    repeat

[angelicdreamweaver]

The reason is that you didn't set a default value for that property you are changing.
xpan wants a float by the way.

Thanks, I changed both... but it still does the same than before, that weird jump forward in the panning.

[m_from_space]

The reason is that you didn't set a default value for that property you are changing.
xpan wants a float by the way.

Thanks, I changed both... but it still does the same than before, that weird jump forward in the panning.

Probably because of the wrong order like @Ocelot stated. Because on my end it works.

[angelicdreamweaver]

Probably because of the wrong order like @Ocelot stated. Because on my end it works.

How weird! When I do it, it doesn't matter what order the transforms are called. I always have that jump foward during the panning.

[Ocelot]

Show you current code for both transforms and how you display it.

[angelicdreamweaver]

Nothing has changed from what I posted earlier in #6 ...
Thank you for looking into this!

[Ocelot]

Adding default value and fixing order of transform fixed the issue for me in the new project:

Code: Select all

transform pan:
    animation
    subpixel True
    xpan 0
    linear 33.0 xpan 360
    repeat

transform gettingdarker:
    matrixcolor TintMatrix("#fff")
    linear 10.0 matrixcolor TintMatrix("#fa8e60")
        
label start:
    show bg room  at pan
    "well..."
    show bg room  at gettingdarker, pan
    "333"
    return

[angelicdreamweaver]

I actually did have the xpan 0 in there as well. Now when I tested it again, copying the lines in the same place, it worked fabulous. Don't know what was wrong before. Thank you!