Frogger and Mappy get goofy resolutions with latest versions (Page 1) — Support

1 Topic by emuola 2016-06-06 09:37:35 (edited by emuola 2016-06-06 09:39:21)

emuola
Member
Offline

Topic: Frogger and Mappy get goofy resolutions with latest versions

This was also posted in Arcadecontrols forum, but because the that server is still having issues (which effectively prevents real interaction there), I decided to post this also here. I hope this is ok.

So, running Win7 64bit and latest versions of GM and CRT Emudriver and Atom15. Attract mode as frontend. Everything installed just fine and most of the games look really good :) I have 23 modes and using super resolutions. I have resolution 2560x0 and cleanstretch 2 in mame.ini.

I'm having problems with Frogger and Mappy. They both get really weird "software scaled" looking resolutions. The image is almost a square and there are no scanlines -> game looks like it's displayed on a lcd. Other 15khz vertical games like 1943, Commando, Burning rubber, Contra, Bomb jack work just fine: image is not a square and they have proper scanlines. Even the info screen is totally different looking with Mappy and Frogger -> info screen is very crisp looking (the others have kinda distorted info screen) and has almost 16:9 ratio?! All horizontal games I've tried work perfectly :D

I know I can create a machinemame.ini files for the problematic games, but I would lkike to know what is causing this weird behaviour with only these two games.

Here are some (bad quality) pictures of the info screens and Frogger in-game:

https://onedrive.live.com/redir?resid=C … hoto%2cjpg
https://onedrive.live.com/redir?resid=C … hoto%2cjpg
https://onedrive.live.com/redir?resid=C … hoto%2cjpg

One more thing: What is the current way to adjust the aspect ratio for vertical games in ini file(s)? There seems to me some older instructions that do not apply to GM anymore?

Win7 64b
GM 170b ASIO
CRT EMu driver beta 8
ATI HD2400XT
M-Audio Delta 24/96 (pci) with official ASIO drivers
m3129

Thanks in advance!

2 Reply by Calamity 2016-06-07 18:36:49

Calamity
Administrator
Offline

Re: Frogger and Mappy get goofy resolutions with latest versions

Hi emuola,

Your issues with Frogger and Mappy are different (this would be very clear with a log by the way).

The issue with Frogger is that MAME renders it at a resolution of 768x224 in order to properly emulate the starfield in Galaxian, which is its parent driver. The problem is created when we users want to rotate the native resolution on a horizontal monitor.

GroovyMAME used to have a patch to force these games to be rendered at 256x224, but this patch has been removed in recent versions, as it prevented these games to display the backgrounds correctly when the intended, un-rotated native orientation was used.

On the othe hand, the issue with Mappy is due to the way the m3129 preset is defined. Because it can't achieve the correct refresh at 288p, it jumps to the next range, because 288 over a resolution of 320 doesn't leave so large borders, at least in theory (the fact that 320 is used as the lower limit, actually tells GM that the user is fine with the possible borders resulting from producing that resolution at the specified frequencies).

monitor "m3129", "Wei-Ya M3129", "4:3"
crt_range0 15250-16500, 40-80, 2.187, 4.688, 6.719, 0.190, 0.191, 1.018, 1, 1, 224, 288, 448, 576
crt_range1 23900-24420, 40-80, 2.910, 3.000, 4.440, 0.451, 0.164, 1.048, 1, 1, 320, 384, 0, 0
crt_range2 31000-32000, 40-80, 0.636, 3.813, 1.906, 0.318, 0.064, 1.048, 1, 1, 480, 512, 0, 0

A possible workaround is to just increase that value so ranges 0 and 1 are more separated:

