Holy cow, how can I fix this problem of MV popping up this notification and playtest getting bricked (with multiple instances of NW.js running)?

[TenraiEmiko]

I have tried and updated the NW.js of MV according to KillerGin's tutorial, but whenever I do so, this annoying notification pops up, and after that, playtest in MV was bricked, and following that were multiple instances of NW.js running in the background... (which I need to run a .bat file to kill these processes)

I have tried several methods of trying to troubleshoot this, including uninstall and reinstall MV, revalidate the files through Steam, and even the last resort: Replacing the new NW.js with the original one that MV has (assume what Gin said in the tutorial was correct)... Even after I did these troubleshooting methods above and started with a fresh new project, this annoying problem still persists...

Are there any way to properly fix this so my MV could run normally again?

Thanks in advance!

 

[TheAM-Dol]

Please take time to use google:

NW.js error

I recieve this pop up when I playtest. I haven't tried exporting to see if it still appears, but it started basically out of nowhere. I've actually tried updating the NW.js by following a tutorial, but I ended up with a new error, "Required value 'name' is invalid.", but luckily I was able to...

forums.rpgmakerweb.com

RMMZ - "profile error occured"???

What does this mean? The person cannot play the games apparently because of this.

forums.rpgmakerweb.com

 

[TenraiEmiko]

Please take time to use google:

NW.js error

I recieve this pop up when I playtest. I haven't tried exporting to see if it still appears, but it started basically out of nowhere. I've actually tried updating the NW.js by following a tutorial, but I ended up with a new error, "Required value 'name' is invalid.", but luckily I was able to...

forums.rpgmakerweb.com

RMMZ - "profile error occured"???

What does this mean? The person cannot play the games apparently because of this.

forums.rpgmakerweb.com

I have tried them, but it is still bricked as all hell...

Maybe it is a call for me to switch to RPG Maker MZ entirely...

 

[TheAM-Dol]

I don't think you read them very thoroughly, or perhaps you have misunderstood the contents of the text.
It's not a problem with RPG Maker.
It's a problem with NW.js, which RPG Maker uses, but it's not RPG Maker.
As I stated in one of those threads:

Basically, when you play an RM game using the default version of NW.js that profile is saved to your local machine. Whenever you play an RM game where the dev may have updated the NW.js, that profile on your local machine gets updated with the new info.
Now, whenever you go and play another RM game that uses the old NW.js version, you will get this warning because it's not going to roll-back the profile saved on your machine.

So in short, upgrading to MZ isn't going to magically fix it because you are "upgrading" the wrong software.

Once again, if you read the thread:

Here:

NWJS-Profile Bug Fix

Hello guys, i have build an .exe that will hopefully solve the "nwjs-profile" bug that occurs sometimes. It automatically delete the folder nwjs, also the files "Web Data" and "Web Data-journal". Let me know if it works or not. regards, Mura

forums.rpgmakerweb.com

As said, it's kind of a bandaid solution as in you gotta use this every time you play an rpg maker game. It essentially just automates deleting 2 folders that are causing this error. You can do this manually as well.

By now, the profile error is a well established "error". It's more of a warning and doesn't really affect anything aside from being a nuisance. It happens when RM games have different NW.js versions. (Some updated, others not so much.) So it will pop back up again likely whenever you play a game made with a different NW.js version than your own project.

Using this software will remove it.

As for MV not working, afaik, this error doesn't affect MV's performance. Since I often play many different RM games, I get the error regularly and in no way has this error harmed the editor's performance. Try using the above exe to fix the error message. If MV continues to perform badly, then there is another problem that has merely coincided with this error message.

 

[TenraiEmiko]

I don't think you read them very thoroughly, or perhaps you have misunderstood the contents of the text.
It's not a problem with RPG Maker.
It's a problem with NW.js, which RPG Maker uses, but it's not RPG Maker.
As I stated in one of those threads:

So in short, upgrading to MZ isn't going to magically fix it because you are "upgrading" the wrong software.

Once again, if you read the thread:

