nesdev.org

Relaunch has none of the the old code that I wrote over 10 years ago. New code based off of jsNES, but with a ton of improvements to make it lots faster, uber fast 2x zooming, fixed a bunch of bugs, expanded mapper support, and google search integrated for lots of roms w/out the legal hastle!

http://zelex.net/nezulator

w00t!

Zelex wrote:Relaunch has none of the the old code that I wrote over 10 years ago. New code based off of jsNES, but with a ton of improvements to make it lots faster, uber fast 2x zooming, fixed a bunch of bugs, expanded mapper support, and google search integrated for lots of roms w/out the legal hastle!

http://zelex.net/nezulator

w00t!

I get about 8-10FPS running SMB1 on my Intel core i5 @ 2.6GHz. Is this expected?

I guess speed largely depends on the browser you're using. It probably runs much faster on Chrome, since it compiles JavaScript IIRC.

58-60Fps is what it says for me on Chrome 10, but it still runs very choppy. Good job though. Although, I think a interface like jsNES would be nicer.

Yeah, definitely run in chrome. Firefox and Opera are over twice as slow -- and believe me that this emulator pushes the boundaries of what is possible in javascript. Its a really... really slow language.

I'm working on some changes to squeeze out another 5 fps or so, but it makes a world of difference for my laptop. Hopefully be done this weekend sometime

I got around 6fps in Firefox but a perfect 60 in Chrome. The sound was badly out of sync though, but I didn't even expect it to have any sound. How did you implement sound with JavaScript anyway? This is pretty amazing.

Nezulator wrote:A is Z
B is X

Nope. A is X. B is Z.

tokumaru wrote:I got around 6fps in Firefox

Firefox 3 or Firefox 4?

tokumaru wrote:How did you implement sound with JavaScript anyway?

This page might explain: make a .wav file, base64 encode it as a data: URI, and put it in an <audio> element. The other way is to use an experimental browser-specific audio stream API.

Kasumi wrote:

Nezulator wrote:A is Z
B is X

Nope. A is X. B is Z.

woops. my bad. fixing now

tokumaru wrote:I got around 6fps in Firefox but a perfect 60 in Chrome. The sound was badly out of sync though, but I didn't even expect it to have any sound. How did you implement sound with JavaScript anyway? This is pretty amazing.

Chrome and Firefox have a raw sound api that allows you to do it. It also uses a flash based fallback if your not in firefox. (currently implementing the chrome api). The flash based fallback is why the sound is delayed a bit. Working on implementing the chrome api soon.

Cool. I'm surprised nobody has made a decent emulator for the NES specifically for Chrome and put it on the Chrome Experiments page. I forgot to mention earlier but I also had delayed sound, but apparently you know.


And it'd be nice to add the buttons WSADGHKL as Up,Down,Left,Right,Select,Start,B,A. It's a lot more natural to play that way. And a option to select a file on your computer to play would be needed, as....well...the search sucks. Typed in Mario and the first result was: NES****DiskDude!x¡* *√óÄ Ä* ܪpá*ä*áäæê.......That's not good.

3gengames wrote:Cool. I'm surprised nobody has made a decent emulator for the NES specifically for Chrome and put it on the Chromium projects. I forgot to mention earlier but I also had delayed sound, but apparently you know.


And it'd be nice to add the buttons WSADGHKL as Up,Down,Left,Right,Select,Start,B,A. It's a lot more natural to play that way.

Thats a good idea! I wonder if its hard to put it up there?

My $2 : Making an emulator for a specific browser is, in my opinion as dumb as making a game for a specific emulator.

You're right....lets use IE6 as the basis for all web development and not move forward with open source and high quality 21st technology. But I think we are mainly talking HTML5 tech, not just Chrome alone.