Yes, klogg you're right. Altmer (Max) has made some new stuff with emulator. And the stage of alfa test has end. At this moment emulator manage to lunch (and you can really play) games what in past versions can not work correctly - SPACE HULK (not stuck any more in close combat), MICROCOSM - playable again, PABBLE BEACH GOLF LINKS - do not show error and not shutdown emulator anymore. And many other great stuff. Like: save/load state, joustick pluggin system & e.t.c.

All there very simple (in my opinion ). Or you need someone to translate meaning of some options in emulator? If so - say what you want to know and I'll try to translate (but I'am sure all this easy to translate just using even Google translater)

Im sure it would but i couldnt be bothered to figure it out really. As soon as I saw killing time only running 40fps and sound skipping again (like all versions after 1.7) I stopped caring. but im on vista if anyone wants to try and tell me how to get the words to show up right and maybe I will try again if I have the time.

PS did anyone ever figure out the exact cause of that bug in previous versions after 1.7? quadcore processors? vista 32-bit? 1.7 works great for me, fullspeed easily.

How I figured out (by my experience), on Vista new version - runs awful When the beta-test begins - I've tested emulator on CoreQuad - and I must say it was GEAT! Full speed, no sound bugs, full screen, 60 fps. But when I tried to test the same game on the same PC with Vista - it was disaster: top fps - 40 and sound bugs was was rewarded from Microsoft

So if you wanna have good game - play it on XP

PS. About "how to get the words to show up right" - if you don't want to install russian language (how already advised Zombie13), I'll try to translate some basic options of emulator...

BryWI wrote:I guess that bug is a vista thing then. Must be something in the code thats making it act up weird with vista.

Not a bug and not related to Vista either. I only get ???s as well. Reason is simple: It's not compiled as unicode. XP and on are unicode-only and have a conversion layer for non-unicode applications, but that doesn't work well. Should be fixable with Microsoft's AppLocale Utility (just google for apploc).

I was refering to the 40fps thing as a vista bug. Running the emualtor on a vista machine that is more than capable of getting 60fps still only yields 40fps. Something weird is going on to cause it. Has been happening since v1.8

Power doesn't really matter, it runs worse on my more powerful PC than my wussy one. Like the original, it depends on the actual setup you have. The original team never released what they were making it on/for so we are kinda in the dark on this one.