A good emulator will still run slower, however you shouldn't require 5 times the processing power to run an application, that's ineffecient...
But it is emulation, you are using software to emulate hardware, this will always be VERY slow.
I agree, it will be slower, but there could be code optimization that could better utilize the current hardware. e.g. - SMP, HT, Open GL, and Direct 3D to name a few. Look at the power of the current average pc, which can barely run some emulated games, and honestly tell me that it's only slightly better than a game pcb from 10 - 15 years ago?
I understand it's about emulating the ROM exactly, but there is room for improvement, there always is with emulation...
Doing what you are saying would be a "de-provement" to emulation. the emulation is perfect, it's your hardware that can't handle it.
The only 100% accurate way to use hardware acceleration with an emulator is to have the EXACT same chips the original hardware did. That simply isn't possible.
Now things like zinc have come around, but it's been a happy accident.
See zinc only emulates psx arcade games (games that ran on a glorified playstation). They use hardware acceleration. The reason they can is because they "borrowed" the renders from playstation emulators. Playstation emus CAN use hardware acceleration. Why? Because psx emus have been out for years, since the hardware for all playsation discs are exactly the same they can interpret rendering calls from the game code into Dx/Open/Gl ect calls. It's complaicated, but long story short, zinc didn't pop up out of the blue, it was built on the back of over 5 years worth of playstation emus figuring out exactly how the psx video chip works. So zinc is translating code and bypassing the video chip NOT using hardware acceleration to run the emulated code faster.
Mame doesn't work that way. For the most part it's dumb to what is going on. You tell it what chips are on a board, how they plug into the roms, where the rom data is stored, and it just runs the code. It has no clue what the code is or what it does.
In order to use hardware acceleration you have to actually read the code, understand what it does, understand what the rendering calls actually do, and finally write a function to do the Dx/Ogl equivelent.
Long story short, it's frikkin hard to do.
It was done with zinc because given the vast amounts of data/ code available on the psx it was easy to do, in that one particular case.
It still isn't as accurate as mame btw.
To "fix all the slow games in mame" would take not one emulator but several dozen. Each one uses different hardware, each one is coded differently, ect.
On top of that you'd have to find someone willing to actuallywork on these craptastic games. Let's face it, most of these games totally suck, or are available elsewhere.
Crusin is playable with some tweaks as are Ki and Ki2 (on a good system, not a crappy one)
How many console sequels to blitz are there at this point? 30? (all crap, but I digress)
Mk4 is availble on the n64, psx and the gold version (which is better than the arcade) is on the dreamcast.
Sfrush was also ported... even if it weren't it's just not fun unless you are sitting in the cockpit.
Wargods, BioFreaks..... both ported (and both crap anyway)
Mace was on the dc and the n64 as was the gauntlet games.
And this was the point in time at which the arcade games were actually worse than the console ports because consoles were starting to be more powerful than their arcade counter-parts.
So even if it was possible I really don't think it's worth it.
Home
Help
Search
Login
Register
Send this topic
Print
Topic: CHD games not working right, what to do??? (Read 6594 times)
