- Apr 22, 2014
- Reaction score
- First Language
- Primarily Uses
I downloaded and installed. Self installed to root directory. Opened up MV...Nothing new. Still version 1.2
Did you update from 1.2.0 to 1.3.1 directly or first update to 1.3.0? Also did you make sure it was installing the update to the actual install directory of RPGMaker MV?I downloaded and installed. Self installed to root directory. Opened up MV...Nothing new. Still version 1.2
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.
Dalph, it's been stated already that the Devs are aware of the memory leak. If you would Like Dalph I can make a 2 map single default paralax and turn it into a full screencap video displaying memory usage of the game steadily grow as I move between the two maps repeatedly. I won't defend His [Brandos] actions of using unrealistically large images for the parallaxes. But for those who have never noticed this bug, It does Highlight it rather quickly. Unlike smaller paralaxes where it doesnt cause much of an issue unless youve been running the game for a long time.Prove to me that 50 maps with normal parallaxes will eventually cause the same effect, then talk.
Your example is extreme.
Dalph, it's been stated already that the Devs are aware of the memory leak.
How about quality of life stuff? I'd like to be able to have the database open on one of my screens and the map editor/Event Editor on another window. Or be able to keep the plugin help window open and off to the side while I work on my database or events so that I can reference it repeatedly and still edit note tags and script calls without the disjointed feeling of closing and re-opening and refinding my place in the help file repeatedly. Ahhh now that would be amazing.But this would be on a project's topic, and this topic's comment section only serves to analyze the program.
Am I right or wrong?
Oh yeah, forgot about that particular detail.
I'm not understanding much about this "memory leak" thing, but what I can assume I understood is that this means MV consumes too much RAM from the computer, right?I'm not sure if you were aiming the first question at me or generally, but I feel inclined to respond because of my prior post.
From what you say here, you imply that there is nothing else to say once we stop talking about memory leak. I'm sure there are a lot of other things to say positively or negatively regarding MV. A lot of people have reported graphical glitches, audio issues, etc. We can try to be more productive and report bugs or request features that might be useful for everyone, but constantly nagging the devs and demanding fixes is just going to delay production and make people burned out. I own MV too, and I'm frustrated with the bugs and/or lack of certain features, and I do appreciate all the reports and comments other users make since one person can't replicate every single bug out there. I just think it's both useless and annoying to keep reiteritaring the same thing over and over again when the devs have already acknowledged the issue and are actively working on it. There is life after memory leak, after all.
It's not so much that it uses too much RAM, its that when it takes the ram, it doesn't give it back until the program closes.I'm not understanding much about this "memory leak" thing, but what I can assume I understood is that this means MV consumes too much RAM from the computer, right?
Well, consuming memory or not, I still want to say that the pre-made Fantasy database was kind of a good idea though.
Hey, is Aekashics accepting battler requests? 'cause I make a request of a bunny battler for MV in every RPG Maker community that I enter and no one attends my wish, so Aekashics making this battler to me would be great.