Using this software will remove it.

As for MV not working, afaik, this error doesn't affect MV's performance. Since I often play many different RM games, I get the error regularly and in no way has this error harmed the editor's performance. Try using the above exe to fix the error message. If MV continues to perform badly, then there is another problem that has merely coincided with this error message.

Well, actually, I did use the bugfix software, and the problem still persists...

 

[ATT_Turan]

As said above, that error shouldn't have any impact on RPG Maker games actually working - it shouldn't be able to "brick" your game.

We're not even sure what you mean when you say "playtest in MV was bricked" - did the game lock up? Did you get a crash with an error message? Are you saying clicking the button in the editor did nothing, even after shutting down the duplicate processes and restarting your computer?

Regardless, unfortunately, modding things yourself incurs a risk - if you read through any significant portion of the thread you linked to before trying it, you'll see other people posting that trying to do this caused things in their games to not work correctly anymore.

But if you can give more specific descriptions, people here will try to help you.

 

[TenraiEmiko]

As said above, that error shouldn't have any impact on RPG Maker games actually working - it shouldn't be able to "brick" your game.

We're not even sure what you mean when you say "playtest in MV was bricked" - did the game lock up? Did you get a crash with an error message? Are you saying clicking the button in the editor did nothing, even after shutting down the duplicate processes and restarting your computer?

Regardless, unfortunately, modding things yourself incurs a risk - if you read through any significant portion of the thread you linked to before trying it, you'll see other people posting that trying to do this caused things in their games to not work correctly anymore.

But if you can give more specific descriptions, people here will try to help you.

What exactly happened is when I clicked the playtest button in MV, it did nothing (just a small loading wheel and then no playtest window pops up), and instead multiple instances of NW.js appeared in the Task Manager.

If so, then how I can fix that?

 

[ATT_Turan]

And to be clear, that happens after you've restarted your computer and not done anything else?

And it's happening on a new project?

I can only suspect that you didn't correctly revert the NW.js and got something borked on your system.

This page lists some additional folders on your system that might have duplicate info you need to get rid of.

Uninstall Node.js on Windows 10

I have Node.js installed in my machine with Windows 10. However, I found something weird with Node.js. When doing node -v from the command line, I got the running version as 0.10.28, but I am sure ...

stackoverflow.com

 

[EndlessGame]

same thing happening to me. I upgraded nw.js a while back and that message kept popping up. Was told it was fine, and it was. still get that message but now my playtest doesn't work - not sure if related.

hadn't worked in my game in months, just upgraded my gpu and psu in my pc and decided to get back to work on it... but the playtest button does nothing. in the task manager, there are multiple nw.js running but no game playing.

By the way, this happens even with completely new projects.

 

[bgillisp]

Some PCs cannot run newer nw.js versions at all. Its why MZ had to go back to an older version as they tried to update it and many could not playtest or play the games afterwards. If you hit this issue you really should roll back to the original version of nw.js that comes with the engine.

 

[EndlessGame]

Some PCs cannot run newer nw.js versions at all. Its why MZ had to go back to an older version as they tried to update it and many could not playtest or play the games afterwards. If you hit this issue you really should roll back to the original version of nw.js that comes with the engine.

I'll try that out.

Some PCs cannot run newer nw.js versions at all. Its why MZ had to go back to an older version as they tried to update it and many could not playtest or play the games afterwards. If you hit this issue you really should roll back to the original version of nw.js that comes with the engine.

How would I do this?

 

[TheAM-Dol]

Some PCs cannot run newer nw.js

Agreed, and on a similar note this reminded me: some plugins may be dependant on certain functions that get changed or deprecated in newer versions, which obviously may break functionality. If you followed the guide, it's best to use the version mentioned in the guide and not go to the latest version available.

 

[bgillisp]

I merged your posts, as we prefer you to not post directly below yourself unless 72 hours have passed.

As for how, sadly that I don't know. I just know it is not advised to update it for the reasons I mentioned so never explored the rest. Might have to start a thread asking on how to do that and see if others can advise.