Webcore 64 > EmulatorJS. There, I said it.

[isiguzoflorence521-gif]

When it comes to N64 emulation in the browser, performance is everything. I’ve been leaning heavily toward Webcore 64 lately for that extra bit of speed and accuracy.

For me, the specialized N64 core just handles the heavy lifting better. Has anyone else noticed a performance gap when switching between these two?

[ethanaobrien]

Webcore 64 seems to be heavily written by AI, and their build process is very unclear on what binaries they are publishing making it fundamentally closed source. We do not accept Ai contributed code unless it is heavily reviewed, as time and time again Ai code has been proven to leave open doors that should be closed. This project is older than widespread Ai.

EmulatorJS is fully open source, you're more than welcome to submit PRs to RetroArch or to Mupen64Plus-Next to improve performance

I am a full time student, on top of working a full time job, on top of being the lead-maintainer for several open source projects. EmulatorJS development has been slow recently because I do not currently have much time at all.

Yes, emulatorjs is not the best choice for Nintendo 64 emulation in the web browser on lower end devices, though it's the easiest project I've found to cleanly provide a standard across many different systems. The priority of emulatorJS is to provide a nice, clean UI for various RetroArch cores running on the web. I don't have the experience on how to optimize cores how I would like to.

This appears to just be a post attempting self-promotion, lol. I'm removing your diagram since it's a blatantly simple statement that we don't need a diagram with checkboxes and cancel icons

[isiguzoflorence521-gif]

"I get that you're busy, but 'AI-contributed' doesn't mean 'low performance.' My 'closed source' binaries are actually running Paper Mario while your 'open source' cores are still stuttering. I didn't need a PR to fix the speed—I just picked a better engine. Sorry the diagram hurt your feelings, lol."

[ethanaobrien]

You didn't even remove the quotes before you pasted your chatgpt generated comment...

[isiguzoflorence521-gif]

The 'quotes' don't matter. What matters is the RSP/RDP timing in my /data/n64.js. I manually tuned those paths to avoid the exact audio stuttering issues that EmulatorJS has on Chromebooks. If you want to talk code instead of ChatGPT, let's talk about why your loader.js overhead is killing N64 performance.

[ethanaobrien]

You have no idea what you're talking about. Well, blocked from the organization!