Games to test Emulators

[Anonymous No.9087573]

What games do you use to see how well the emulators runs?

For example, I can perfectly play the Woodman stage of MM2 and I can tell when something is off.

[Anonymous No.9087576]

>>9087573
What could possibly be off in Wood Man's stage?

[Anonymous No.9087586]

I used SMB3 to test input lag

with that said anyone who claims he can tell when "the emulator is innacurate" is full of shit unless it has to do with graphics or sound

[Anonymous No.9087612]

>testing emulators
Not my problem.

[Anonymous No.9087614]

>>9087576
It's more about to test input lag and stuff.
But it's pretty hard to fuck up NES emulation.

[Anonymous No.9087894]

Turok 3 for GBC. It tends to crash or have graphical glitches on emulators for older handhelds like the GBA and (iirc) DS.

Kid Chameleon for Genesis. If the sound emulation is bad then the music in the first level will peak.

The arcade version of Phelios. It runs slow on every hacked console I have. The only exception being the Wii because it got an official VC release.

[Anonymous No.9088164]

>>9087586
Casual detected.

[Anonymous No.9088260]

NES go to is River City Ransom or Crash n the Boys. They're graphically detailed and have super precise inputs so it's easy to see if something got fucked with the emulation. SNES is usually Mega man 7 because of the same sorta reasons, plus it's fun. GB is Downtown Nekketsu Koushinkyoku for the gameboy because I know that game inside out and can spot an inaccuracy in emulation a mile away. GBC would be Tetris DX because the saves always get fucked if the emulator sucks. GBA I use river city ransom EX because it's demanding on any emulator that sucks ass. Genesis I usually will use Bonanza Brothers cuz imput and sound. SMS I rarely need to test but I use renegade. N64 I use Smash bros. Arcade I usually use whatever is at the top of my rom folder because I don't use em much. I don't emulate anything else for the most part

[Anonymous No.9088296]

Ninja gaiden NES
Wonder boy master system

[Anonymous No.9088302]

>>9087573
Yoshi's Island to test if it's even capable of running special chips. Fun fact, no system before the Switch is capable.

[Anonymous No.9088306]

I get bothered playing melee on dolphin because the load times are not accurate to the real console and it's inconsistent with my memories. Sure, it's the equivalent of being surprised when a favorite CD doesn't have the record skip you were used to from the vinyl you grew up listening to, but it still is off-putting.

[Anonymous No.9088312]

>>9087573
I use whatever's on Retroarch so I don't really need to test for emulators. I did use to test shaders but these days I just play most of my games unfiltered. I used Donkey Kong Country 2 and Mega Man X as tests because I grew up on those games.

[Anonymous No.9088318]

>>9087573
Any Super Mario Bros. game for NES/SNES, Sonic 1 for Genesis. The main thing I check for is sound lag. If I'm hearing the jump sound effect in the middle of the jump and not when I hit the button, it's an issue.

[Anonymous No.9088340]

>>9088318
>i use the single most basic games to test my emulators limits

[Anonymous No.9088363]

>>9087573
What NES game is impossible to emulate?

[Anonymous No.9088367]

I use Super Mario World to test controllers and TVs.

[Anonymous No.9088409]

>>9088340
8- and 16-bit games are so low-effort to emulate that there's really no point in testing their limits. To me, so long as the buttons trigger right and the sound is accurate, there's nothing else to worry about.

[Anonymous No.9088413]

>>9088409
Nigger jenkins. Nigger. Jenkins. Nigger that is jenkins. Jenkins. Nigger.

[Anonymous No.9088502]

>>9088260
How often do you need to test emulators? You test it once and say
>this is good/acceptable
and just play games.

[Anonymous No.9088506]

>>9088502
Are you telling me that this entire thread is bogus? They aren't actually posting about the topic at hand?

[Anonymous No.9088527]

>>9088502
I mean like how it was phrased
>NES go to is River City Ransom or Crash n the Boys.
If you have a "go to" that would imply that you need to test emulators frequently.
My question is you should stop testing, pick a emulator and just play the damn game

[Anonymous No.9088531]

>>9088527
Oy vey.

[Anonymous No.9088637]

>>9088302
What about the Wii? It got SA-1 games on VC.

[Anonymous No.9088645]

>>9087586
Loading timing is easy to tell if you played the games often. An example: Legend of thr Mystical Ninja always took a couple seconds to get to the Konami logo, whereas Super Mario Kart is almost instantaneous to the Nintendo logo.

