I noticed with TDDP's plugin, as well, that if you re-enter a map that you already loaded, it increases your memory by about 0.5gb even though it's already loaded, meaning that the plugin itself suffers a memory leak issue. This was all tested on a brand new project using only a map overlay plugin and no other plugin or specialty, utilizing parallax maps that were 70x70 and 80x80 in size. After swapping over to this plugin, I went from gaining 0.5gb+ of RAM per map change to 0.1gb~, which is so much more manageable. I know some of you are using this plugin, so I have to recommend a swap over to Hudell's Orange Overlay. With the plugin I was using, however, this problem was magnified by over 500%! I was using TDDP's Bind Pictures to Map plugin, which seems to magnify the memory leak problem to unacceptable and nearly unplayable levels. There is, in fact, an issue where images are kept and never disposed of in MV, meaning that as the player goes through maps with big images (such is the case with parallax mapping), the RAM usage will creep up, up, up, until the game client is reloaded, which would force the images to be disposed. However, after getting so little feedback on the "issue" both on the subreddit and on the RPG Maker forums, I figured the issue might've been in the plugin I was using.Īfter testing, I can conclude that I was both right and wrong. really rather large, and would result in entering a new map eating up half a gigabit of memory. I recently made a post asking if there's a solution to the memory leak problem in RPG Maker MV in regards to parallax mapping.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |