-
-
Notifications
You must be signed in to change notification settings - Fork 388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WASM version improvements #9411
Comments
Hi @oleg-derevenetz , could you please look through the proposed list and comment if anything doesn't not make sense or I missed something? Hi @zenseii , would you mind to take a look at possible changes in the documentation? Hi @ololoken , could you please check if any of these tasks can be handled by you? |
I think we need to solve the issue with pthreads first. There is an unmerged (yet) PR to the upstream emscripten repo that should allow us to build fheroes2 with pthreads and throw away all these Emscripten-related crutches for our
I think we can try to do it another way - we can bundle the demo version by default (this way, the user can immediately start playing the demo version), but allow users to use their own game assets. To do this, we will need to refine the UI, but it needs to be refined in any case. Any objections or maybe other suggestions? |
Hi @oleg-derevenetz , While we discussed similar topic regarding usage of demo version in the past and concluded that it should not violate copyright according to its licence file, by shipping the engine with the files from the demo version we might be entering the gray area of law. The license allows to redistribute the demo version but we aren't going to distribute it but our own engine which might be considered as a derived work according to Ubisoft's EULA file. Also, to be consistent with other platforms we should allow to download the demo version but not to ship with it. @zenseii , what is your opinion about this? |
As far as I understand, the demo version that is freely available everywhere has only original 3DO license, which doesn't impose any restrictions related to "creation of derivative work" and other additional restrictions from Ubisoft, and Ubisoft cannot retroactively impose additional restrictions on something that was already shipped on a certain terms by 3DO. It can only impose restrictions on something that it ships now on its own. But I'm not a lawyer and you are right, this looks like a gray area. |
@oleg-derevenetz and @ihhub. As pointed out, the license of the demo doesn't really prevent shipping the demo files, but this might still be enough to provoke Ubisoft to make some sort of action to shut it down or cause trouble. Therefore I think if we can avoid taking one step into the gray area/provoking them, which we have made efforts to avoid up until now, then that is best. It's a risk vs reward situation: will the user experience be so much worse by not shipping the demo files that it makes it worth the risk? |
Slightly updated module launcher https://turch.in/fheroes2/ |
It's better to build launcher as standalone project: no issues with shipping of 3rd party data, I mean wasm build should not contain anything related to licensed materials, even links |
Here is repo with wasm module launcher https://github.com/ololoken/fh2-ems |
Fill free to use https://github.com/ololoken/fh2-ems in any way you want.
Quick test results: in all major desktop browsers ff, chrome and safari build works stable (sometimes pages crashes in chrome, at least I saw it once on XL map day ~40-45); on mobile devices: iphones, ipad, galaxy tab, and some chinese android build stable crashes page in one-two turns on any map, I guess oom. |
I can change the documentation, but since I'm not following every step of the port development, I'm not sure exactly what the final state of the port and its implementation will be like. Is it already good enough for the documentation to be written? |
Hi @zenseii , at the moment WASM version is very unstable and it's not ready for the public. Therefore, we don't need to change documentation as of now. |
I am marking this issue as low priority as we don't want to spend many resources to support an unstable version. |
Btw I've also done a web version in the past (the build is very old at this point). Open the console, click "download demo version" and wait til it is successful :) |
@polybluez , are you offering help in this? |
I guess, if you don't mind. It will take me some time to catch up with what happened since the last time I've worked with fheroes2, though |
Preliminary checks
Describe the problem requiring a solution
We've recently added WASM version of the engine in #9406. However, there are many things we need to do to make this version up to our standards.
Describe the possible solution
This is a list of tasks which we will need to do:
Additional info
No response
The text was updated successfully, but these errors were encountered: