MV Playtest randomly crashes, making PC unusable until reset

● ARCHIVED · READ-ONLY
Started by ekhartpl 6 posts View original ↗
  1. For roughly a week, a bit over I'm having massive troubles with MV. They started at 1.6, but I moved back to 1.5.2 - yet the problems still appear.

    Basically, every now and then, without apparent cause, using Playtest function opens game window in basic resolution, completely black. My pc then starts acting up, is very slow and almost unusable, even if I manage to close both game window and MV itself.

    At first I thought that some data on the map got corrupted, as it would crash on transfer from intro to a map. Restored earlier version of the map, but it didn't help. Rolling back to 1.5.2 did help, until today. It crashed again, on a different map this time. The thing is - this map worked perfectly yesterday, and I haven't changed anything since I left it yesterday. Started the program today, playtested the map to see where I left off, and had to reset my PC.

    Strangely enough, testing by using index.html on firefox works with no issue whatsoever.


    I tried to check if Program data is not corrupted (verify integrity on steam), but all files are correct. Now I don't know what do to with this issue - while I can test the game with FF and just avoid using playtest function, I'm afraid that this problem will persist to deployed game.


    I'm attaching list of plugins used, but as I said - I wasn't making any changes in plugins between yesterday's work and today's test.
    RPGMV_2018-03-25_14-03-38.png
  2. Since this error sometimes occurs before the game even launches, I cant help but feel that the issue is related to the TDDP_PreloadManager Plugin you're using. Since it would be applying assets before the game launched, it seems like the most likely culprit.

    Another tip would be to look at the plugins you added since this error has been popping up. This does seem to me to be a plugin error, since its persisting through versions.
  3. I have removed the PreloadManager plugin, and it does seem that it was the culprit. Playtest opened with no issue whatsoever. Hopefully that was the problem, and it's gone for good.

    Thanks!

    Excuse the double post, as I can't bring the thread up without it.

    The issue is back. I haven't changed anything in game again, and playtest stopped working all out of sudden. Again. Had to reset my PC. Now when I'm trying to open my project it says "Unable to read file Game.rpgproject". Restored it (last version from February), now it cannot read System.json. And Plugins.js afterwards. Recovering those three files allowed me to open the project, but now I'm not sure if I should progress with the project on MV, or move back to VXA
  4. You seemed to have experienced a corruption of sorts. I do not how it got corrupted. I don't know if it's something you did or a bug in that specific project (both are possible). You shouldn't base your decision on just corruption. Too many variables to decide and even with the variables, its hard to say if this will be reoccurring or if its just an isolated incident.

    My opinion - I'm open to anyone challenging it
    I'm a little biased on the matter (although I have both Ace and MV). I would say go to VXA unless the ability to play on mobile is that important to you. MV has many good additions but not without consequences. For one, MV is overall weaker in performance (but depending on your game, that might not damage you too much). Their decision to make MV also mobile-available meant they had to lower its overall power so a mobile device can play it with ease. VXA remains PC so it maintains its strong power because most PCs can play a VXA game anyways but a mobile game wouldn't be able to handle it.
  5. @ekhartpl I have merged your two posts for you.
  6. ekhartpl, the issue you are experiencing with the file corruption is most likely due to you removing the pre load plugin I would guess. There may be other plugins causin the issue as well, but with the pre load plugin things are loading differently. removing that plugin means that things have once again been changed, which makes them more likely to corrupt the files. I've never heard of the plugin in question, to be honest but i'm still rather new. I hope you can sort out your issues, MV's positives make up for the negatives, and unless you're making MASSIVE maps (Rpg maker MV only supports maps of up to 256x256 size) its easier to use MV. Javascript is a much more workable language than ruby (Which as far as I know is an rpg maker exclusive language) so there are many reasons to keep doing it.

    I suggest you look at more of Yanflys plugins for any of your needs if you decide to keep going. she has a massive library of plugins, and shes making more all the time. But to be honest, a preload plugin really isn't essential, it ultimately doesnt do anything but risk more bugs.