Problem with NW.js versions

You could try my guide here:

I think it's more understandable than most of the others. If the playtest is just a black window, the only reason I ever encountered that is when you minimize the window during startup. Try minimizing and opening it again a couple times, that usually fixes that particular issue. (Or just don't minimize the window of course)

If it's not that, I suppose make sure you really followed the guide and didn't mess anything up. If you need more specific help with this plugin, you need to link to the plugin page, or tell us if it was one that came with MV. We can't mind read and it's not like there is only one singular rumble plugin out there.

Okay thank you, I'll try to follow your guide!

For the minimize tip : I don't think that I can minimize the window since it's just a black screen without any possible interaction (the only way to close it is by closing the 'Game.exe' in the windows task manager).

And btw I did link the plugin I'm talking about (the blue parts in my thread are links that you can click).

I'll tell you if your guide's working!

Xipinjin said:

Okay thank you, I'll try to follow your guide!

For the minimize tip : I don't think that I can minimize the window since it's just a black screen without any possible interaction (the only way to close it is by closing the 'Game.exe' in the windows task manager).

And btw I did link the plugin I'm talking about (the blue parts in my thread are links that you can click).

I'll tell you if your guide's working!

Click to expand...

Ahaha, sorry. I'm using dark mode and they're just white with Fat font. Since you used the fat font in multiple part on the post, I must've overlooked it!

In any case, let me know how it goes. The minimize thing usually just happen when you like.. tab out during the loading. The chance that this was your issue was quite slim I'll admit.

The window not having a top bar is quite curious tho. Usually whenever the game can't load, it'll at least have the regular "window functionality".

In case of NW.js. The one outlined in my guide is already quite high, and there aren't many "newer" versions that are still compatible with MV. If I remember correctly 49.2 is already incompatible, so 50 and above definitely didn't work either.

Hahaha yeah I'm the kind of maniac to use the default white version of the website.

It's still not working...
I had a lot of hope when I saw that, unlike the youtube tutorial, your guide says :

Download both of the links which are purple in this screenshot. The "sdk" version goes into your nwjs-win-test folder, the regular version goes into your nwjs-win folder within your rpg maker files (Not your project folder!).

Click to expand...

So I tried again with the v0.49.2 NW.js but it still didn't work (all it does is opening a small black window in the upper-left side of my screen. The sound of my game start playing but you can't see anything. There's no top bar and no program icon in the windows task bar so I have to close the 'nwjs' program in the task manager to close it.).

I renamed the 'nw' files as 'Game' or 'Game.exe' but it doesn't work. I tried adding the 'www' file into the 'win-test' one but it still doesn't work.

I'm also using a fullscreen plugin so maybe it's his fault or maybe I'm using a too modern version of NW.js but both theories doesn't make sense since I already managed to make the game work well with the ready to rumble plugin in the past and I saw a post of a guy saying he was using the v0.49.2 version without problems.

Thanks again if you have any other tips or propositions!!

Try adding some text to the package json in the 'name' field and see if that changes anything.

Well, you gotta be messing something up somewhere if it doesn't work. My guide says to use 94.0. Anything above that has issues on MV.

The fact that the deafult NW.js does work is a strong indicator that you're doing something wrong when upgrading it. I have just never encountered a black window before. If you forget to rename the NW file, the playtest will just not run.

If you forget to put a name into the package.json file, it throws an error. But never have I heard about a completely black window that doesn't even have the minimize, maximize and X buttons.

bass2yang said:

Try adding some text to the package json in the 'name' field and see if that changes anything.

Click to expand...

That problem wouldn't result in a black window, but throw an actual error message. It's also outlined in my guide, so if OP followed that correctly, they should've done that already.

SGHarlekin said:

Well, you gotta be messing something up somewhere if it doesn't work. My guide says to use 94.0. Anything above that has issues on MV.

The fact that the deafult NW.js does work is a strong indicator that you're doing something wrong when upgrading it. I have just never encountered a black window before. If you forget to rename the NW file, the playtest will just not run.

If you forget to put a name into the package.json file, it throws an error. But never have I heard about a completely black window that doesn't even have the minimize, maximize and X buttons.


That problem wouldn't result in a black window, but throw an actual error message. It's also outlined in my guide, so if OP followed that correctly, they should've done that already.

Click to expand...

I believe earlier nwjs versions do not throw any errors for that if I recall correctly which is why I suggested it when OP said they were using 0.49.2. (Though it has been a while since I've used 0.49.2).

I also use v0.94 and have no issues with any of the Steam stuff currently.

I figured you had it in your guide which is a great resource - just thought it was weird that there was only a blank screen.

Maybe the scene isn't ready and is stuck somewhere? Like a Scene Title or Scene Boot using the .isReady() method (which has happened to me before as well).

Edit: also check your package json for "fullscreen": true which you will need to remove. That one gave me a headache as well. Your plugin should be taking care of the full screen.

bass2yang said:

I believe earlier nwjs versions do not throw any errors for that if I recall correctly which is why I suggested it when OP said they were using 0.49.2. (Though it has been a while since I've used 0.49.2).

I also use v0.94 and have no issues with any of the Steam stuff currently.

I figured you had it in your guide which is a great resource - just thought it was weird that there was only a blank screen.

Maybe the scene isn't ready and is stuck somewhere? Like a Scene Title or Scene Boot using the .isReady() method (which has happened to me before as well).

Edit: also check your package json for "fullscreen": true which you will need to remove. That one gave me a headache as well. Your plugin should be taking care of the full screen.

Click to expand...

Hi again, I'm so sorry for the late reply but I tried to remove the "fullscreen": true in the json package and it worked!!
Thanks a lot but I still have one issue : the json package keeps on reinitialising itself everytime I open the game in the editor.
How do I edit the json package once and for all?

Thanks again for your advice!