MV 1.3.1 Tile Blending Bug

● ARCHIVED · READ-ONLY
Started by chalkdust 18 posts View original ↗
  1. Are you using plugins? Did you disable them first? Does the bug still happen?


    No plugins.


    Is your bug already reported by another person? Don't make a new topic. Reply to that thread instead if you have anything substantial to add.


    No reports but I have confirmation from 2 other users.


    Bug Explanation:


    Tiles have a yellow border around them from a blending error (seemingly where there are partially transparent pixels?). This occurs after transferring from a map to a new map with a different tileset, and then transferring back to a map using the previously loaded tileset. Everything looks fine the first time each tileset is loaded, but the bug occurs when a tileset is reloaded after being switched out at least once.


    WEYapqI.png


    Error Report:


    N/A


    Exact Steps on How to Replicate Bug:


    (1) Begin on any map. The bug seems most prominent on tiles with partial transparency, so place a few of those on the map.


    (2) Transfer to any other map with a different tileset.


    (3) Reenter a map that uses the previously used tileset.


    Sample Project (REQUIRED):


    https://drive.google.com/open?id=0B3arvarQzHNfNnNRaEJlRS1IUE0


    Filesize: ~20 MB (most audio and graphics stripped)


    Additional Notes:


    Tested on Steam version 1.3.1, and on the standalone version with the 1.3.1 patch. The standalone patch changed the js files but the "About" description in the editor still reads 1.3.0 so I assume the exe wasn't updated. The Steam update did not update pixi.js and pixi-picture.js. They are still the 1.3.0 version dated 8/10. The standalone updater, however, did update pixi.js and pixi-picture.js to the 1.3.1 version dated 8/12. The error occurs in both versions of the engine and with all combinations of these two js files.


    Tested on old projects with updated js files and index from NewData. Also tested on a newly created project. The error occurs on both old and new projects.


    This bug disappears if you revert rpg_core.js to the 1.3.0 version.


    Thanks for all of the hard work on these updates!
  2. My projects become like that too...hope MV fix soon...
  3. Same here I have that bug 2
  4. Something-something premultiplied alpha somewhere. I'll find it.


    Try that one please.


    UPD. WRONG! Take the file in the bottom post below vvvvvvvvvv
  5. This bugs also happens with me, sometimes entering a battle and exiting fix the tileset.
  6. Hackerham said:
    Try that one please.


    View attachment 45061



    @Hackerham, that didn't work, sorry :(

    Note from the original post that I was able to get rid of the bug by reverting to the 1.3.0 version of rpg_core.js. That doesn't prove that the problem is in rpg_core.js (it could be something called by rpg_core.js), but looking at the changelog from 1.3.0 to 1.3.1 might help you narrow it down. I've looked at them side by side and there are some changes related to blending, but I wasn't able to pinpoint the problem any closer than that.
  7. Having the same issue. does anyone have a 1.3.0 core js?


    I only have updated versions :(
  8. Nice catch! 1.3.0 wont help you, but this file will help, 1 line added. I forgot that premultiplied alpha needs to be set before each subTexImageData

    View attachment pixi-tilemap.js
  9. It works on me :)  Thanks @Hackerham :)
  10. Hackerham said:
    Nice catch! 1.3.0 wont help you, but this file will help, 1 line added. I forgot that premultiplied alpha needs to be set before each subTexImageData


    View attachment 45124



    Great! It works fine now, thank you @Hackerham. I hope it will work for the other users, but I think this must be put in the next update for the RMMV.
  11. Hackerham said:
    Nice catch! 1.3.0 wont help you, but this file will help, 1 line added. I forgot that premultiplied alpha needs to be set before each subTexImageData


    View attachment 45124



    Will this be a useful update for all of us to incorporate, even if we're not, as yet, experiencing this phenomenon..?
  12. Dad3353 said:
    Will this be a useful update for all of us to incorporate, even if we're not, as yet, experiencing this phenomenon..?



    Yes. We'll be adding it in the new version.
  13. @Archeia...


    OK, thanks; that's good to know.
  14. Hackerham said:
    this file will help, 1 line added. I forgot that premultiplied alpha needs to be set before each subTexImageData


    View attachment 45124



    Fix confirmed! Awesome work!
  15. Hackerham said:
    Nice catch! 1.3.0 wont help you, but this file will help, 1 line added. I forgot that premultiplied alpha needs to be set before each subTexImageData


    View attachment 45124

    Yoink! I needed this, Thank you!
  16. Hackerham said:
    Nice catch! 1.3.0 wont help you, but this file will help, 1 line added. I forgot that premultiplied alpha needs to be set before each subTexImageData


    View attachment 45124

    Work perfectly - thanks :)
  17. Thanks for this.  We were getting ready to release for Early Access and that bug was killing us.  Thank you for that quick fix!