Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(2 edits)

I forgot to mention a couple of strange technical issues I had that I haven't seen with RPG Maker before.

First, I was playing with a gamepad, but my mouse cursor wouldn't leave the screen.  Even if I moved it to my other monitors, a ghost cursor would still stay stuck in the game window.  I just pushed it as far over to one side as possible.

I also saw a weird corruption/warping effect flicker a couple of times.  It's hard to describe, but it was very brief and random, so I could not get a screenshot.  It happened once in the eastern forest, the other I don't recall where (maybe the same area).

There is one other thing too, which I also saw with another game in FBQ8.  When launching the game, I get the below error popup for a split second.  It goes away when the game finishes launching and doesn't seem to cause any problems, but I have no idea what it means.


(+1)

For the mouse issue, that's due to a plugin that's meant to customize the mouse. I'll just remove that feature for now and stick with the standard mouse cursor.

The warping effect, at least in my case, was due to a driver issue. I noticed it pop up very randomly. But since I rolled back my drivers to a more stable version, I haven't seen it since. I've confirmed this with another user who was experiencing the same thing. Only they updated their drivers, and that solved the issue. Unfortunately, there isn't anything I can do on my end to resolve this.

The NW.js profile issue is due to different RM games using different versions of NW.js. By default, RPG Maker MV/MZ uses specific versions of the NW.js runtime environment, and that version has been known to be the reason for performance/frame rate issues in some games (depending on how hard they dev is pushing the engine with complex eventing, plugins, etc.). Updating this usually improves performance and frame rates, but it's also known to cause the alert that you see now. What's happening is that whenever you play a RPG Maker game, there's an NW.js profile that gets saved locally. If you play an RPG Maker game with a newer version, then go back and play a game that has the default version (like most RM games), then you'll get this alert.

The only solution is to delete the following folders:
\AppData\Local\nwjs\
\AppData\Local\User Data\Default\Web Data
\AppData\Local\User Data\Default\Web Data-journal

It's not a permanent solution though. You'll get the alert again if you play games that have different version of NW.js.