monitor "m3129", "Wei-Ya M3129", "4:3"
crt_range0 15250-16500, 40-80, 2.187, 4.688, 6.719, 0.190, 0.191, 1.018, 1, 1, 224, 288, 448, 576
crt_range1 23900-24420, 40-80, 2.910, 3.000, 4.440, 0.451, 0.164, 1.048, 1, 1, 384, 400, 0, 0
crt_range2 31000-32000, 40-80, 0.636, 3.813, 1.906, 0.318, 0.064, 1.048, 1, 1, 480, 512, 0, 0

3 Reply by emuola 2016-06-08 08:16:38 (edited by emuola 2016-06-08 08:18:00)

emuola
Member
Offline

Re: Frogger and Mappy get goofy resolutions with latest versions

Calamity wrote:

Hi emuola,
Your issues with Frogger and Mappy are different (this would be very clear with a log by the way).
The issue with Frogger is that MAME renders it at a resolution of 768x224 in order to properly emulate the starfield in Galaxian, which is its parent driver. The problem is created when we users want to rotate the native resolution on a horizontal monitor.
GroovyMAME used to have a patch to force these games to be rendered at 256x224, but this patch has been removed in recent versions, as it prevented these games to display the backgrounds correctly when the intended, un-rotated native orientation was used.
On the othe hand, the issue with Mappy is due to the way the m3129 preset is defined. Because it can't achieve the correct refresh at 288p, it jumps to the next range, because 288 over a resolution of 320 doesn't leave so large borders, at least in theory (the fact that 320 is used as the lower limit, actually tells GM that the user is fine with the possible borders resulting from producing that resolution at the specified frequencies).

monitor "m3129", "Wei-Ya M3129", "4:3"
crt_range0 15250-16500, 40-80, 2.187, 4.688, 6.719, 0.190, 0.191, 1.018, 1, 1, 224, 288, 448, 576
crt_range1 23900-24420, 40-80, 2.910, 3.000, 4.440, 0.451, 0.164, 1.048, 1, 1, 320, 384, 0, 0
crt_range2 31000-32000, 40-80, 0.636, 3.813, 1.906, 0.318, 0.064, 1.048, 1, 1, 480, 512, 0, 0

A possible workaround is to just increase that value so ranges 0 and 1 are more separated:
monitor "m3129", "Wei-Ya M3129", "4:3"
crt_range0 15250-16500, 40-80, 2.187, 4.688, 6.719, 0.190, 0.191, 1.018, 1, 1, 224, 288, 448, 576
crt_range1 23900-24420, 40-80, 2.910, 3.000, 4.440, 0.451, 0.164, 1.048, 1, 1, 384, 400, 0, 0
crt_range2 31000-32000, 40-80, 0.636, 3.813, 1.906, 0.318, 0.064, 1.048, 1, 1, 480, 512, 0, 0

Hi Calamity and thanks again for your great work and support! :)

Sorry, I forgot the logs. Actually After I did the changes you suggested, Mappy (and Ikari Warriors, which I forgot to list earlier) now work just fine :D Thank you Calamity! I'd never figured this out without your help!

Frogger, however, refuses to cooperate looking exactly the same as before :/ Here's the log (created from cmd with admin proiviledges by typing "mame frogger -v > frogger.txt"):

