• Just a reminder that providing specifics on, sharing links to, or naming websites where ROMs can be accessed is against the rules. If your post has any of this information it will be removed.
  • Our friends from the Johto Times are hosting a favorite Pokémon poll - and we'd love for you to participate! Click here for information on how to vote for your favorites!
  • Akari, Selene, Mint, Solana - which Pokémon protagonist is your favorite? Let us know by voting in our poll!
  • Welcome to PokéCommunity! Register now and join one of the best fan communities on the 'net to talk Pokémon and more! We are not affiliated with The Pokémon Company or Nintendo.

Weird flickering when using Graphics.transition?

  • 122
    Posts
    9
    Years
    • Seen Mar 23, 2023
    Hi. I kinda signed up here to ask about this thing. I've been playing around in Essentials 16.1 for a little while now, going through the code and learning all the stuff about it (and in the process, learning Ruby).

    So, I'm not sure if this is a bug with Essentials, or with RMXP, or with my computer, or what, but the Graphics.transition function just does not want to work properly with the default fade. (I have a lovely youtube video RY4yB8izxw4 demonstrating this, but I'm not allowed to post links yet...) It does this strange flickering most of the time, where the screen it's transitioning to flashes up at full for a frame or two before it seemingly tries to finish the transition it didn't properly start. And forget fading out.

    The intro scene was doing the same thing in my project, but it is now fine that a switched it to a wipe transition instead of a fade.

    Google is useless for finding any info on this, and thus I come to you fine folks. Windows 7, 64-bit, if that matters.
     
    So no one else is getting this problem? Only me then? Awesome, awesome.... -_-
     
    This is probably due to Transitions Script Section. Try to use the one on 15.1 version.

    Oh, that worked! I downloaded 15.1 and copied the Transitions Script wholesale over at first. I paired it down to the minimalist backwards changes required.

    Ok, so it looks like the new FadeTransition class is not nearly as good as the built-in fade transition. Simply commenting out lines 95 and 96 in the Transitions section will default the transition back to the built-in transition, which is maybe slower by default, but at least much smoother. I'm curious as to why the fade transition was being reimplemented in the first place...?

    Thanks!
     
    Back
    Top