Discussion in 'RPG Maker MV Software Updates' started by Archeia, Aug 12, 2016.
Oh, man, oh why....?
Note: open spoiler at own risk.
Self switches appear to no longer work after this update, anyone else experiencing this?
I tested it out earlier and it works for me
In fairness testing with small paralaxes also has a memory leak, but at least with manageable filesizes its not rediculusly insane as it is with 50mb paralaxes. lol
Not having that bug myself, double checked.
We are aware, and as stated we are working on it. It isn't just as simple as "clear the image cache" every so often.
I'm not much of a coder with the complicated stuff. But I can imagine so, trying to manage the cache in way thats effective across the board as to not need to redownload all the images all the time on say a web release version of the engine and having the engine smartly refer to cached images as opposed to reloading the image all the time. Far more complicated than my js knowledge can work with. So I am jealous of all the scriptwriters out there and their capabilities. Sorcery I tell you!
Is KDKW aware of the memory leak too and how long you're trying to fix it?
Again KDKW would not fix the memory leak anyway, probably. In past RM's there were very few, if at all any updates after release, primarily just hotfix updates or adding steam support. "How long you're trying to fix it?" We can't answer that, we cannot discuss our roadmap, or what we have been doing with the engine. I can tell you, that not for very long, upgrading to pixi4 was more of a priority than the memory leak.
Kadokawa doesnt expect users to use RM like that. There is a reason you only have 1 parallax
Just out of curiosity, what is the point of using images over 5000x3000? 50mb each basically, that's insane.
What are you trying to make there?
The size of your game will be ridiculously big at the end, 500mb is already a lot for an rm game (and there are only 6 maps).
Travelling through 50 maps with one parallax per map has the same effect like being on one map with 50 parallax.
Ah, alright. Thanks. That's good to hear I guess? Still a bit shocking that they wouldn't fix something that would go as false advertising in many countries.
Again this project was created just for the purpose of a dramatic effect to display the memory leak. Also If I had used normal sized pictures it would have taken quite the time to create those 50 maps to get up to 1gb. It was faster to create, more dramatic effect. Next time maybe read through a conversation before you decide to take part in it.
How would that go as false advertising? The engine works, when you use it the way they intend you to use it. Their is something called liability, and they aren't liable at all if you don't use the engine the way they designed it too. Just cause it may take more time for a memory leak to appear doesn't mean the engine doesn't work.
Dalph has a point here. 500 mb is already bigger than my ENTIRE game (which is now playable from start to finish), and even after I add the three missing songs to it I doubt I'm going to gain the 200 mb needed to hit 500 mb.
Right now from what I can see brandos' game is looking like it will take up more HD space than FF-Type 0 when done. Just who is going to download and play it?
Parallax mapping certainly isn't part of RPGMaker too so...
worst part is i have to remember my screen resolution and menu fixes T_T
Again this project was created just for the purpose of a dramatic effect to display the memory leak. Also If I had used normal sized pictures it would have taken quite the time to create those 50 maps to get up to 1gb. It was faster to create, more dramatic effect
Oh, so the option to add a parallax map in the map option window is a plugin?
That is one parallax and shouldn't be causing issues if you remember the limits I said earlier.
Sorry to hear that D: In the future remember to make a backup before making an update or change like this, just in case.
The basic purpose of using the option to add a parallax is for adding a sky effect behind the maps, not to make maps without using a Tileset. The parallax mapping was commonly used with RMVX because it didn't have the option to use more than a single Tileset for all the maps. Now that VX Ace and MV offers the option to add more Tilesets, parallax mapping it's almost obsolete. With a proper Tileset configuration, you can do larger maps without using larger images and lagging your project. In my opinion, the parallax mapping is more slower that making a map with the editor itself.
Yeah, I goofed up and overwrote my custom swimming and flying script. It took a few hours to rewrite. As many times as I've done this you would think I would've learned to make backups by now. Operator error, haha.
Separate names with a comma.