-
Notifications
You must be signed in to change notification settings - Fork 1
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
Web build (WASM) #14
Comments
Good progress on WASM build today: https://github.com/nathanleiby/drum-break/compare/4c9c9fa9b8288da73a8d4ce7d382851b33cf822a..66bff4c5c09eb538acbf986744526477392169c4 Got a build working that lets me keep Macroquad with its special wasm build toolchain, but include other One obvious issue has cropped up. The screen is flashing sometimes in WASM build. This is a reported issue for Macroquad web builds: not-fl3/macroquad#471 (comment) In that case, it was due to loading a resource during the loop in a way that's expensive. Could that be my issue? It seems to flash just before a sound is played
Whatever my fix is, I should chime in on the Macroquad issue and share context. Maybe they can close the issue out if it doesn't seem to be a Macroquad isue. Contributing in some way to |
This resolves the 'blinking screen' issue seen in WASM in #14 The approach is to not do repeated reloading of expensive assets. I'm following Kira advice here https://tesselode.github.io/kira/playing-sounds.html > If you want to play a sound multiple times, keep a copy of the StaticSoundData around and clone it each time you pass it to AudioManager::play
Fixed the blinking screen issue ^ f4999f1 |
Why?
Way easier to share and ship iterative improvements.
How?
time
to workconfy
score
history #1, figure out how to store data in web context (local storage? remote datastore?)The text was updated successfully, but these errors were encountered: