Thanks for feedback.
I’ve introduced new customizable callback to provide own resize window
implementation Introduce resize window callback for html5. by ekharkunov · Pull Request #8799 · defold/defold · GitHub. If everything goes ok - it should be landed into beta branch later.
No just update. The GO doesn’t have any physic component.
@1.8.0 - bob.jar
vulkan backend
/usr/bin/ld: cannot find -lX11-xcb
log.txt (3.2 KB)
openGL backend - build OK
log.txt (1.5 KB)
execution log:
INFO:DLIB: Log server started on port 46779
INFO:ENGINE: Target listening with name: dev - 127.0.1.1 - Linux
INFO:ENGINE: Engine service started on port 8001
INFO:GRAPHICS: Installed graphics device ‘ADAPTER_FAMILY_OPENGL’
INFO:ENGINE: Defold Engine 1.8.0 (210d8bf)
can confirm - same @1.8.0
During the beta test, we found that our attempt to keep Rotation/Euler changes in the GUI backward compatible failed, and it would be better to make APIs clear and separate these properties (to align them with how we handle them in GOs).
Taking this into account, along with the pretty serious changes related to HTML5 (changes in the template and an Emscripten update), we decided to change the version of the beta to 1.8.0 to draw your attention to the breaking changes in this version.
So, there is no 1.7.1 anymore. Instead, the next version will be 1.8.0.
In the latest update of the beta, we fixed the reported (beta) issue of not being able to remove the physics libraries. It has now been remedied, but if you use a custom app manifest, you should take note of these changes.
(ping @aglitchman )
The sprite slice9 issue is now fixed in the latest beta.
Do we have a small(er) repro case for this?
E.g. can I set the finish screen to test it specifically?
(clicking and playing through takes extra time)
Closing the issue as it’s actually due to the change to GUI rotation, not stencils.
Well, a simple rename should suffice I guess?
Or are you using gui rotation in that scene specifically?
Yes, as far as I can tell the issue is resolved by just updating the names and functions.
This one fixed as well
I had a confusion, but it’s 1.7.1, I wrote comments in this thread but the versioning changed only to 1.8.0, right?
HTML5 build
asm.js | wasm | |
---|---|---|
1.7.0 | ||
1.8.0 |
Can you specify a little bit what does it mean? And what did you do?
I ask because I checked on latest beta (cf019276903452e6dab40cea069d73748196b1d0) and everything ok. _asm.js and wasm.js + wasm files presented
I’ve checked (debug builds):
- bundle HTML 5 with both archs (vanilla engine)
- build HTML5 (vanilla engine)
- bundle HTML 5 with both archs (with extensions)
- build HTML5 (with extensions)
sorry for not being clear about the issue.
vanilla engine same version on 1.8.0 beta ...b1d0
building works and run fine.
bundling works fine (debug variant)
tested both in chrome & firefox on linux
wasm build - works
asm.js build - crash
Is there any info you could share? Like a crash log?
Please, provide more info (logs, console output, example project).
crash.txt (5.2 KB)
js-web.zip (1.9 MB)
its sample desktop project from the start screen
PS
same from firefox
console-export-2024-4-16_15-30-52.txt (11.7 KB)
Thanks. I’ll take a look.