MV 1.3.1 Tile Blending Bug
Preserved forum archive. This topic stores the original first post and locally mirrored RPG Maker Web attachments when available. It is posted by the BMMPlay archive account, not by the original creator.
Original Source
- Original title: MV 1.3.1 Tile Blending Bug
- Original author: chalkdust
- Original date: August 13, 2016
- Source thread: https://forums.rpgmakerweb.com/threads/mv-1-3-1-tile-blending-bug.66752/
- Source forum path: Game Development Engines > Legacy Engine Support > RPG Maker MV Support
Summary
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.
Archived First Post
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.
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!
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.
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!
Downloads / Referenced Files
Log in to download
Log in, then follow the RPG Maker Developers Group to see these download links.
Log in to downloadCreator Claims / Removal
If you are the original creator and want this listing reassigned, edited, or removed, join BMMPlay and contact the moderators with proof that matches the original RPG Maker Web profile, linked GitHub, itch.io page, or another public creator identity.
Replies (0)
No replies yet.
Topic Summary
Loading summary...