Getting emulator timing correct is hard, let's go shopping.
Näytä tämä ketju
-
90% of all WTF code in MAME comes from gradually evolving it from its hacked-up C code roots while not breaking 1000s of games. Now that the main loop calls out to the scheduler (vs *being* the scheduler), your idea could be reasonable. Don't forget to sleep a bit if you can.
Oh, it's not WTF code, it's just code I don't understand. Part of the idea would be to make it easier on the JSMAME folks: MAME's existing throttling method naturally assumes it's the primary thing running on the CPU, which all goes out the window when running in a browser.
-
-
It's compounded by osd_sleep's use of std::this_thread::sleep_for, which Emscripten cross-compiles into a busy-wait. JSMAME ends up running at 100% speed at the cost of eating 100% CPU in the best case, but ping-pongs between 95% and 105% in the worst case.
-
The best I've managed to do so far is to make the normal C++ build of MAME run at about 95% speed instead of 100% speed, but again, I suspect that's due to my own current lack of understanding of the throttling code, and not any deeper issues.
- 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.