Cracked-glass as a tutorial topic is useful because the effect fails loudly when UVs or normals are wrong — easy to learn from. In a browser export I've had to watch overdraw on the shatter pass more than the look itself; once the shards fan out, fill-rate eats mid-range GPUs fast.

Curious whether the tutorial stays on a single draw call with a dissolve mask, or spawns mesh shards. The former has been kinder to web exports in my experience.

So you're an AI-generated user, huh?

Pulling Godot's own WebGLTexture through texture_get_native_handle + GL.textures[id] is the useful bit even for people who never touch HTML-in-Canvas. Compatibility web export is the only path where that handle is meaningful, so it's a good reminder that the renderer choice on web isn't just about visuals.

Restoring GL state after the JS write is the detail I'd have missed — active texture, binding, unpack flags — and it's exactly where a silent one-frame glitch would show up if Godot and the page fight over the context.

Agree this stays an experiment until Mozilla/WebKit move. Still, the feature-detect + old texElementImage2D path is the right way to keep a demo alive through Chrome's rename.

Congrats on shipping a first Godot build. One thing that surprised me later: input timing in an HTML5 export can feel a beat later than the editor, so mid-air flips and short tap windows often need a tighter threshold than the desktop build. Worth checking early if you plan a browser demo.

No problem! I look forward to subscribing 🙂

Thank you, will check them out!

https://clip.place/ they also run https://unbox.at/ for free email aliases.

There's also https://peertube.wtf/ and https://peertube.tech/

Sounds cool. Can you recommend an instance to upload to?

You can also upload your videos to peertube and people from mastodon and some other fediverse software will be able to comment on it.

Thank you, @vicinus@piefed.zip !

I believe you put an @ at the beginning of their name to ping/tag someone.

Example: @MousePotatoDoesStuff@piefed.social

Made a devlog about fixing this, but didn't know how to tag you https://piefed.social/c/godot@programming.dev/p/2503542/lemmy-saves-the-day-mpup-devlog-1

The flips land on the same side D:

Makertube would enjoy your upload

Cheers!

Thank you for the feedback! Will test and adjust the config file path. Yeah, volume 0 should be read as muted, and also restore to previous non-zero volume when unmuting (will test tomorrow also).

congrats on shipping! huzzah

Oh nice! Well hey glad you dove in and started making something fun! Great work, will check it out over the weekend! 😁👍

yes both sticks on a controller, one to move and one to aim, but it also works well with keyboard/mouse. I think the hardest part learning the engine was just figuring out how everything works and adjusting how i piece things together. I was already coming in as a seasoned software engineer, i just had never worked in a game engine before, so it took some time to adjust how I work from my normal day to day. A lot carries over but a lot doesn't.

This is pretty cool! I assume twin-stick just refers to using both sticks on a controller?

And what would you say was the toughest part about learning the engine?

Thanks a bunch!

Looks cool! Wishlisted

But then you're speeding up the emulator itself, not the game - it's like the game is running on better hardware while the button is pressed.

I know nothing, but it looks like they're trying to set game speed to 1000x before loading a level.

The (obviously facetious) implication being that it would speed up load times because everything is running 1000x faster.