I'm not sure how steam handles it, but as far as the download link posted above for the alternative, it seems to just re-update to v1.3.0.
Wrong installer, lol?
RPG Maker MV v1.3.1: Fixes
● ARCHIVED · READ-ONLY
-
-
remove the beta it's will force a autoUpdate.
That's what I did by accident there's a few hours ago, but thanks for your help.
I'm not sure how steam handles it, but as far as the download link posted above for the alternative, it seems to just re-update to v1.3.0.
Wrong installer, lol?
Well, the auto-update seems to require to be non beta... Aside from that, it goes fine. I guess...
The installer doesn't seems to work for the Steam and bêta issue. -
The intermittent stuttering appears to be fixed for me. It was always intermittent so hopefully it doesn't come back, but initial trials of roaming a 255x255 map seem to point toward promising results.
Thank you! -
I'm going to do more tinkering and troubleshooting to rule out operator error before making an official bug report, but perhaps someone would like to offer some thoughts on this problem I'm having:
I have both the Steam and standalone versions. The Steam version updated to 1.3.1. The standalone installer updated the standalone version's js files, but the "About" still says 1.3.0 so this fits with the explanation above that the exe wasn't updated.
The following problems are happening on both versions (in both old projects and in a fresh project with no plugins):
(1) The WEBGL: INVALID_VALUE error is still appearing in the console. (All js files and index are the latest versions.)
(2) Transferring to a map with a different tileset, and then back to the first map (reloading an already-loaded tileset), causes a blending error around the borders of certain tiles (those with partially transparent pixels, I think). This blending error disappears if I revert rpg_core.js to the 1.3.0 version.
Since no one else has reported this problem I'm leaning toward operator error of some kind at this point. I don't want to bother the staff and devs with a bad report until I can confirm, so I'd like a few others to please test and let me know if you get the same blending error. I have prepared a sample project for an official report if I can get some confirmation that this isn't just me. -
Hey Archeia!
I got the update to 1.3.1 from Steam, but the scrolling flicker still remains. :headshake:
I cannot make use of your download link, as I have a mac and exe-files won't do anything here :unsure:
Hope there will be a proper fix soon...
Thank you and have a great day! :) -
I'm going to do more tinkering and troubleshooting to rule out operator error before making an official bug report, but perhaps someone would like to offer some thoughts on this problem I'm having:
I have both the Steam and standalone versions. The Steam version updated to 1.3.1. The standalone installer updated the standalone version's js files, but the "About" still says 1.3.0 so this fits with the explanation above that the exe wasn't updated.
The following problems are happening on both versions (in both old projects and in a fresh project with no plugins):
(1) The WEBGL: INVALID_VALUE error is still appearing in the console. (All js files and index are the latest versions.)
(2) Transferring to a map with a different tileset, and then back to the first map (reloading an already-loaded tileset), causes a blending error around the borders of certain tiles (those with partially transparent pixels, I think). This blending error disappears if I revert rpg_core.js to the 1.3.0 version.
Since no one else has reported this problem I'm leaning toward operator error of some kind at this point. I don't want to bother the staff and devs with a bad report until I can confirm, so I'd like a few others to please test and let me know if you get the same blending error. I have prepared a sample project for an official report if I can get some confirmation that this isn't just me.
I've tested your sample project and you're all right. There is a problem with the blending and yes, if I create a new project, the "WEBGL: INVALID_VALUE error" appears and I have the same blending error as you, no matter what. I'm using the Steam version too, but not the standalone. Since it's a common problem, it really deserves an official bug report in the Support forums. -
I'm going to do more tinkering and troubleshooting to rule out operator error before making an official bug report, but perhaps someone would like to offer some thoughts on this problem I'm having:
I have both the Steam and standalone versions. The Steam version updated to 1.3.1. The standalone installer updated the standalone version's js files, but the "About" still says 1.3.0 so this fits with the explanation above that the exe wasn't updated.
The following problems are happening on both versions (in both old projects and in a fresh project with no plugins):
(1) The WEBGL: INVALID_VALUE error is still appearing in the console. (All js files and index are the latest versions.)
(2) Transferring to a map with a different tileset, and then back to the first map (reloading an already-loaded tileset), causes a blending error around the borders of certain tiles (those with partially transparent pixels, I think). This blending error disappears if I revert rpg_core.js to the 1.3.0 version.
Same issue :( But don't have a standalone version. -
I've tested your sample project and you're all right. There is a problem with the blending and yes, if I create a new project, the "WEBGL: INVALID_VALUE error" appears and I have the same blending error as you, no matter what. I'm using the Steam version too, but not the standalone. Since it's a common problem, it really deserves an official bug report in the Support forums.
Blending is OK but please do not report invalid_value. We are aware of it and I'm pretty sure that's fixed so I'll recheck again -.- -
Thanks for checking, I'll make an official report in the support forums then.
Edit: posted bug report -
...
#thatmomentwhenyoujustrealizedyouactedlikeadumbperson
Wow Archeia, you are making people be convinced to go to a horrible version? (Sorry, it's just that 1.3.1 didn't work for me)
Well, I uninstalled and reinstalled RPG Maker MV just to make sure it wasn't my fault; and yes, it still doesn't work with me. It doesn't feel like it has changed, since when I click on About, it still says I have 1.3.0.
Well, at least I think it's just the about page that's wrong, the other things should probably be normal.
There was no update to the editor itself, so I am guessing the deployment team chose to not rebuild the editor and include a useless update such as that in the hotfix. Trust me, if the editor was rebuilt it would say 1.3.1, I changed the numbers myself :). Also from the data gathered by reliable sources it seems all the listed changes should be working, please keep in mind updating the engine to use pixi4 is a major overhaul and a few bugs not listed here may still remain.
Edit: It seems the WebGL buffer error may still be occurring, we are looking into it. -
《Bug Reporting》
All reports should go to the RPG Maker MV Boards. Do not make duplicates.
Have 2 little bug here guys.
Strange bug ! my game work but good but , i dont like when i have red in console :)
1: Network dont found some pixi-lib ? But the file are in folder !? its add .map after the .js extention ??
2: In console
WebGL: INVALID_VALUE: bufferData: size == 0 ??
-
I haven't updated yet- but has anyone reported graphical glitches with character sheets bigger than the standard RTP size?
For example I notice that sometimes white pixels briefly go transparent and sometimes pixels next to certain areas can be smeared down or in unusual places.
I have checked several times with my sheets for transparency layers and none of this seems to add up. -
So we can't report the memory leak because it can't be proberbly visualized with only 90 mb projects. Smart move.
-
So we can't report the memory leak because it can't be proberbly visualized with only 90 mb projects. Smart move.
I can't seem to replicate any memory leak in MV, how does that exactly happen to you? And what are your pc specs? Host the project on mediafire maybe?
This hints me you might be using unbelievably huge parallax images but I might be wrong. -
I'm going to suspect what Dalph says here. I'm still on 1.1 and have no memory leak. After all, remember that parallax images have to load into memory their entire size first to be used (and then some extra, as you cannot ever load into memory the exact size of things. Memory is not set up to work like that at all).
And on that note, what would be the best way to go from 1.1 to 1.3.1 if I were to do so? Just download the new link? -
Got a little problem here.
I've done the update to 1.3.1 just now and even though I re-opened RPG Maker, seems the Help>About still shows 1.3.0 and the BGM just refuses to loop, just like it did in 1.3.0.
How can I fix that? -
So we can't report the memory leak because it can't be proberbly visualized with only 90 mb projects. Smart move.
Make a dedicated project, specifically to show off the bug, that is what the project size limit is meant to force people to do. Strip the Music and ALL other assets not needed to display the bug. How LARGE of a file do you really need? If there is a memory leak, it should be visible even with small total project size, instead of your game running away with 500+MB of ram and growing, it will runn off with 200 and growing or something but still should be visible if the problem is there. ALSO remember, that all bug reports are to be done WITHOUT plugins. So if you can not reproduce the bug without plugins then you need to isolate what plugin you are using the makes the bug happen and then contact that plugin's developer about the bug.
This is in no way their attempt at silencing a bug report, this is about making this EASY to work with for everything. Easy for us making a report to upload the affected project, and easy for them to download and USE the affected project to see whats happening and why. When I am helping fix problems for other users of MV, after getting an explenation of the problem, if I can not immediately come up with an answer to the problem that I know will work, I'll ask if theri willing to send me a stripped down version of the project removing all unnecessary assets Because I don't want to download someones 600+ MB project to fix one or two small problems with it, I rather download a 100MB project with only the essentials and bug-fix from there. -
Got a little problem here.
I've done the update to 1.3.1 just now and even though I re-opened RPG Maker, seems the Help>About still shows 1.3.0 and the BGM just refuses to loop, just like it did in 1.3.0.
How can I fix that?
Liquidize said that the programmers chose to not update the editor, since if they did that, then the editor would display v1.3.1 on the About section.
As for the BGM problem...I dunno. -
Make a dedicated project, specifically to show off the bug, that is what the project size limit is meant to force people to do. Strip the Music and ALL other assets not needed to display the bug. How LARGE of a file do you really need? If there is a memory leak, it should be visible even with small total project size, instead of your game running away with 500+MB of ram and growing, it will runn off with 200 and growing or something but still should be visible if the problem is there. ALSO remember, that all bug reports are to be done WITHOUT plugins. So if you can not reproduce the bug without plugins then you need to isolate what plugin you are using the makes the bug happen and then contact that plugin's developer about the bug.
This is in no way their attempt at silencing a bug report, this is about making this EASY to work with for everything. Easy for us making a report to upload the affected project, and easy for them to download and USE the affected project to see whats happening and why. When I am helping fix problems for other users of MV, after getting an explenation of the problem, if I can not immediately come up with an answer to the problem that I know will work, I'll ask if theri willing to send me a stripped down version of the project removing all unnecessary assets Because I don't want to download someones 600+ MB project to fix one or two small problems with it, I rather download a 100MB project with only the essentials and bug-fix from there.
I even say that one of the bug that I had was due to a conflict between two of my plugin, and since they weren't related, I had a hard time to replicate it out of my project. But doing so, I managed to reveal the culprit and correct everything. So no, that's not to silenced people but to help them ! -
I'm going to do more tinkering and troubleshooting to rule out operator error before making an official bug report, but perhaps someone would like to offer some thoughts on this problem I'm having:
I have both the Steam and standalone versions. The Steam version updated to 1.3.1. The standalone installer updated the standalone version's js files, but the "About" still says 1.3.0 so this fits with the explanation above that the exe wasn't updated.
The following problems are happening on both versions (in both old projects and in a fresh project with no plugins):
(1) The WEBGL: INVALID_VALUE error is still appearing in the console. (All js files and index are the latest versions.)
(2) Transferring to a map with a different tileset, and then back to the first map (reloading an already-loaded tileset), causes a blending error around the borders of certain tiles (those with partially transparent pixels, I think). This blending error disappears if I revert rpg_core.js to the 1.3.0 version.
Since no one else has reported this problem I'm leaning toward operator error of some kind at this point. I don't want to bother the staff and devs with a bad report until I can confirm, so I'd like a few others to please test and let me know if you get the same blending error. I have prepared a sample project for an official report if I can get some confirmation that this isn't just me.
I also have the same problem concerning the blending. For exemple, water plants appear with a with contour.