Home Page Forums Other Emulator Message Boards Nestopia Nestopia 1.41 unofficial release

Yeah I saw that post a while back in my quest to solve this problem, and while it didn't help me with nestopia, it did fix some other problems by bumping the clock rate.


Yeah if only I could find a non-Creative card that works as well in 3D games (new and old), I'd ditch this one in a heartbeat.

I've been having the same problems with skipping audio on my system, but I'm not very knowledgeable about all the technical stuff and I don't want to break my sound. :-/ I'm seeing 18 sound drivers, and I'm not sure how to tell which (if any) is causing a problem for me. I see several by Microsoft, IDT, and SRS Labs. Apparently Microsoft is good, but are there any known problems with the others? I can give more details if you need, but I'm not sure what you'd need to know.... v_v

*crickets chirping*

...Anybody? :-/

I still have the input lag when vsync is enabled. It's a little bit better, but I still can notice it in Mike Tyson's Punch Out - it's enough to affect the gameplay. My specs:

Windows 7 x64
ATI 5850 with latest CATs installed
Core i7
4GB of RAM
Resolution at 1280x720 @ 60Hz

Timing:
Synchronize to Refresh Rate
VSync
Use high-precision timer
Enable triple buffering
Default speed

I'm using a Logitech Rumblepad 2 if that makes any difference. Disabling vsync resolves the input lag, but I get screen tearing of course.

First, I want to say thank you to c0d3h4x0r for updating this emulator. I downloaded the emulator from your link, unzipped it, didn't touch any of the settings, and opened up Super Mario Bros in full screen. Unfortunately I still seem to have the lag on my controller when vsync is enabled. And if I disable vsync I get the screen tearing. Any advice?

Woah!!!

This is great news!

I am surprised that somebody took it upon themselves to continue where the original Author left off.

It's sad that the original Author has abandoned his creation & if he could only be contacted I'd really want him to answer a few questions that has bugged me after he released version 1.38 of the emulator.

First off, why did he removed the emulator's support, or rather the emulator's ability to recognize & emulate games that use a few Mappers, mostly once used by Unlicensed &/or prototype games such a Free Fall? I know a lot of these games that uses the mapper boards he removed support from his emulator are bad games, but still they are a part of the rich history that the NES/FamiCom had. Instead of removing mappers, shouldn't he had added more, so that the emulator could be "perfect"?

My next question is, why did he make his emulator so "perfect" that it will not recognize & run ROMs that are hard patched with translations &/or ROM Hacks? Sure to compensate he did made it so that soft patching will work, but a lot of ROM Hackers are avoiding Nestopia like the plague because of this feature.

Because of those two improvements, I've stuck with version 1.37 of the emulator & I'd really would have loved it if the 2xSAI filter was already present in that version LOL!

To be honest, I absolutely love this emulator especially since it's currently the one I use that is capable of emulating the FamiCom Disk System perfectly A lot of people say that FCEUX beats Nestopia, but I could never get that damn emulator to run FDS Games, even though both emulators use the "disksys.rom" ROM Image of the FDS BIOS.

I wish you sir would consider re-adding those mappers the original Author took out or even add a few more, so the emulator can play a lot more stuff. And I also hope you can do something about that "modified ROM identified, I will not run/load this" issue as well

This is just a wild guess, but I expect it's because it's senseless to shit up an internal DB with such magnum opuses as "Penis Mario" and such.


Not to be too snarky, since you're not agreeing with those people, but a lot of people say pretty stupid things, that being one of them. I'd be curious to hear one of those people give details as to the universe they live in, because I personally would like to know in what universe FCEUX "beats" Nestopia. Certainly not one where accuracy is king, because in that regard FCEUX is shit.

AFAIK NST will load things that aren't in the database according to standard iNES rules, but of course there's no guarantee it gets things right in the many ambiguous cases.

As far as hacks/patches, I think soft patching is preferable - it uses less disk space, and it keeps the total number of ROMs you have more manageable.

The translations he's talking about are of games with "bad" iNES mappers--cases where two incompatible boards got lumped under the same mapper number, so that you need either an internal DB or some kind of heuristic identification (ugh) to emulate the iNES-format ROM.

As far as I can tell, ROM Hackers love FCEUX because of the fact that it is not such a bitch with Fan Translation & Hack patches & they are raving about the emulator's debugger that as the claim is way more friendlier than Nestopia's.

But I couldn't agree with you more that FCEUX IS NOT better than Nestopia.


Also, most NES ROM Fan Translations that were made prior to 2004 are hosted on ROMs hosting sites pre-patched onto the target ROM so you essentially will be getting a modified ROM off hand & if Nestopia doesn't like these off hand then it kinda is of a bother.