SwitchRes: v0.015m, Monitor: custom, Orientation: horizontal, Modeline generation: enabled
SwitchRes: Monitor range 15250.00-16500.00,40.00-80.00,7.187,4.688,6.719,0.190,0.191,1.018,1,1,224,288,448,576
SwitchRes: Monitor range 23900.00-24420.00,40.00-80.00,2.910,3.000,4.440,0.451,0.164,1.048,1,1,380,400,0,0
SwitchRes: Monitor range 31000.00-32000.00,40.00-80.00,0.636,3.813,1.906,0.318,0.064,1.048,1,1,480,512,0,0
SwitchRes: \\.\DISPLAY1: ATI Radeon HD 2400 XT (CRT Emudriver - WDDM v1.1) (PCI\VEN_1002&DEV_94C1&SUBSYS_0D021028&REV_00)
SwitchRes: Device key: System\CurrentControlSet\Control\Video\{5A7C7B2F-A7FD-4805-8C98-A97F7816B770}\0000
ATI legacy init
Switchres: Searching for custom video modes...
Switchres: [  1]  640x 480 @ 60* : ATI legacy timing "640x480_60 31.500000KHz 60.000000Hz" 25.200000 640 656 752 800 480 490 492 525   +hsync +vsync
Switchres: [  2] 2560x 240 @ 60 : ATI legacy timing "2560x240_60 15.719000KHz 59.996183Hz" 56.840000 2560 2968 3232 3616 240 243 246 262   +hsync +vsync
Switchres: [  3] 2560x 248 @ 60 : ATI legacy timing "2560x248_60 16.260000KHz 60.000000Hz" 59.710000 2560 2992 3272 3672 248 252 255 271   +hsync +vsync
Switchres: [  4] 2560x 256 @ 59 : ATI legacy timing "2560x256_59 16.498000KHz 59.132616Hz" 60.980000 2560 3000 3288 3696 256 259 262 279   +hsync +vsync
Switchres: [  5] 2560x 264 @ 57 : ATI legacy timing "2560x264_57 16.498000KHz 57.484321Hz" 60.980000 2560 3000 3288 3696 264 267 270 287   +hsync +vsync
Switchres: [  6] 2560x 272 @ 56 : ATI legacy timing "2560x272_56 16.498000KHz 55.925424Hz" 60.980000 2560 3000 3288 3696 272 275 278 295   +hsync +vsync
Switchres: [  7] 2560x 280 @ 54 : ATI legacy timing "2560x280_54 16.498000KHz 54.448845Hz" 60.980000 2560 3000 3288 3696 280 283 286 303   +hsync +vsync
Switchres: [  8] 2560x 288 @ 53 : ATI legacy timing "2560x288_53 16.498000KHz 53.048232Hz" 60.980000 2560 3000 3288 3696 288 291 294 311   +hsync +vsync
Switchres: [  9] 2560x 320 @ 60 : ATI legacy timing "2560x320_60 23.940000KHz 60.000000Hz" 81.590000 2560 2800 3048 3408 320 351 355 399   +hsync +vsync
Switchres: [ 10] 2560x 336 @ 60 : ATI legacy timing "2560x336_60 23.940000KHz 60.000000Hz" 81.590000 2560 2800 3048 3408 336 359 363 399   +hsync +vsync
Switchres: [ 11] 2560x 344 @ 60 : ATI legacy timing "2560x344_60 23.940000KHz 60.000000Hz" 81.590000 2560 2800 3048 3408 344 363 367 399   +hsync +vsync
Switchres: [ 12] 2560x 352 @ 60 : ATI legacy timing "2560x352_60 23.940000KHz 60.000000Hz" 81.590000 2560 2800 3048 3408 352 367 371 399   +hsync +vsync
Switchres: [ 13] 2560x 360 @ 60 : ATI legacy timing "2560x360_60 23.999000KHz 59.997500Hz" 81.790000 2560 2800 3048 3408 360 371 375 400   +hsync +vsync
Switchres: [ 14] 2560x 368 @ 60 : ATI legacy timing "2560x368_60 24.420000KHz 59.706601Hz" 83.420000 2560 2800 3048 3416 368 380 384 409   +hsync +vsync
Switchres: [ 15] 2560x 376 @ 59 : ATI legacy timing "2560x376_59 24.420000KHz 58.561151Hz" 83.420000 2560 2800 3048 3416 376 388 392 417   +hsync +vsync
Switchres: [ 16] 2560x 384 @ 57 : ATI legacy timing "2560x384_57 24.420000KHz 57.458824Hz" 83.420000 2560 2800 3048 3416 384 396 400 425   +hsync +vsync
Switchres: [ 17] 2560x 448 @ 60 : ATI legacy timing "2560x448_60 15.329000KHz 59.996086Hz" 54.820000 2560 2952 3208 3576 448 464 470 511 interlace  +hsync +vsync
Switchres: [ 18] 2560x 464 @ 60 : ATI legacy timing "2560x464_60 15.329000KHz 59.996086Hz" 54.820000 2560 2952 3208 3576 464 472 478 511 interlace  +hsync +vsync
Switchres: [ 19] 2560x 480 @ 60 : ATI legacy timing "2560x480_60 31.500000KHz 60.000000Hz" 100.800000 2560 2624 3008 3200 480 490 492 525   +hsync +vsync
Switchres: [ 20] 2560x 496 @ 59 : ATI legacy timing "2560x496_59 32.001000KHz 59.042435Hz" 102.660000 2560 2624 3016 3208 496 507 509 542   +hsync +vsync
Switchres: [ 21] 2560x 512 @ 59 : ATI legacy timing "2560x512_59 16.528000KHz 59.134168Hz" 61.090000 2560 3000 3288 3696 512 518 524 559 interlace  +hsync +vsync
Switchres: [ 22] 2560x 544 @ 56 : ATI legacy timing "2560x544_56 16.528000KHz 55.932318Hz" 61.090000 2560 3000 3288 3696 544 550 556 591 interlace  +hsync +vsync
Switchres: [ 23] 2560x 560 @ 54 : ATI legacy timing "2560x560_54 16.525000KHz 54.448105Hz" 61.080000 2560 3000 3288 3696 560 566 572 607 interlace  +hsync +vsync
SwitchRes: Found 23 custom of 23 active video modes
SwitchRes: -resolution was forced as 2560x0

