I _still_ don't get this problem. :/ I can only assume that your CPU is not fast enough. The HQ?X filters are a bit demanding when it comes to CPU power. Nestopia is not a very fast emulator, either.
Neo Kaiser wrote:1.23 was also released!!! This project is moving fast now.
Yeah, I was one of the first ones to download it. The author added triple-buffering, too, which was a feature I requested. He seems very open to requests as far as I can tell.
Neo Kaiser wrote:1.23 was also released!!! This project is moving fast now.
Yeah, I was one of the first ones to download it. The author added triple-buffering, too, which was a feature I requested. He seems very open to requests as far as I can tell.
Yeah and with that Nestopia got the crown. BTW could you change the title of this thread? Just replace the 2 with a 3.
Nestopia is pretty good, but does anybody else find that it runs slow on their computer? I'm thinking this is a pretty resource intensive emulator.
I'm running an AMD T-bird 1.3Ghz with a Geforce 2 Ultra, so I'm pretty sure my system is just not good enough. However, the rest of the NES emulators I have seem to run full speed.
[url=http://transcorp.romhacking.net]TransCorp[/url] - Home of the Dual Orb 2, Cho Mahou Tairyku Wozz, and Emerald Dragon SFC/SNES translations.
[url=http://www.romhacking.net]ROMhacking.net[/url] - The central hub of the ROM hacking community.
With HQ2x, framerate is between 30-60, but never 60 steadily. Scale2x is 60 FPS almost constantly, but occassional slow down. I assume no filter would be steady 60 FPS.
Cool! I thougth you where some Back to the Future fan or something. Guys I don't know why you have resourse problems because Nestopia runs fast on my Pentium 3 800MHz computer with 256SD RAM (Half used for main system) and my video card is a G Force 2 MX of 64 MB.
Hey Marty, have you considered maybe adding a palette editor feature like Nesten has? That's the only reason I keep Nesten around. Would like to toss it in favor of a Nestopia palette function.
Would also like to see an auto-ines header fixing option as a lot of my roms seem to have "garbage" in the header. Thanks!
As far as I can tell, it doesn't have it. You can fix them individually with Nestopia, but it doesn't have an auto-fix option where you don't have to do anything. Maybe I missed that option, so I will check again.
Edit: Nope, still can't find an option to have it auto-save corrected headers. Everytime I load a rom with a bad header, it warns me about it, but doesn't save a corrected version over the old file unless I do it manually.
BTW:
Why can't you use a stand-alone palette editor?
Because I prefer not to. Otherwise I'd just keep using Nesten.
Thanks Jipcy. The only big difference is your video card, but that usually has no effect no NES emulation. I'll forget what settings I have(not at home now). I do remember I was using 2xSAI.. and then i tried Bilinear which shouldn't take much CPU power. Same results with both. A little stutter here and there and my input lagged with Punchout and caused me to lose to Soda Pop! I can usually get to Super Macho man without trying on the real sytem. I'll play around with them again next time I play some NES games.
[url=http://transcorp.romhacking.net]TransCorp[/url] - Home of the Dual Orb 2, Cho Mahou Tairyku Wozz, and Emerald Dragon SFC/SNES translations.
[url=http://www.romhacking.net]ROMhacking.net[/url] - The central hub of the ROM hacking community.
Neo Kaiser wrote:Cool! I thougth you where some Back to the Future fan or something.
Can it be both?
Nightcrawler wrote:Nestopia is pretty good, but does anybody else find that it runs slow on their computer? I'm thinking this is a pretty resource intensive emulator.
It is, due to the LLE. I think your computer should be able to handle it though, at least with the less intensive filters. Seeing that you run it on a notebook, have you tried disabling the high-precision timer?
FirebrandX wrote:Hey Marty, have you considered maybe adding a palette editor feature like Nesten has?
I'll think about it..
FirebrandX wrote:
Edit: Nope, still can't find an option to have it auto-save corrected headers. Everytime I load a rom with a bad header, it warns me about it, but doesn't save a corrected version over the old file unless I do it manually.
I prefer not to mess with files behind the user's back. You can turn off the warning and pretend your files are okay though.
Ok, cool. For a minute I was worried I had overlooked an option for header overwrites. Normally I'd just do it manually, but my archive is too big to do it rom-by-rom. It would take me quite some time that way.
No big deal since we can just turn off the warnings like you said. Thanks for the tip!
For anybody interested, I fixed the problem I was having with Nestopia laggin and running slow.
I guess Vsync was enabled by default or I inadvertainly turned it ontime awhile back and forgot about it. I turned that off and choose Triple Buffering and everything is fine.
I have since bought myself an AMD X2 system for Christmas and have yet to get the time to play any NES ROMs on it yet.
[url=http://transcorp.romhacking.net]TransCorp[/url] - Home of the Dual Orb 2, Cho Mahou Tairyku Wozz, and Emerald Dragon SFC/SNES translations.
[url=http://www.romhacking.net]ROMhacking.net[/url] - The central hub of the ROM hacking community.
I was having a problem with Nestopia, and googling around I found you guys discussing Nestopia in this forum, so I joined to see if anyone can help.
The problem is the following: when I start to play, emulation goes at full 60fps. After a few minutes (5 minutes or so, depends on the filter I'm using, but happens even when no filter is used), the fps starts to gradually drop, until the emulation is slow beyond anything playable.
At first, I thought it might be because I'm running it on a Pentium 3 800Mhz, and it would require something more powerful. But then how come I am able to play it perfectly in the first 5 minutes? Later, I updated the video drivers, the problem still happens but now it will allow for 10 minutes of smooth play before the propblem begins.
By the way, I'm running version 1.24 with vsync enabled (since my video card doesn't suppot triple buffer).