> The resolutions the snaps are taken at are the resolutions the game is running at, so
> no wonder why you like the older version better -- it is running at the higher
> resolution.
>
> The question is, what parameters are you passing that is causing 0.104 to run at the
> lower resolution. Run with -verbose for a clue.
E:\games\mame32-69>mame tempest -verbose
Parsing mame.ini : N/A
Parsing vector.ini : OK
Parsing tempest.ini : OK
Using DirectInput 7
Keyboards=1 Mice=0 Joysticks=0 Lightguns=0
Enumerating video device display
Hardware stretching supported
Best mode = 1024x768x16 @ default Hz
Primary surface created: 1024x768x16 (R=0000f800 G=000007e0 B=0000001f)
Blit surface created: 378x482x16 (R=0000f800 G=000007e0 B=0000001f)
Primary buffer: 44100 Hz, 16 bits, 2 channels
SSE2 supported
Average FPS: 59.996943 (89 frames)
I normally use MAME32 here. Curiously, baseline .104 says the roms are missing files. But the MAME32 .69 roms work with baseline .104 .
In any case, okay, I know what's going on. I have hwstretch on (desktop is at 1024x768). It seems MAME handled hwstretch differently some time after .69 - or maybe it's just that .69 is running at a higher 'inherent' resolution, so the scaling isn't obvious. With .104, if I turn off hwstretch, turn on switchres, and set the res for 1024x768, the image is crisp and distinct.
Ideally, it still needs a boost from either vector intensity at 3, or fsb at 2 (they seem to have slightly different effects).
Alternatively, I went an set the res for 640x480, and that's definitely the best-looking - but that's probably because I'm using a CRT. I'm getting that phosphor glow of the lower scan rate.
By the way, I may have some news on AAE, soon.
Consider it high comedy....sincere tragedy....whatever...don't take it personally.
The Culture
|
Previous 
Index 
Next 
Flat 
Re: AAE - incorporating it into MAME
Reply
