I can put anything in Display panel boxes and it does resize (as designed) as long as "Allow scaling" is ticked.

I can't duplicate. Do you use filters? (filters not mentioned == I expect they are not enabled :))

silly me i was looking fot the option in the display panel. my bad. it works

indeed they are not enabled. i've tested it more without being able to reproduce it :(
i used the sonic demo and had the same results 3 or 4 times, but nothing this morning.

Found stupid bug that probably explains this. (comparing p96 width to window height when it should have been height to height..)

Hi,
I have just tested Beta2. I like the scaling very much.
I have Workbench running in 800x600 32 Bit BRGA.
When the WINUA-Window has the same size everything is fine. When I make it smaller than 800x600 however the mousepointer is no longer visible in the whole amiga screen area. It becomes invisible on the right and bottom part of the screen. The percentage of this invisible mousepointer area depends on the size of the Winuae window.

Regards selco

i have noticed one other thing, and i don't know if it's the same stuff already discussed;

the window doesn't properly resize, or better, it uses resize even when it is not needed and stays stuck there in this case:

in Winuae GUI
- full screen set to different resolution than RTG (and so ignored), for instance 720*576
- RTG screen set to 800*600
- either checked "alway scale" or not
- Fullscreen set for non rtg modes

-inside the emulation, rtg is set to 800*600

the screen mode is set to windowed.

firing up that i end up with resizing applied to the window no matter if the 2 resolutions RTG and window are the same. it is probably caused by the fact that winuae starts fullscreen anyway and skips to fullscreen any time i change the RTG resolution inside the emulation.
if i set the apparently unused fullscreen resolution to the same value as the other two, 800*600, resizing disappears.

http://www.winuae.net/files/b/winuae_1510b3.zip

Beta 3:

- corrected directinput keyboard enumeration, possible fix for wrong keycodes (=non-working key) on some keyboard/driver combinations. (bug since the beginning, I blame really bad keyboard directinput documentation)
- Picasso96 color space conversion color errors (b2)
- Picasso96 now always keeps aspect ratio in scaled modes (both windowed and full-window)
- window resize worked strangely in some cases
- full-window on the fly monitor change fixed
- disappearing mouse cursor if scaled window was smaller than original Picasso96 resolution
- detect Amiga Forever 2008 Value Edition rom key when winuae is located outside of AF install directory
- fullscreen to fullscreen non resolution/depth changes won't reopen the display anymore (except D3D/OGL<>other filter change)
- fullscreen to fullscreen resolution/depth change speed improved
- Windowed Picasso96 scaling fixed when native mode was set to fullscreen or fullwindow
- nasty memory corruption fixed in configuration handling introduced in 1.5 betas. Causes random crash or memory corruption sooner or later when saving configuration few times.

i have not spot any problem.

a reques though:
can you remove it? or at least made it so you can force resizing? it's nice on non 3/4 monitors.

the best would be have both: the list of correct ratios (but you can borrow that from the primary video driver' list) and free resize input

thanks in advance! :)

More information please. It should automatically select correct aspect ratio

For example full window RTG 1024x768 on 16:10 has black borders but same 1024x768 on 4:3 monitor has no borders. (I have two monitors, primary is 16:10 1920x1200 and secondary is 4:3 1600x1200)

why oh why i let myself be dragged in betatesting each saturday afternoon? :lol

so... i have a 16:10 1680*1050 monitor.

Fullscreen:

RTG mode is ok, as Picasso resolution fits perfectly in the center of screen and the ratios are correct.
Native modes need a bit of thinkering with filters to be resized to the monitor borders or the use of "correct aspect ratio" button, as the 640*480 (which is the littlest resolution available on my pc) leaves the top and the bottom of the amiga screen out of the monitor.

so no problem here.

Windowed modes:

to beta 2, RTG modes are resized to whatever number you input in the display panel. wich is cool because you may want to have a big window on almost the size of the monitor and in a roughly 16:10 ratio.
if you want an amiga-like window, without, or with less, artifact, then you just borrow one of the screensizes from the native display and you apply it in windowed mode.

with beta 3 you are limited to those instead, because of the RTG screen non resizing.

in native modes that's even worse, as the amiga resolution is lower and the maximum size of the winuae window to have centered screen and the screen fit to the window is only 600*512: more than that you need to use filters again.

"non resizing"? I still don't understand. RTG will resize as long as it is enabled. (what do you mean by resize? window resizing or "p96 monitor" resizing?)

Native modes work as previously, p96 scaling won't change that.

resinzing as in to fully fit the window.

beta 3 resizes windowed RTG only to 4:3 and however, not to custom sizes, wich makes pointless the whole resizing thing, as if you'd need to simply screen-mode you could already do it with the picasso preferences inside workbench

Ah, ok. I guess I need to fit rtg aspect ratio checkbox somewhere.

Or perhaps even select box with some standard values + none + automatic..

that would be perfect! :)

sorry if i was not much understandable, again i have a poor tech vocabulary

Something like this: http://www.winuae.net/files/b/winuae.zip
Good enough? :)

it's good! :)

i had in mind something like :

disbled
automatic
custom

and with custom you could enter the sizes for height and width directly too, so you wouldn't have to approximate the windows sizes.

with a 2 fields line like the one in the display panel next to it.

however, if it's not woth the hassle, believe me, it's good enough :)

thank you!

sorry to stumble again in the discussion, but i've noticed that with the RTG set to stretch the window, if you switch to a native mode, the screen stays black if the null filter is on. (you switch it off, it the screen appears back)

both in fullscreen and in windowed modes.

DirectX works.

I guess that's some incompatibility of the two resizing managers, but as one affects only RTG and the other only native modes, and the latter is needed with a winuae window so big, it's a bit of a bug.

One more thing: switching to and from windowed and fullscreen, this time Winuae disabled aero modes of Vista (which usually MAY happen when you run 32bit video software on 64bit OS) which it has never happened with Winuae before, leaving some shit on screen until i closed Winuae .

do you need winuaelog?

I didn't bother, nobody needs them anyway and you can edit configuration file manually if needed :)

Can't duplicate. (perhaps needs specific resolution settings = more information please :))

Aero always gets disabled in fullscreen modes.

what there is already is more than enough! if you'll ever get back to rearrange buttons in the GUI, will maybe be worthy to think about it (putting all together RTG stuff, bar the ram, in the display panel).
but that's an opinion, not a bug report, and as it is now, it works :)

ok i attach the configuration. the HD boots in a UAE 800*600 32 BIT picasso wb.
with that setting, if you just switch to a normal mode, either by prefs, or launching a native mode program, like whdload, the screen stays black.

as a sidenote, the particular settings of the null filter that there are, are ininfluent, i have tested many other: these were the last ones i saved. it happens the same thing anyway.

ok, but it seemed to me that in this case winuae was sucking away all the resources like when it hangs, and it switched off aero already when i turn back to windowed mode, and that i've never seen.

if you happen to reproduce what described above about the filter, try some fullscreen switching and back, to check it: as i said, as it doesn't hanged, in the end, it may just be nothing of important.

i have got to say, that the last betas, no matter the minor problems and the bugfixing, are really great Toni! it seems to me Winuae is every day more solid as a software, without sacrificing versatility.

Can't duplicate, even with your configuration (after fixing rom path and harddrive path)

Logs needed.

Aero gets disabled if program tries to read or write visible display ram directly (instead of blitting)

RTG or native or both? Logs again :)

Thanks. It gets better faster if there is feedback. Thanks again :)