Issues with NW.js
Opened this issue · 5 comments
I've been trying to run my game, made using NW.js on boxedwine for some time, in hopes to eventually manage to port it to the web, which would then allow me to port it to any platform(also, would there be any way to make a pre-compiled webassembly version of it?). Issue is, after many attempts, and trying to run it as admin, changing wine back and forth between 1.7 and 5, the boxedwine always crashes.
It spends a big amount of time trying to install 2 things I can't quite remember right now, but one of them is for .net support and the other for HTML applications, and always fails one of the two or both
As far as I know .NET does not work inside Boxedwine. It is a goal in the future to get it running, but first I'm currently focused on getting games from around the year 2000 and before to work and multiple platforms.
It spends a big amount of time trying to install 2 things I can't quite remember right now, but one of them is for .net support and the other for HTML applications, and always fails one of the two or both
IIRC, it's Mono and Gecko. The install is unrelated to the app you're trying to run, I think it's just a default Wine thing.
If I had to guess, Boxedwine's Debian install is probably missing dependencies that NW.js needs to work. I don't know if there's an easy way to install them.
would there be any possible way to add full support to it in the next release? It would help my game project a lot.
With a web assembly version of it, I could port the game to android and the web
Even if nw.js could run on Boxedwine, I doubt the performance would be acceptable in web assembly (WASM). The WASM build of Boxedwine is more of a proof of concept that can run some things that don't require a lot of CPU power.
Even if nw.js could run on Boxedwine, I doubt the performance would be acceptable in web assembly (WASM). The WASM build of Boxedwine is more of a proof of concept that can run some things that don't require a lot of CPU power.
my game isnt very heavy(its a 2D game, and part of its processing was offloaded to GPU). It uses about 10% of my CPU and GPU(ryzen 5 3600 and RTX 2060)