SwitchRes: Entering switchres_modeline_setup
SwitchRes: v0.015m:[frogger] Calculating best video mode for 224x768@60.606060 orientation: rotated

SwitchRes: [ 640]x[ 480]_[60=60.000000Hz] - locked

SwitchRes: [2560]x[ 240]_(60=59.996183Hz)
   rng(0): 2560 x 240_60.606060p 15.878788 [fract] scale(6, 1, 1) diff(6.67, 0.00, 0.0000) ratio(11.429, 0.313)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 248]_(60=60.000000Hz)
   rng(0): 2560 x 248_60.606060p 16.424242 [fract] scale(6, 1, 1) diff(6.67, 0.00, 0.0000) ratio(11.429, 0.323)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 256]_(59=59.132616Hz)
   rng(0): 2560 x 256_59.139786p 16.500000 [fract] scale(6, 1, 1) diff(6.67, 0.00, -1.4663) ratio(11.429, 0.333)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 264]_(57=57.484321Hz)
   rng(0): 2560 x 264_57.491291p 16.500001 [fract] scale(6, 1, 1) diff(6.67, 0.00, -3.1148) ratio(11.429, 0.344)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 272]_(56=55.925424Hz)
   rng(0): 2560 x 272_55.932205p 16.500001 [fract] scale(6, 1, 1) diff(6.67, 0.00, -4.6739) ratio(11.429, 0.354)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 280]_(54=54.448845Hz)
   rng(0): 2560 x 280_54.455444p 16.500000 [fract] scale(6, 1, 1) diff(6.67, 0.00, -6.1506) ratio(11.429, 0.365)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 288]_(53=53.048232Hz)
   rng(0): 2560 x 288_53.054661p 16.500000 [fract] scale(6, 1, 1) diff(6.67, 0.00, -7.5514) ratio(11.429, 0.375)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 320]_(60=60.000000Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 336]_(60=60.000000Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 344]_(60=60.000000Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 352]_(60=60.000000Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 360]_(60=59.997500Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 368]_(60=59.706601Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 376]_(59=58.561151Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 384]_(57=57.458824Hz)
   rng(0):  out of range
   rng(1): 2560 x 384_57.458824p 24.420000 [fract] scale(6, 1, 1) diff(6.67, 0.00, -3.1472) ratio(11.429, 0.500)
   rng(2):  out of range

