The issue is because you have tiles with a star passage, and you put them down, and then you put down tiles that don't have a star passage. The editor shows them in the order you drew them, which may not be the same order / priority they're displayed with in-game. This issue has been here since the very first MV and at that time we were told changing the editor was too risky.
In short - if you put down B-E tiles that you don't want there, actually erase them, rather than just covering them with other tiles, because with the 2 upper layers, just because you can't see them doesn't mean they're not there.
RPG Maker MV v1.3.1: Fixes
● ARCHIVED · READ-ONLY
-
-
I too am waiting for the memory leak fix, I don't want a situation where the player has the game running on a tab and then over time disaster happens putting the blame solely on my shoulders. With that said **Warning mini rant**
This is really the only industry where it is socially acceptable to commonly use the phrase "whenever we get around to it" food, art, music, ect this would not only be rejected but could potentially get sued. The only industry that sort of comes close to this is TV hardware, but even then if you took it home, booted it up, and it powered down and started acting funny after so many hours, you would get a response like these found here on this site. "It will be fixed when it's fixed" or my recent favorite "Meh who needs to play that long anyway?" ...while you community including myself is willing to accept these social standards of software development there is a limit to how many times responses like that don't garnish backlash.
To the users understand that you have very very little ground to stand on, even in the worst case hypothetical situation where they supply no more updates and not work on anything more, the most that will happen is Enterbrain will find a different publisher leaving you the fans out in the cold. So be nice, and wait as I have, heck I'm still waiting for my refund on member+ and that was way back. Memory leak will be fixed (if its fixed at all) in due time. -
MV 1.3 now works with updated versions of nw.js, though they seemed slower on my tests.
-
@Mako Yea basically this, but I think conversation diverged away from that topic far enough back. people get it, doesn't make them any less antsy about it though. As you yourself just said, you don't want your game to cause problems with the consumers, neither do any of us. :3 I myself am happy to watch and wait, as they have proven to me so far that they haven't left us in the dark and are working on things. Even more so as one Dev stated, they were Hired to fix bug's in the Editor. Them working on the Engine it'self is a bonus. [though that may only apply to that single Dev. XD] I look forward to each incrimental Update that leads us closer to a Final state where there are no catastrophic bugs.
Though if anyone can update that old script that was used to occasionally clear the image cache, that would be at least a bandaid for now. -
MV 1.3 now works with updated versions of nw.js, though they seemed slower on my tests.
Nice seeing you here, Hudell!
That's strange tho.
I came back to show you something about MV that can't be unseen:

(If the names look strange, sorry, my system and copy of RMMV are on PT-BR)
HTMLFIVE = HTML FIVE = HTML5 -
Yea, It's a long running gag that they spell something out with the actor names. It was only natural for MV to have HTML spelled out and FIVE spelled out with the additional Database entriies. :D
-
Am I the only one who is getting the "Now Loading" screen more often now with 1.3(.1) ?
-
My problem which I reported here was only occurred by compatibility with the plugin "TDDP_BindPicturesto map" in ver. 1.3.1.Sorry about that.
-
Though if anyone can update that old script that was used to occasionally clear the image cache, that would be at least a bandaid for now.
What old script, and why doesn't it work with 1.3.1? I wrote a cache clearer plugin and unless they've drastically changed how the ImageManager works, I don't see why it wouldn't work still. -
if what @Hudell said was true and we can update to the latest version of NwJs this mean we can use now ES6 features.
wich is REALLY great for organisation sakes.
and most ALL the most popular internet browser support ES6
if Degica decide to update the NwJs to the latest version I will make sure to update aswell the default library to es6
but after it's ONLY if they decide xD -
if what @Hudell said was true and we can update to the latest version of NwJs this mean we can use now ES6 features.
wich is REALLY great for organisation sakes.
and most ALL the most popular internet browser support ES6
if Degica decide to update the NwJs to the latest version I will make sure to update aswell the default library to es6
but after it's ONLY if they decide xD
not many mobile browsers or webViews support ES2015 -
What old script, and why doesn't it work with 1.3.1? I wrote a cache clearer plugin and unless they've drastically changed how the ImageManager works, I don't see why it wouldn't work still.
Back a few pages Brandos posted this script :
/*:
* @param Save File Index
* @desc The temporary index of the save file pre-saved and preloaded per transfer.
* @default 1
*/
var mapTransferredCounts = 0;
var params = PluginManager.parameters('X_MapSaveFix');
var saveFileIndex = Number(params['Save File Index']);
var x_sceneMap_update = Scene_Map.prototype.update;
Scene_Map.prototype.update = function() {
x_sceneMap_update.call(this);
if (mapTransferredCounts >= 10) {
$gameSystem.onBeforeSave();
if (DataManager.saveGame(saveFileIndex)) {
mapTransferredCounts = 0;
StorageManager.cleanBackup(saveFileIndex);
this.reloadMapIfUpdated();
$gameSystem.onAfterLoad();
SceneManager.goto(Scene_Map);
ImageManager.clear();
}
}
};
Scene_Map.prototype.reloadMapIfUpdated = function() {
if ($gameSystem.versionId() !== $dataSystem.versionId) {
$gamePlayer.reserveTransfer($gameMap.mapId(), $gamePlayer.x, $gamePlayer.y);
$gamePlayer.requestMapReload();
}
};
var x_gameInterpreter_command201 = Game_Interpreter.prototype.command201;
Game_Interpreter.prototype.command201 = function() {
mapTransferredCounts += 1;
x_gameInterpreter_command201.call(this);
};
I can't javascript for beans so I dunno what changed that makes this script not work anymore. But that's his claim about it anyway.I assume its the change to pixi4 and how pixi4 handles image data vs how pixi2 handled image data. -
1.3.1 just got an update for beta but so far it's steam only, we'll try to update asap :)
-
It seems like there's currently a problem regarding WebGL filters, which was fixed yesterday: http://www.html5gamedevs.com/topic/24493-converting-a-filter-to-pixi-v4/?do=findComment&comment=140105
Maybe you could include this in a future bugfix version.
/edit: The latest update doesn't seem to include the fix, yet. -
1.3.1 just got an update for beta but so far it's steam only, we'll try to update asap :)
Pixi.js stuffs updated this morning. :D -
not many mobile browsers or webViews support ES2015
Honestly this why I said "IF"
I would make a conversion so people can use it if they want on the desktop version. -
Thank you for the new update! Everything seems to be working very well, but- and I apologize in advance if this is a question with an obvious answer- I am unsure as to how to put the Fantasy Database into my current project. EDIT nevermind, I figured out how to do it.
-
1.3.1 just got an update for beta but so far it's steam only, we'll try to update asap :)
Looks like the error from the Dev Editor disappeared with this update, with all the bugs from Tilesets too. Thank you so much! -
Just uploaded the latest version of 1.3.1! Opening topic posts the new changes. Please update everyone!
-
Waouw, thanks for the update !