Horz. + Vert. size +-0.50 | gfx option

[Toni Wilen]

Originally Posted by cfTrio

Now, the size of the picture can be adjust right on the fly directly in the game and the spaces between the scanlines are always regularly.

PERFECT THANKS

Great

What do you think about the implementation of the 0.50 steps Fullscreen-Filter?

What do you mean? Screen mode should not make any difference.

(Btw. the FS option in the drop down menus doesn't work anymore since the change from int to float)

Fixed

[cfTrio]

no more time today -will give you an answer tomorrow - Happy Hogmanay

[cfTrio]

Hello Toni, wish you a happy new year.

Originally Posted by Toni Wilen

What do you mean? Screen mode should not make any difference.

I thought of a flexible portable solution. But maybe Winuae requires some more options to be able to do this?

I will try to explain my thoughts with my sometimes google-translated german-english:

Instead of the Standard-Setup in the display panel

Fullscreen: 800x600 | 16 | Default refresh rate

i need a solution like this

Fullscreen: [native resolution] or [current desktop resolution] | if possible use 32Bit else 16Bit | if possible use 50Hz else 60Hz

With these options i don't need to change the Fullscreen resolution in my portable Winuae anymore, when i use my uae-configs on other PCs with other native/current desktop resolutions.

Then, the '0.50 steps Fullscreen-Filter', that only uses the 0.50 steps/multiplications, could automatically switch to the matching vert + horiz values in relation to the native/current desktop resolution e.g:

resolution = vert. multi x horiz. multi
720x576 = 1.00 x 1.00
800x600 = 1.00 x 1.00
1024x768 = 1.50 x 1.50
1366x768 = 1.50 x 1.50
1680x1050 = 2.00 x 2.00
1920x1080 = 2.00 x 2.00

EDIT: Changed the example with the Fullscreen in the hope that it makes more sense now.

[cfTrio]

Originally Posted by Toni Wilen

What do you mean? Screen mode should not make any difference.

i think i should point out that i always use the native resolution to prevent the 'waves effect' with enabled scanlines on LCD Monitors. The picture in the Attachment shows the effect.

So, when i use my configurations on an other PC that uses an other monitor with an other native resolution, i must change manually the fullscreen resolution in the display panel in Winuae first and then every time again once i load an other config.

Instead of saving a fixed resolution in the config

gfx_width_fullscreen=1680
gfx_height_fullscreen=1050

it would be really helpful having a feature like this

gfx_width_fullscreen=native
gfx_height_fullscreen=native

[Toni Wilen]

"native" selection can be done but can't you use "full-window" mode? It is practically same as fullscreen in native resolution (but without being in real fullscreen mode).

[cfTrio]

My native resolution is 1680x1050 60Hz. The full-window mode doesn't use the 50Hz by default - that's the problem.

EDIT: i made a custom resolution 1680x1050 50Hz in the driver software (just for Winuae) but i don't use this setup as standard for my desktop

EDIT: That's why i asked in my post from yesterday after this feature: "if possible use 50Hz else 60Hz"

[Toni Wilen]

"Native" selection will be done, refresh rate selection probably isn't needed because it will switch to default (60Hz) if 50Hz isn't found.

[cfTrio]

Ok, that's good, thanks!

[Toni Wilen]

Done. http://www.winuae.net/files/b/winuae.zip (This version may have other issues but native resolution stuff should work)

[cfTrio]

Native resolution works (tested with three Monitors; all have different native resolutions: 1920x1080, 1680x1050, 1280x1024)

Some "Native" Setup Bugs

-Config: 32Bit can not be saves
-GUI: Changing the Hz, 32Bit switches to 16Bit automatically
-GUI: Returning to the display panel, resolution drop down menu is empty + 32Bit switches to 16Bit

[Toni Wilen]

Should be fixed now.

[cfTrio]

Hi Toni,

on my first machine Win7 Pro 64Bit SP1 (Monitor1: 1680x1050, Monitor 2: 1680x1050) it works without any problem

on my second machine WinXP Pro 32Bit SP3 (Monitor1: 1920x1080, Monitor2: 1280x1024) Winuae crashs directly at the beginning (with or without winuae.ini, configuration.cache, registry entities, config.uae + with both or only one monitor).

Unlike Public Beta 0, 2013.01.07, this problem doesn't occur with Public Beta 0, 2013.01.06.

Winuae -log
(as i can not upload an ini file i have renamed the winuae.ini to winuae.ini.txt)

[Toni Wilen]

Does it work if you use -maxmem 256 command line parameter? (if yes, does it still work if you change it to -maxmem 512?)

[cfTrio]

Same result with

Winuae -maxmem 256 -log
and
Winuae -maxmem 512 -log

It's an Athlon 1800+ with 1GB Ram

[cfTrio]

It has something to do with my second machine. On my first machine i have installed the same XP on a second partition. Here i can start Winuae without problems.

[Toni Wilen]

Run with "-maxmem 256 -log -logflush" (without -logflush last few log lines will be lost if it crashes)

I still think it is memory related because this kind of early crash on 32-bit XP with 1G or less memory has happened previously

[cfTrio]

hmm, with the command "winuae -maxmem 256 -log -logflush" i got the same result (without extra line).

How can i find out if it is a RAM problem?

With Winuae Public Beta 0, 2013.01.06 and Winuae 2.5.1 i have not these problems.

EDIT: Attachment

[cfTrio]

I have tested the Public Beta 0, 2013.01.07 with the same XP on 3 other machines

winuae -maxmem 256 -log -logflush

Athlon 2600+ 1.5GB RAM = identically problem
Intel Pentium 4 3GHz, 2GB RAM = works
Intel Core 2 6600 2.40GHz 3GB RAM = works

[Toni Wilen]

Does it still happen with today's version?

[cfTrio]

No. Both versions 08 and 09 runs as usual = problem located and solved?