WinUAE 3.6.1 beta series

[Toni Wilen]

Originally Posted by DamienD

What the configuration file isn't enough?
.

No because I need to know where exactly it happens and how. (title screen? in-game? some bonus screen that takes 30mins of game play and so on..)

[DamienD]

Originally Posted by Toni Wilen

No because I need to know where exactly it happens and how. (title screen? in-game? some bonus screen that takes 30mins of game play and so on..)

Title screen and in-game Toni and is very obvious as soon as you start level 1.

Here's how things look for me; perfect!!!



...but I don't ever use that evil "automatic scaling" option which distorts text / graphics etc.

[Toni Wilen]

Perhaps but don't force your personal options to other users. It is always user's personal choice, even if it is stupid and evil.

But there is not automatic scaling even enabled in that config so this is totally offtopic here..

Anyway, it seems to work as designed ("default" scaling option). Image start is very early and it probably gets clipped on real TVs too.

[DamienD]

Originally Posted by Toni Wilen

But there is not automatic scaling even enabled in that config so this is totally offtopic here..

Default scaling is set; not the same as automatic scaling?

BTW, I'm not forcing anything... ok, so I don't like an option but with good reason and I've explained why. People are free to make their own choices, why should anyone listen to me?

To be honest, I couldn't care less if this gets fixed or not... was just trying to help out ransom1122...

Just thought that you would like to know Toni as it seems to be a quite similar issue as with Arabian Nights.

Anyway, that's it for me on this... do as you please and sorry for bringing it up then.

[Toni Wilen]

Originally Posted by Zandig

However now if using Direct3D 11 and you right click on the WinUAE icon on the Windows taskbar and select "Close Window" it takes you back into the Amiga screen instead of closing the program.

This also oddly happened only randomly when I tried enough times.. winuae.7z may or may not fix it..

[Zandig]

Originally Posted by Toni Wilen

This also oddly happened only randomly when I tried enough times.. winuae.7z may or may not fix it..

Yes Toni,

That has indeed fixed the problem of closing WinAUE using Direct3D 11!
Thank you.

[Mclane]

Unlucky Damien, you kept saying it wasn't your cfg...The joys of trying to help

[Toni Wilen]

Originally Posted by Zandig

Yes Toni,

That has indeed fixed the problem of closing WinAUE using Direct3D 11!
Thank you.

Great. Hopefully that was last one

[Toni Wilen]

http://www.winuae.net/files/b/winuae_3610b6.7z
http://www.winuae.net/files/b/winuae64_3610b6.7z

Beta 6: (Almost there..)

- Task bar icon -> close window (possibly also other "external" close methods) didn't always work in D3D11 fullscreen mode.
- Virtual RDB non-512 byte block size support. Last update also broke it if filesystem field was empty.

Retest D3D11 mode changes etc again, thanks.

[mark_k]

Originally Posted by Toni Wilen

- Virtual RDB non-512 byte block size support. Last update also broke it if filesystem field was empty.

Not sure whether it matters, but the recently-added filesystem-in-virtual-RDB support puts 512/4 (for 512-byte or larger sectors) in fhb_BlockBytes field. It seems most(?) partitioning software puts 256/4 there, as for RDSK and PART blocks.

[AMIGASYSTEM]

Toni I do not know if the last beta did miracles, now the audio is clean and perfect, I can even listen to two MP3s without having hiccup.

[ Show youtube player ]

[Toni Wilen]

Originally Posted by mark_k

Not sure whether it matters, but the recently-added filesystem-in-virtual-RDB support puts 512/4 (for 512-byte or larger sectors) in fhb_BlockBytes field. It seems most(?) partitioning software puts 256/4 there, as for RDSK and PART blocks.

fhb_BlockBytes does not exist. If you meant rdb_BlockBytes, it is byte value (512), at least in all RDB hardfiles I checked.

[mark_k]

Whoops, typo. I meant to write fhb_SummedLongs.

[Toni Wilen]

Originally Posted by mark_k

Not sure whether it matters, but the recently-added filesystem-in-virtual-RDB support puts 512/4 (for 512-byte or larger sectors) in fhb_BlockBytes field. It seems most(?) partitioning software puts 256/4 there, as for RDSK and PART blocks.

I checked hardfiles I have, some of them have $80, some $40 in FSHD block. Probably hdtoolbox version difference.

[msayed1977]

Hi everyone,
With latest beta 6,
Using D3D9, F12 displays the GUI on the emulated Amiga background.
Using D3D11, F12 displays the GUI on Windows native screen as a background, and it takes time (not too much).

Please investigate.
Thanks Toni.

[Toni Wilen]

It is by design. D3D11 can't show GDI elements in fullscreen mode. (and why do you specifically mention b6? It has always done it!)

[msayed1977]

Originally Posted by Toni Wilen

It is by design. D3D11 can't show GDI elements in fullscreen mode. (and why do you specifically mention b6? It has always done it!)

Sorry for inconvenience.

[Toni Wilen]

I only mentioned it because normally it would have caused confusion ("was it introduced in b6 or not?"), but in this case I knew it has always been like this.
So I couldn't do anything else than complain quickly

[Toni Wilen]

Originally Posted by AMIGASYSTEM

Toni I do not know if the last beta did miracles, now the audio is clean and perfect, I can even listen to two MP3s without having hiccup.

Great but what did you do? Did you change any options, did you enable some new options? There is only small chance that it would "automatically" become faster..

[AMIGASYSTEM]

Nothing in particular I just added WASAPI, i enclose file config