So, to be clear - the WebAssembly Emularity build is NOT falling back if you don't have WASM up and running. We'll fix it, of course.
-
Now that we are actually compiling to Web assembly, we can finally go back and optimization makes more sense
Great, so circling back to the original question, how are the sound and performance "weird"?
-
-
Calling in
@DopefishJustin who knows how to phrase this more competently than I do -
My understanding, which he can correct, is there is a very slight synchronization issue with frames between our scripting and the browser
- Näytä vastaukset
Uusi keskustelu -
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.