SwitchRes: [2560]x[ 448]_(60=59.996086Hz)
   rng(0): 2560 x 448_60.606060i 15.303030 [fract] scale(6, 1, 1) diff(6.67, 0.00, 0.0000) ratio(11.429, 0.583)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 464]_(60=59.996086Hz)
   rng(0): 2560 x 464_60.606060i 15.363636 [fract] scale(6, 1, 1) diff(6.67, 0.00, 0.0000) ratio(11.429, 0.604)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 480]_(60=60.000000Hz)
   rng(0): 2560 x 480_60.606060i 15.909091 [fract] scale(6, 1, 1) diff(6.67, 0.00, 0.0000) ratio(11.429, 0.625)
   rng(1):  out of range
   rng(2): 2560 x 480_60.606060p 31.878788 [fract] scale(6, 1, 1) diff(6.67, 0.00, 0.0000) ratio(11.429, 0.625)

SwitchRes: [2560]x[ 496]_(59=59.042435Hz)
   rng(0): 2560 x 496_60.606060i 16.454545 [fract] scale(6, 1, 1) diff(6.67, 0.00, 0.0000) ratio(11.429, 0.646)
   rng(1):  out of range
   rng(2): 2560 x 496_59.040592p 32.000001 [fract] scale(6, 1, 1) diff(6.67, 0.00, -1.5655) ratio(11.429, 0.646)

SwitchRes: [2560]x[ 512]_(59=59.134168Hz)
   rng(0): 2560 x 512_59.139786i 16.529570 [fract] scale(6, 1, 1) diff(6.67, 0.00, -1.4663) ratio(11.429, 0.667)
   rng(1):  out of range
   rng(2): 2560 x 512_57.347672p 32.000001 [fract] scale(6, 1, 1) diff(6.67, 0.00, -3.2584) ratio(11.429, 0.667)

SwitchRes: [2560]x[ 544]_(56=55.932318Hz)
   rng(0): 2560 x 544_55.932205i 16.527967 [fract] scale(6, 1, 1) diff(6.67, 0.00, -4.6739) ratio(11.429, 0.708)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 560]_(54=54.448105Hz)
   rng(0): 2560 x 560_54.455444i 16.527227 [fract] scale(6, 1, 1) diff(6.67, 0.00, -6.1506) ratio(11.429, 0.729)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [frogger] (1) vertical (224x768@60.606060)->(2560x480@60.606060)
   rng(2): 2560 x 480_60.606060p 31.878788 [fract] scale(6, 1, 1) diff(6.67, 0.00, 0.0000) ratio(11.429, 0.625)