[Anonymous No.9088647]

>>9088637
That isn't 'emulation', when you need to provide a certain 'gotcha' like this.

[Anonymous No.9088658]

>>9087573
I just use any given Mario game since I too can tell if the inputs are off by miliseconds on that one.
Only things that I really care about are input lag and aspect ratio, other than that, I can tolerate anything when I'm just emulating

[Anonymous No.9088661]

>>9088647
If it's about unofficial emulation, the Wii can do that too. I played Star Fox 2 on Snes9x GX.

[Anonymous No.9088723]

Daffy Duck in Hollywood for SMS
Some emulators can't emulate the music of this game well
https://www.youtube.com/watch?v=vasN-WotnxY
https://www.youtube.com/watch?v=M1hO3nT-cZA

[Anonymous No.9088762]

>>9087573
On genesis most clones fail one of these.
Ristar for shadow highlight scene and cram dots on the water.
Sonic 2 for shadow highlight on bonus stage under the characters, hi rez mode and also correct cram dot behavior on water.
Alex kidd or golden axe will have wrong tones in the music.

GB
Batman and roadrash do midscreen updates.

N64
I don't think I've ever seen goldeneye done right

Sms - road rash
Snes - secret of mana menu is high rez

>>9088363
Elite is pretty hard.
I don't think the action replay code of XLLUUU for super mario bros would ever work on an emulator unless it emulated the composite circuits.

https://youtu.be/8R_eW-5_WDU?t=180

[Anonymous No.9089210]

I use actual test ROMs instead whatever you retards imagine to be accurate

[Anonymous No.9089268]

>>9088527
This people don't play games. They tinker with them.

[Anonymous No.9089297]

Not useful for everyone, but I think the best games to use to test emulation are those you are most familiar with on the original hardware.

For example, I can tell how well an NES emulator handles input delay by running Ninja Gaiden (1). I know exactly how the game feels on original hardware, so anything a certain degree slower or inconsistent immediately feels wrong.

For testing NES graphics/filters, the grass in Willow does the trick for me. Again, I've seen it on a CRT, so I have a comparison point.

I've nothing obvious for NES sound. As long as it is not noticeably corrupted or mistimed, I probably won't notice any problems with sound emulation.

Pic unrelated, but it's what I'm having fun playing right now.

[Anonymous No.9091806]

>>9087573
Gimmick or Mario 3 to test input lag. Usually gimmick.
Also Punch Out.

[Anonymous No.9092227]

>>9089297
This. Everyone has a go-to title to test shit, theres no substitute for experience with real hardware. I use dragons trap for sms, I've played through it hundreds of times on real hardware. Same with Secret of mana on snes. I know instantly when emulation is off with these.

[Anonymous No.9092235]

>>9092227
Just admit you have OCD

[Anonymous No.9092473]

>>9087573
I use Airman's stage to test input lag

[Anonymous No.9092892]

Battletoads NES used to have 1-tile-off collision in a popular emulator at the time (probably NESticle) but that was in ancient times. Anyway that was a fucking nightmare compared to the original experience and made me think I'd gotten worse.

SD3 is a good SNES test because it's swapping resolution on the fly all the time and uses an uncommon special cart for compression IIRC. Most games did neither. You can tell your setup is faulty if you notice the res change a lot, such as by screen filters that can't adapt properly between modes without becoming noticable.

[Anonymous No.9092939]

>>9089297
>I think the best games to use to test emulation are those you are most familiar with on the original hardware.
This. Just this. Why would anyone use [random game] for testing if they don't know it from the original hardware? In case, you're a new kid, forget it, you can't properly test a emulator, unless you have the real thing right by your side. In my case, I've never had a PC Engine, so all I can do is trust strangers on their take about a given emulator and check if said stranger is serious about his thing or is full of inconsistencies.

[Anonymous No.9093931]

>>9092227
>Everyone has a go-to title to test shit
What are you talking about? See >>9088527
How many emulators are you testing?
At that point when you know you have a good working emulator, you'd only be testing particular games and wouldn't have a "go to" game to test, you'd have a "go to" emulator.

[Anonymous No.9094803]

for snes: the rain in zelda

[Anonymous No.9094954]

>>9088340
Sometimes the most basic games are good to test the input lag because they are committed to memory on how they should feel.

[Anonymous No.9095114]

>>9093931
There are always new emulators hitting the scene anon, none of them are perfect (that being said I think higan/bsnes is pretty fucking good) I haven't tried mister yet so I don't know how that implementation fares.