- Jan 8, 2013
- Reaction score
- First Language
- Primarily Uses
Yeah, I updated the beginning of the write up so people know its basically a step by step write up for MV users though MZ users can still learn and update their MZ (I just updated my MZ to NW.js version 50, everything is working great. Deployed and test games run just fine)
Um, everything should work just fine. Why not give it another try? Reset MV back to 29.... make sure it works, then retry the steps in the guide.
Remember, the normal (nwjs-win) and test (nwjs-win-test) folders are set up a bit differently.
1) Normal - contains package and www folder, test does not.
2) Test - contains "chrome..." file.
I swear to you that this is not the first time that I have done this, I tried again after seeing the topic and I said to myself "let's try again". Nothing to do, the window seems to open strange. Just like it's not on the right resolution and F4 doesn't work as i said. This is only in Test mode. And the files are correct <_> That's for MV, i remember...
(Did you update NWJS to v.50 despite Orange Green works staying at 49.2?)