[4.4.2.0-4.4.2.2] Global anims seem to take a frame to appear in editor screen

Found a bug in R'n'D? Report it here!

Moderators: Flumminator, Zomis

Post Reply
User avatar
TheOnyxGuy
Posts: 687
Joined: Wed Oct 30, 2013 5:32 am
Location: Russia
Contact:

[4.4.2.0-4.4.2.2] Global anims seem to take a frame to appear in editor screen

Post by TheOnyxGuy »

Some of you may know how I've done quite a few screen locking global anims that prevent you from accessing such screens, especially the experimental levelsets.
Anyways, in the levelset "Level Shuffle", yet again, editor is being protected by a couple of anims, specifically one of them waits for 16 frames and then force exits you. But before that, another anim waits for few frames to appear.
The thing is, the first anim is permanent, it covers the whole screen, using '.class: window' and '.draw_masked: false', it does not 'appear' nor 'disappear' in any way. Yet for some reason on 4.4.2.X versions before immediately showing that large black screen it first darkens everything except the border just for a frame (so the whole screen just becomes RocksScreen.png) before properly cutting to the editor screen global animations.

qwgfqqafqf.png
qwgfqqafqf.png (39.28 KiB) Viewed 48 times

Just for comparison I tried the levelset on 4.4.2.0, 4.4.2.1 and 4.4.2.2, it displays that frame. Trying out on 4.4.1.3 - no such frame appears. Technically that's partly my problem that I didn't set the 'global.border.EDITOR' graphic to NULL, but again, that frame didn't appear in 4.4.1.3, so I'm not sure which change in 4.4.2.0 created it. Plus I'm not sure if it's exclusive to just editor. Of course it's not a big problem, but I'm just a little bit confused.
Previously known as Eizzoux (boooo)
User avatar
Holger
Site Admin
Posts: 4455
Joined: Fri Jun 18, 2004 4:13 pm
Location: Germany
Contact:

Re: [4.4.2.0-4.4.2.2] Global anims seem to take a frame to appear in editor screen

Post by Holger »

This is a perfectly vaild bug report. Even if it may not be that big of a problem here, it may be in other, yet unknown circumstances.

So I will check which change between 4.4.1.3 and 4.4.2.0 introduced the different behavior, and check why it has the described side effect.
Post Reply