Main > Software Forum

AVGA and Arkanoid: whats a good resolution to pick?

<< < (5/7) > >>

Howard_Casto:
Well if you have an arkanoid.ini that is setting the resolution, don't you think that is what is forcing the resolution?

duh!

Btw you typed 256x265 I don't know if that was a typo or not, but since 256xx265 is not a resolution listed by your card, that is why you are getting the odd-ball resolution.

Also about the directdraw surface.... pixel aspect is a non-issue, because unless Aaron typed the verbose output wierd, it says it created a 256x256 directdraw surface.  Surfaces can't be stretched and in fullscreen mode the surface size would have to equal the resolution, unless some crazy manual blitting is going on.  (Which is a possibility) 

Dead space generally occurs on any directx app when the resolution selected isn't supported but the code has error suppression.  What happens is a larger resolution is actually used and since the surface size can't be stretched, it simply fills as much of the screen as possible, leaving dead space below and to the right.  This is what you are describing yes?

So remove the ini and see what res it selects now. 

Banacek:

--- Quote from: Howard_Casto on November 03, 2006, 07:08:03 pm ---Well if you have an arkanoid.ini that is setting the resolution, don't you think that is what is forcing the resolution?

duh!

Btw you typed 256x265 I don't know if that was a typo or not, but since 256xx265 is not a resolution listed by your card, that is why you are getting the odd-ball resolution.

Also about the directdraw surface.... pixel aspect is a non-issue, because unless Aaron typed the verbose output wierd, it says it created a 256x256 directdraw surface.  Surfaces can't be stretched and in fullscreen mode the surface size would have to equal the resolution, unless some crazy manual blitting is going on.  (Which is a possibility) 

Dead space generally occurs on any directx app when the resolution selected isn't supported but the code has error suppression.  What happens is a larger resolution is actually used and since the surface size can't be stretched, it simply fills as much of the screen as possible, leaving dead space below and to the right.  This is what you are describing yes?

So remove the ini and see what res it selects now. 

--- End quote ---

That was a typo, my bad. After getting the chance to do extended testing, other games at that resolution (Donkey Kong, 1942, Arkanoid: Revenge of Doh) work perfectly. The only game so far to have this problem is Arkanoid and it's clones. Here's a comparison between "-verbose" outputs, with both games set to "resolution auto":


--- Quote ---E:\mame>mame arkanoid -verbose
Video: Monitor 00010001 = "\\.\DISPLAY1" (primary)
DirectDraw: Using DirectDraw 7
DirectDraw: Configuring device Ultimarc ArcadeVGA
DirectDraw: Selecting video mode...
(cut out different tests)
DirectDraw: Mode selected =  256x 256@ 60Hz
DirectDraw: primary surface created: 256x256x32 (R=00FF0000 G=0000FF00 B=000000F
F)
DirectDraw: New blit size = 383x306
DirectDraw: blit surface created: 383x306x32 (R=00FF0000 G=0000FF00 B=000000FF)
DirectInput: Using DirectInput 7
Input: Using RAWMOUSE for Mouse input
Input: Mouse 1 : HID-compliant mouse
Input: Mouse 2 : HID-compliant mouse
Input: Keyboards=1  Mice=2  Joysticks=0  Lightguns=2
Input: "mycontrols" controller support enabled
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
Average FPS: 60.000004 (728 frames)
--- End quote ---


--- Quote ---E:\mame>mame arknoid2 -verbose
Video: Monitor 00010001 = "\\.\DISPLAY1" (primary)
DirectDraw: Using DirectDraw 7
DirectDraw: Configuring device Ultimarc ArcadeVGA
DirectDraw: Selecting video mode...
(cut out different tests)
DirectDraw: Mode selected =  256x 256@ 60Hz
DirectDraw: primary surface created: 256x256x32 (R=00FF0000 G=0000FF00 B=000000F
F)
DirectDraw: New blit size = 224x256
DirectDraw: blit surface created: 224x256x32 (R=00FF0000 G=0000FF00 B=000000FF)
DirectInput: Using DirectInput 7
Input: Using RAWMOUSE for Mouse input
Input: Mouse 1 : HID-compliant mouse
Input: Mouse 2 : HID-compliant mouse
Input: Keyboards=1  Mice=2  Joysticks=0  Lightguns=2
Input: "mycontrols" controller support enabled
ark28742.bin NOT FOUND (NO GOOD DUMP KNOWN)
WARNING: the game might not run correctly.
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
Average FPS: 60.000011 (344 frames)
--- End quote ---


For arknoid2 (also for dkong and 1942), the blit size is equal to the what the resolution should be, in this case 224x256. It seems only arkanoid is giving me the trouble. This is so odd.

Silver:
Using your ini, I get stuff off-screen - but sideways, not vertically.

If I set maximize to 0, it is corrected.

Banacek:

--- Quote from: Silver on November 03, 2006, 09:51:31 pm ---Using your ini, I get stuff off-screen - but sideways, not vertically.

If I set maximize to 0, it is corrected.



--- End quote ---

GOT IT! (I think) I just dled a fresh version of Mame. Can you do me a favor and set up the artwork path in Mame and then set "use_bezels" to 1 and run arkanoid. Make sure the Bezel comes up. Then quit out and change "use_bezels" to 0, and bam!, you should have the problem I was having. If I never use the bezel, Arkanoid works fine. Interesting...

Silver:
once done, can you correct it by deleteing the arkanoid.cfg file in the cfg directory?

EDIT: ok, I get a cropped top section of the screen, and black space at the bottom.

Mame creates a different size windows IF you point it to a valid artwork directory no matter what any of the artwork options are. How strange.

EDIT2: This might be about what video mode mame starts up in. Hit Tab and go to video options, then switch between 3:4 aspect and pixel aspect (7:8)

Once you have run with bezels, mame starts up in the "with instructions card" video mode, which appears to crop some of the screen?

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version