Much thanks for your response. Deleting the folders and keeping the save game files seemed to do the trick and I am no longer getting the NW.js error. However the lockup persists. I will try redownloading the update. / the entire version. . Just curious - I can certainly locate the version 76.1 of the NW.js file, and will download and try that version. I am just wondering what is the best or correct way to update the NW.js file. I am seeing a NW.js file and a Nw.js DLL file and some other files do those all need to be updated?. Any assistance in helping me to update my NW.js file(s) would be greatly appreciated.
Best if you get current advice about updating NW.js for the Windows version of the game from somebody hereabouts that knows exactly how to do it and preferably has done it. The directory structure is different in Linux and I wouldn't want to suggest doing anything that I haven't first tried out myself and wouldn't want to lead you astray without knowing 100% I was offering good advice. Do a search or make a post asking for instructions. With a bit of luck somebody will help you quickly although the thread seems a bit quiet at the moment.
![Thumbs up (y) (y)](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
To be honest I don't think you would have got as far in the game as you have if your NW.js was faulty and reckon it more likely to have something to do with missing or errors relating to the game's files themselves than anything else.
Later: Right I had a chat about upgrading the NW.js of TGO with a Windows user. According to him best to use an earlier version than the one I used with Linux which he reckons probably won't be compatible. According to him version 41.2 works fine with Windows TGO which you can get from:
You must be registered to see the links
and the matching pre-built ffmpeg.dll from:
You must be registered to see the links
Best to try the next bit separately from the game itself, experimentally, to see if it works:
(1) Extract the folder in the downloaded NW.js ZIP file somewhere other than where your actual TGO folder is.
(2) Extract the pre-built ffmpeg.dll into your new NW.js folder overwriting the one supplied.
(3) Rename the new NW.js folder the same as your actual TGO game.
(4) Copy your game's www folder into your new NW.js folder.
(5) Copy your game's package.json file to your new NW.js folder.
(6) Rename the NW.exe file in your new NW.js folder to Game.exe.
And that should be it! When you execute the new Game.exe from that folder TGO should start up with NW.js v.41.2!
(Easiest way to check this is to rename the package.json file temporarily to something else, e.g., package.json_, restart the game to see what NW.js you've renaming package.json back to that afterwards.)
I can't try this myself because I haven't got a Windows box but if you try it out separately to your actual TGO to see what's what you can't do any harm. If all is well you can then replace your original game's folder with the new renamed NW.js folder and play the game from that point on with the new NW.js. Best to copy/move your original version of the game somewhere else before doing this so you can restore it if anything goes wrong. I hope this works for you but, as I say, I'm only the messenger and haven't tried this out myself.
![Thumbs up (y) (y)](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)