SwitchRes: Modeline "2560x480_60 31.878788KHz 60.606060Hz" 102.267152 2560 2624 3016 3208 480 491 493 526   +hsync +vsync
Switchres: saving    ATI legacy timing "2560x480_60 31.500000KHz 60.000000Hz" 100.800000 2560 2624 3008 3200 480 490 492 525   +hsync +vsync
Switchres: updating  ATI legacy timing "2560x480_60 31.878788KHz 60.606060Hz" 102.267152 2560 2624 3016 3208 480 491 493 526   +hsync +vsync
SwitchRes: Setting option -rotate
SwitchRes: Setting option -noror
SwitchRes: Setting option -noautoror
SwitchRes: Setting option -norol
SwitchRes: Setting option -noautorol
SwitchRes: Setting option -noblack_frame_insertion
SwitchRes: Setting option -multithreading
SwitchRes: Setting option -notriplebuffer
SwitchRes: Setting option -syncrefresh
SwitchRes: Setting option -waitvsync
SwitchRes: Setting option -keepaspect
SwitchRes: Setting option -filter
SwitchRes: Setting option -prescale 1
Video: Monitor 0000000008656248 = "\\.\DISPLAY1" (primary)
Direct3D: Warning - Unable find any D3D9 DLLs; disabling post-effect rendering
Direct3D: Using Direct3D 9Ex
window_proc: WM_NCACTIVATE
blit_lock = TRUE
Physical width 640, height 480
Direct3D: Configuring adapter #0 = ATI Radeon HD 2400 XT (CRT Emudriver - WDDM v1.1)
Direct3D: Adapter has Vendor ID: 1002 and Device ID: 94C1
Direct3D: Using dynamic textures
Direct3D: YUV format = RGB
Direct3D: Max texture size = 8192x8192
Direct3D: Device created at 2560x480
Direct3D: First scanline: 35, Last scanline: 515, Break scanline: 515, Delay scanline: -17
blit_unlock = TRUE
window_proc: WM_PAINT
Blitting thread created
winwindow_video_window_create: blit_lock = TRUE
RawInput: APIs detected
Input: Adding Mouse #0: HID-compliant mouse
Input: Adding Gun #0: HID-compliant mouse
Input: Adding Mouse #1: HID-compliant mouse
Input: Adding Gun #1: HID-compliant mouse
Input: Adding Kbd #0: HID Keyboard Device
Input: Adding Kbd #1: HID Keyboard Device
Input: Adding Kbd #2: HID Keyboard Device
Input: Adding Kbd #3: HID Keyboard Device
Blitting thread started
blit_lock = FALSE
window_proc: WM_PAINT:END
DirectInput: Using DirectInput 8
ASIO: Game is running at 60.606060 Hz, screen at about 60.606060 Hz
ASIO: Driver M-Audio ASIO initialized with latency 128,
      sample rate 48000.00
      audio latency is 0
      frame delay is 0
ASIO: Setting initial playback rate to 48000.000 Hz
Region ':maincpu' created
Region ':audiocpu' created
Region ':gfx1' created
Region ':proms' created
Starting Frogger ':'
Optional shared pointer 'decrypted_opcodes' not found
Optional device 'ppi8255_2' not found
Optional device 'digitalker' not found
Optional device 'cclimber_audio:aysnd' not found
Optional device '8910.2' not found
Optional device '8910.1' not found
Optional device 'dac' not found
Optional device 'audio2' not found
  (missing dependencies; rescheduling)
Starting Z80 ':maincpu'
Starting gfxdecode ':gfxdecode'
Starting palette ':palette'
Starting Video Screen ':screen'
Optional device 'finder_dummy_tag' not found
Starting Timer ':stars'
Starting Speaker ':mono'
  (missing dependencies; rescheduling)
Starting 8255 PPI ':ppi8255_0'
Starting 8255 PPI ':ppi8255_1'
Starting Z80 ':audiocpu'
Starting AY-3-8910A ':8910.0'
Starting DISCRETE ':konami'
Starting Frogger ':'
Optional shared pointer 'decrypted_opcodes' not found
Optional device 'ppi8255_2' not found
Optional device 'digitalker' not found
Optional device 'cclimber_audio:aysnd' not found
Optional device '8910.2' not found
Optional device '8910.1' not found
Optional device 'dac' not found
Optional device 'audio2' not found
  (missing dependencies; rescheduling)
Starting Speaker ':mono'
Starting Frogger ':'
Optional shared pointer 'decrypted_opcodes' not found
Optional device 'ppi8255_2' not found
Optional device 'digitalker' not found
Optional device 'cclimber_audio:aysnd' not found
Optional device '8910.2' not found
Optional device '8910.1' not found
Optional device 'dac' not found
Optional device 'audio2' not found
Switchres: restoring ATI legacy timing "2560x480_60 31.500000KHz 60.000000Hz" 100.800000 2560 2624 3008 3200 480 490 492 525   +hsync +vsync
ASIO: Average callback timeslice usage: 0.385251
ASIO: Overrun/underrun: 0/0
window_proc: WM_NCACTIVATE
blit_lock = TRUE
window_proc: WM_DESTROY
blit_lock = TRUE
Blitting thread destroyed

