RMMV tips: Upgrade NWJS and Chromium 67,68 64bits

Discussion in 'Learning Javascript' started by Jonforum, Jun 26, 2018.

  1. Jonforum

    Jonforum Veteran Veteran

    Messages:
    1,575
    Likes Received:
    1,344
    Location:
    Canada / Québec
    First Language:
    French
    Primarily Uses:
    RMMV
    upload_2018-6-26_2-27-8.png

    rmmv v.1.6> only

    You keep updating is imperative to fix security breach, but also to optimize your project and get the performance gain that is constantly updating.
    And get all new features update will give to you.

    We go here to see for the beginner how to update nwjs
    No need to wait until RMMV give you an update to stay up to date.

    go here
    https://dl.nwjs.io/

    click on the version that interest you
    Then make sure to choose the SDK version and 64bits if your processor allows it.
    upload_2018-6-26_2-30-41.png




    create a copy [backup clone] of folder (optional security)
    *C\Program Files (x86)\KADOKAWA\RPGMV\nwjs-win-test


    this clone copy will allow you to backup nwjs to the previous version, if you have problems.
    No need backup your game don't worry.
    Then replace all the SDK contents files you have downloaded in the original rmmv nwjs-win-test folder.

    Rename the executable file nw.exe => by game.exe
    You are up to date now and can take advantage of performance and the latest tools offered by nwjs and chromium.


    also use the 64bits version will unlock you very higth performance memory from your gpu.
    Up to 14 Go [14000mo]
    upload_2018-6-26_4-14-10.png

    EDIT: FOR MAC USER. thanks to @elpeleq42
    http://docs.nwjs.io/en/latest/For Users/Package and Distribute/#mac-os-x


    ..........
    So here log of new feature update you will get since the version from rmmv 1.6.1s with nwjs 0.29.0

    example update log: at date i create this tread.
    0.31.3 / 06-25-2018
    • Update Node.js to v10.5.0
    • Fix: chrome://gpu doesn't load
    • Fix: win.print() "copies" option no longer works. (#6440)
    • Fix: crash in nwjc when there is compilation error (#6682)
    • Fix: Support new-win-policy with external sites (#6655)
    • Fix: nw.App.closeAllWindows() crashes on Mac OSX (#6677)
    0.31.2 / 06-14-2018
    0.31.1 / 06-08-2018
    • Update Chromium to 67.0.3396.79
    • Update Node.js to v10.4.0
    • Fix: Pinning app in taskbar is creating an incorrect shortcut target (#5991)
    • Fix: win.getPrinters not receive an array of JSON objects (#6663)
    0.31.0 / 05-30-2018
    • Update Chromium to 67.0.3396.62
    • Add nw.App.startPath to query the directory where the app starts. (#648)
    0.30.5 / 05-18-2018
    • Update Chromium to 66.0.3359.181
    • Support PaymentRequest API in chrome-extension (#6595)
    • Fix: crash when using service worker (#6624)
    • Fix: NW app not launching if RoamingProfileSupportEnabled registry key is set (#6621)
    • Fix: [Linux] Window should be resizable after setting resizable to true (#6609)
    • Fix: [Win] Upload button instead of select on folder picker nwdirectory (#6610)
    • Fix: Dev Tools crash when clearing Memory Profiles with --enable-node-workers (#6615)
    0.30.4 / 05-14-2018
    0.30.3 / 05-10-2018
    • Update Node.js to v10.1.0
    • Fix: Menu and MenuItem leak (#6583)
    • Add support for nwWindow.setShadow(bool) on Mac (Thanks to Jahanzeb Sherwani)
    • Fix: Window resizable false not honored on Linux (#6592)
    • [docs] Add nwWindow.setShadow(bool) on Mac
    0.30.2 / 04-28-2018
    • Update Chromium to 66.0.3359.139
    • Fix: ES6 modules with .mjs extension / loaded from disk are broken (#6585)
    0.30.1 / 04-25-2018
    • Update Node.js to v10.0.0
    • Fix: WebSocket not working on spotify.com (#6527)
    0.30.0 / 04-18-2018
    0.29.4 / 04-07-2018
    • Update Node.js to v9.11.1
    • Fix: window object return in Window.open callback is undefined with redirecting URL (#6392)
    • Fix debug build
    0.29.3 / 03-29-2018
    • Update Node.js to v9.10.0
    • Fix: webview mouse enter / leave not working correctly (#6518)
    • [docs] Add the documentation for win.isAlwaysOnTop (#6536)
    0.29.2 / 03-22-2018
    • Update Chromium to 65.0.3325.181
    • Fix: new-win-policy not working for new window/tab links (#6522)
    • Fix: win.print() "printer" option no longer works. (#6510)
    • Fix: Crash on breakpoints when binary module is used (#6514)
    0.29.1 / 03-14-2018
    • Update Chromium to 65.0.3325.162
    • Update Node.js to v9.8.0
    • Fix: WebUSB device selection menu not appearing (#6500)
    • Fix: Linux tray submenu click causes crash (#6496)
    • Fix: passing --disable-software-rasterizer disables hardware acceleration (#6498)
    • Fix: Pinch zoom does not work on Mac (#6491)
    • Fix: indexedDB.open in node enabled worker completely crashes (#6504)
    more info on full update log
    https://github.com/nwjs/nw.js/blob/nw31/CHANGELOG.md
     
    Last edited: Mar 5, 2019
    #1
  2. TheCosmicSlug

    TheCosmicSlug Veteran Veteran

    Messages:
    46
    Likes Received:
    15
    Location:
    United Kingdom
    First Language:
    English
    Primarily Uses:
    RMMV
    thanks for this infomation, should be helpful :)
     
    #2
  3. Isabella Ava

    Isabella Ava Veteran Veteran

    Messages:
    636
    Likes Received:
    751
    First Language:
    English
    @Jonforum but i cannot run test the game after i replace old nwjs folder with new one
     
    #3
  4. Jonforum

    Jonforum Veteran Veteran

    Messages:
    1,575
    Likes Received:
    1,344
    Location:
    Canada / Québec
    First Language:
    French
    Primarily Uses:
    RMMV
    hum, if i remember, i see similar issue when i was tested and it came from the file v8_context_snapshot.bin,
    i don't have rmmv to test, but you can maybe try to remove this file.
    Or keep the original one.

    If my memory is good, i remember this file does not allow play test in rmmv software.
    Try remove it
     
    #4
    Isabella Ava likes this.
  5. Isabella Ava

    Isabella Ava Veteran Veteran

    Messages:
    636
    Likes Received:
    751
    First Language:
    English
    Thanks JohnForum but that doesn't solve the problem. When i play test it said "cannot found index.html"..
    unless i move all my project's files into this nwjs folder, i cannot play Test =(
     
    #5
  6. Poryg

    Poryg Pixie of the Emvee kingdom, Ham of a Hamster Veteran

    Messages:
    3,786
    Likes Received:
    9,468
    Location:
    Czech Republic
    First Language:
    Czech
    Primarily Uses:
    RMMV
    That's a minor inconvenience though, instead of playtest you'll click save, then go to the project's folder and launch nwjs. The benefits are worth it!
     
    #6
    Isabella Ava and Eliaquim like this.
  7. Jonforum

    Jonforum Veteran Veteran

    Messages:
    1,575
    Likes Received:
    1,344
    Location:
    Canada / Québec
    First Language:
    French
    Primarily Uses:
    RMMV
    @Isabella Ava
    i dont know what to say i just try and it work !!!
    add and replace the new nwjs sdk pack,
    *delete game.exe
    *and rename nw.exe by game.exe
    upload_2018-12-17_23-24-14.png

    i try play test and it work. you maybe do a mistake somewhere?
    Maybe try made a video of gif and i will see if you do something wrong, but i can not help more because it work on my side.
    upload_2018-12-17_23-26-29.png
     
    #7
    Isabella Ava likes this.
  8. Isabella Ava

    Isabella Ava Veteran Veteran

    Messages:
    636
    Likes Received:
    751
    First Language:
    English
    Thank you, i uploaded the video of my progress here, hope it help
     
    #8
    Jonforum likes this.
  9. Jonforum

    Jonforum Veteran Veteran

    Messages:
    1,575
    Likes Received:
    1,344
    Location:
    Canada / Québec
    First Language:
    French
    Primarily Uses:
    RMMV
    Thank for video.
    hum, little question.
    1: what rmmv version are you use, do you use the last one v1.6.1?
    2: Dont forget to always duplicate (backup) folder before experiment.
    3: why you do this in the distribution folder ? do you have a folder named nwjs-win-test instead of nwjs-win ?
    i made you a little screen shot here.
    Untitled-1.jpg
    You will maybe need to reset your software for try again :)
     
    #9
    Isabella Ava likes this.
  10. Isabella Ava

    Isabella Ava Veteran Veteran

    Messages:
    636
    Likes Received:
    751
    First Language:
    English
    @Jonforum I am using MV 1.5.2 because it's compatibility with most of old plugins.
    Perhaps that's why i get this error?
     
    #10
  11. Jonforum

    Jonforum Veteran Veteran

    Messages:
    1,575
    Likes Received:
    1,344
    Location:
    Canada / Québec
    First Language:
    French
    Primarily Uses:
    RMMV
    ok, hum ya i think rmmv 1.5 are seem not compatible for nwjs update.
    They have major change in the core sofware to allow this in 1.6.
    You can only keep nwjs update with the final publish distribution, but you can no use the software to run the last nwjs.

    it good to know is not available, i update the docs.
     
    #11
    Isabella Ava likes this.
  12. Eliaquim

    Eliaquim Raze: The Rakuen Zero's Guardian! Veteran

    Messages:
    615
    Likes Received:
    190
    Location:
    Brazil - Rio de Janeiro
    First Language:
    Portuguese - Br
    Primarily Uses:
    RMMV
    #12
  13. Jonforum

    Jonforum Veteran Veteran

    Messages:
    1,575
    Likes Received:
    1,344
    Location:
    Canada / Québec
    First Language:
    French
    Primarily Uses:
    RMMV
    #13
  14. Peter_Snayde

    Peter_Snayde Villager Member

    Messages:
    9
    Likes Received:
    0
    First Language:
    English
    Primarily Uses:
    RMVXA
    Thank You!
     
    #14
  15. Eliaquim

    Eliaquim Raze: The Rakuen Zero's Guardian! Veteran

    Messages:
    615
    Likes Received:
    190
    Location:
    Brazil - Rio de Janeiro
    First Language:
    Portuguese - Br
    Primarily Uses:
    RMMV
    Hi there! Sorry for the late answer, i was making other things but now i want this to work ^^''
    So, before i try again and see if the error persists, i want to ask you something to see if you can help me (or anyone else).

    You put this:
    When I click on this highlighted part, it takes me into a page that when I click on this page and navigate through it, I finally get to that screen:
    [​IMG]

    But when i click on this part
    i came across this:
    [​IMG]

    So, what of them should i try to download?
    The version 11.7.0 of the first image or the v0.35.5/ 15-Jan-2019 09:35 of the second image?

    Just for you to know:
    RM MV 1.6.1
    WINDOWS 10 64 BITS
     
    #15
  16. peq42_

    peq42_ Yeet Veteran

    Messages:
    452
    Likes Received:
    269
    Location:
    Brazil
    First Language:
    Portuguese(BR)
    Primarily Uses:
    RMMV
    @Eliaquim The first one is NodeJS, the second is NW.js .They're two different things.
    I assume you're trying to update the NW.js(software that is running your game) version , so you can fix a problem with it right? So go to the NW.js page, download the "SDK" version(the first page always shows the last version), and try running your game in it.
     
    #16
    Eliaquim and Jonforum like this.
  17. Eliaquim

    Eliaquim Raze: The Rakuen Zero's Guardian! Veteran

    Messages:
    615
    Likes Received:
    190
    Location:
    Brazil - Rio de Janeiro
    First Language:
    Portuguese - Br
    Primarily Uses:
    RMMV
    Hi! Thanks for answer!
    In fact, it's more for performance gains as the author of the post said.
    Thanks for explaining the difference, I did not really know they were different things even though I have already seen the names many times ^^ ''
     
    #17
  18. Jonforum

    Jonforum Veteran Veteran

    Messages:
    1,575
    Likes Received:
    1,344
    Location:
    Canada / Québec
    First Language:
    French
    Primarily Uses:
    RMMV
    yes nwjs update will give you good performance gain, but also d'ont forget to update the current rendering engine.
    You can bench test all version here and see future features.
    https://forums.rpgmakerweb.com/index.php?threads/next-pixi-v5-bench-demo.104272/
     
    #18
  19. Eliaquim

    Eliaquim Raze: The Rakuen Zero's Guardian! Veteran

    Messages:
    615
    Likes Received:
    190
    Location:
    Brazil - Rio de Janeiro
    First Language:
    Portuguese - Br
    Primarily Uses:
    RMMV
    Hello!
    Hello!
    I had a problem. I managed to make it work with the new nw.js. However, my project was left with a small black bar on each side of the screen, and the image (and the letters) got a bit blurry.
    In other projects, everything was fine. But in that particular, he made that mistake. I also removed all the plugins and checked the package.json, but the problem persisted.
    Here are the images below:

    [​IMG]
    [​IMG]

    So I reversed the previous version as it was. And I received this warning according to the image (in Portuguese-Brazil). Follow the translation:
    [​IMG]

    "Your profile can not be used because it is from a newer version of NW.js. Some resources may not be available. Specify another profile directory or use a newer version of NW.js.

    Please provide feedback to help us correct this problem."


    Seeing this, then I did the update again to version 35.5 as directed. However, the problem persists.
    I'll try to see this part of the rendering as you said right now to see if it works.

    [[EDIT]]

    Well, I tried to venture out with pixi.js and update it on the project. I upgraded to version 4.8.5 and the problem persisted.
    I upgraded to version 5.0.0 and it conflicted with the rpg maker mv code, and the test did not start (I ran those tests with no other plugins installed).
    I was almost giving up and leaving nw.js the same standard way. So I made a little attempt, and I installed the SRD's GameUpgrade.js plugin. And it worked now.
    Before, I had already installed this plugin, but had made a change in its code. So I installed it again, without changing the code. And everything worked.
    Actually, I really have no idea what happened, but it's working now.

    Just to make it clear to someone else, if you have the same problem:
    What I do know is that after I do the update in the nw-win-test folder and replaced the Game.exe by NW.js (and then rename it to Game.exe) the PlayTest has worked and the black borders and a small blurry appeared in the letters and on the screen.
    I removed all the plugins from the project and put the playtest again. The problem persisted.
    I tested other projects with plugin and without plugin, and the problem did not appear. It only affected that same project.
    So I activated all the plugins again and replaced the GameUpgrade.js from the SRD that I had modified by the original. And then it worked.
     
    Last edited: Jan 28, 2019
    #19
  20. EmbarassingMan

    EmbarassingMan Villager Member

    Messages:
    13
    Likes Received:
    2
    First Language:
    italian
    Primarily Uses:
    RMMV
    Brilliant! any hints about how to do the same on a Mac?
     
    #20

Share This Page