this post was submitted on 06 Jul 2023
79 points (100.0% liked)

Godot

127 readers
1 users here now

Welcome to the programming.dev Godot community!

This is a place where you can discuss about anything relating to the Godot game engine. Feel free to ask questions, post tutorials, show off your godot game, etc.

Make sure to follow the Godot CoC while chatting

We have a matrix room that can be used for chatting with other members of the community here

Links

Other Communities

Rules

We have a four strike system in this community where you get warned the first time you break a rule, then given a week ban, then given a year ban, then a permanent ban. Certain actions may bypass this and go straight to permanent ban if severe enough and done with malicious intent

Wormhole

!roguelikedev@programming.dev

Credits

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
Feyter@programming.dev
79
Godot 4.1 is here, smoother, more reliable, and with plenty of new features (godotengine.org)
submitted 1 year ago by simple@lemm.ee to c/godot@programming.dev
6 comments fedilink hide all child comments
 

It's finally here! The wait for Godot 4.2 begins...

top 6 comments
sorted by: hot top controversial new old
[–] simple@lemm.ee 12 points 1 year ago* (last edited 1 year ago) (1 children)

As of 4.1 web exports still have some limitations due to poor vendor support of certain modern features. Browsers with bad WebGL 2 support, such as Chrome on macOS, unfortunately suffer from issues which we cannot address without a fix from Google or a significant amount of effort put into supporting a dedicated WebGL 1 / GLES2 renderer.

We are also aware of the complexity setting up web games on hosting platforms which don’t let you set the required CORS headers for SharedArrayBuffer support. This mostly depends on Safari implementing the coep:credentialless header support, while Chromium-based browsers and Firefox already work fine (especially if you publish on itch.io). There is a possible workaround that we are investigating.

Nice to know that they're aware of all the web issues. As someone mainly using web exports it reaaaally hope they get around to fixing compatibility issues on web exports, and hopefully removing sharedarraybuffers being required.

As always, I blame Apple :P

[–] anlumo@feddit.de 2 points 1 year ago (1 children)

I really hope they won’t remove SharedArrayBuffers. It’s the technology that allows multithreading in a web browser.

Since modern CPUs ship with 16 hardware threads and even 128 thread machines are coming up, it’d let a lot of performance remain on the table that could better be used to improve performance.

[–] simple@lemm.ee 1 points 1 year ago (1 children)

Having the option at least would be nice. I know the benefits of using sharedarraybuffers but right now there are a ton of websites that don't support it. Maybe in a year or two it could be standard.

[–] anlumo@feddit.de 1 points 1 year ago

I can’t speak for the devs, but my feeling is that it would be a lot of work to maintain two systems in parallel, one multithreaded and one singlethreaded, especially for a niche platform.

Bevy does it this way (doesn’t support multithreading at all on the web), but that engine is much leaner.

[–] russmatney@programming.dev 2 points 1 year ago

I'm loving being able to break the docs (script tab) out of the editor!

[–] violetgreendev@programming.dev 2 points 1 year ago

Can't wait to update!