Do you know any RPG Maker RV game I could test this with? Also, I've tested it on a physical windows 7 install and it worked flawlessly. I think Virtualbox and Wine are the problem here (for some reason). I'll try virtualbox without any acceleration, see if that helps. Also, whenever the app crashes with wine, the standard "report problems" window shows up but telling it to "show more details" causes many lines of
0074:fixme:dbghelp:elf_search_auxv can't find symbol in module
to show up and then the window closes and I get no feedback. So I don't even get to read the crash report.
Thank you for responding to my comment.
EDIT: I've tried to repackage the game with nw.js by removing everything except the www folder and the package.json file then unpacking the nw.js zip on the game. I've tried both the SDK and the normal release but both of them got stuck in the Now Loading screen. This happened on a bare metal linux mint install.
EDIT 2: I have tested another RPG Maker NW application (Verdant Village) and it seemed to be working well, although i *did* use their native linux version. I'll try downloading their windows version and try it with wine to see if the problem is Wine or just the game.
EDIT 3: I have made some interesting observations. First of all, running Verdant Village with wine did not work, meaning wine and RPGMaker RT *are* a problematic combination. However, when I used the repackaging technique (remove everything except the package file, add nw.js files in), their game worked flawlessly. I will now try just unpacking the nw.js SDK runtime inside the windows distribution of Ghost Hospital to see if the problem was me removing one too many files.
PS: Sorry for spamming the thread so hard, just needed to give you (and the community) every bit of information I could.
FINAL EDIT: I have found every problem inside the game that's preventing it from booting. I will post it on a separate thread so other users can see it. If you're curious: I debugged the program by opening the index.html in firefox. (I did have to set the privacy.file_unique_origin flag in about.config to false to stop the cross origin request warnings) I then looked at the errors and debugged from there.