Everything is about perfect except the Frogger now :D

4 Reply by emuola 2016-06-12 11:24:04

emuola
Member
Offline

Re: Frogger and Mappy get goofy resolutions with latest versions

I'll post this as a reply to the original post:

1. When the patch is not there anymore to correct the "Galaxian resolution problem", how can I force Frogger to be displayed 256 x 224? I guess I should create a frogger.ini, but what should I put there?

2. Is there a way to make vertical games a bit wider (not full screen), but just a tad "fatter"? :)

Thanks!

5 Reply by Calamity 2016-06-12 20:40:13

Calamity
Administrator
Offline

Re: Frogger and Mappy get goofy resolutions with latest versions

emuola wrote:

1. When the patch is not there anymore to correct the "Galaxian resolution problem", how can I force Frogger to be displayed 256 x 224? I guess I should create a frogger.ini, but what should I put there?

You can use an .ini file, but forcing a lower resolution like that will trigger fractional scaling and the result will be bad. So it's either that or put up with the resolution as suggested by GM.

Basically the only proper solution is to play the game at its native monitor orientation.

2. Is there a way to make vertical games a bit wider (not full screen), but just a tad "fatter"? :)

You can lie GM about your monitor aspect, by means of the -aspect option. By default -aspect 4:3 is selected, and GM calculates pillarbox borders to achieve 3:4 inside 4:3 for vertical games.

If you specify -aspect 3:4, GM will believe your monitor is already vertically oriented so vertical games will be rendered at full screen.

So what you need to use is an -aspect ratio that's somewhere between 4:3 and 3:4.

6 Reply by emuola 2016-06-14 07:12:46

emuola
Member
Offline

Re: Frogger and Mappy get goofy resolutions with latest versions

Calamity wrote:

emuola wrote:
1. When the patch is not there anymore to correct the "Galaxian resolution problem", how can I force Frogger to be displayed 256 x 224? I guess I should create a frogger.ini, but what should I put there?
You can use an .ini file, but forcing a lower resolution like that will trigger fractional scaling and the result will be bad. So it's either that or put up with the resolution as suggested by GM.
Basically the only proper solution is to play the game at its native monitor orientation.
2. Is there a way to make vertical games a bit wider (not full screen), but just a tad "fatter"? :)
You can lie GM about your monitor aspect, by means of the -aspect option. By default -aspect 4:3 is selected, and GM calculates pillarbox borders to achieve 3:4 inside 4:3 for vertical games.
If you specify -aspect 3:4, GM will believe your monitor is already vertically oriented so vertical games will be rendered at full screen.
So what you need to use is an -aspect ratio that's somewhere between 4:3 and 3:4.

Thanks Calamity :) I tested a few aspect ratios and 6:5 seems to work just fine :) I guess I have to forget the Frogger, you can't get everything in life :D

Frogger and Mappy get goofy resolutions with latest versions

Posts: 6

1 Topic by emuola 2016-06-06 09:37:35 (edited by emuola 2016-06-06 09:39:21)

Topic: Frogger and Mappy get goofy resolutions with latest versions

2 Reply by Calamity 2016-06-07 18:36:49

Re: Frogger and Mappy get goofy resolutions with latest versions

3 Reply by emuola 2016-06-08 08:16:38 (edited by emuola 2016-06-08 08:18:00)

Re: Frogger and Mappy get goofy resolutions with latest versions

4 Reply by emuola 2016-06-12 11:24:04

Re: Frogger and Mappy get goofy resolutions with latest versions

5 Reply by Calamity 2016-06-12 20:40:13

Re: Frogger and Mappy get goofy resolutions with latest versions

6 Reply by emuola 2016-06-14 07:12:46

Re: Frogger and Mappy get goofy resolutions with latest versions

Posts: 6