WinUAE 2.1.0 beta series (was 2.0.2)

[Maren]

Originally Posted by dlfrsilver

i have checked via your savestate, you use non-CE mode

Not really, I'm using CE, actually I never disable it unless I'm testing a problem software that won't run ok when it's on.

Originally Posted by dlfrsilver

non-ce mode = CPU 100% all the time for me.
ce-mode = CPU 43/44% only all the time.

That's even more weird. Here CPU usage stays very low when CE is off.

[dlfrsilver]

once loaded, your savestate shows that you use non-ce mode.

With non-ce mode i get graphic bugs, while 68020 CE mode give perfect result.

Here is what i find once the savestate is loaded :

- More compatible is not ticked when it should ;
- cycle exact mode is OFF instead of ON ;
- sprite collision should be FULL ;
- Chipset Extra => A1200 instead of generic ;

(PS : i use Windows 7, you use Windows XP SP3...does it matter ?? :| )

[Toni Wilen]

Originally Posted by dlfrsilver

once loaded, your savestate shows that you use non-ce mode.

With non-ce mode i get graphic bugs, while 68020 CE mode give perfect result.

Here is what i find once the savestate is loaded :

- More compatible is not ticked when it should ;
- cycle exact mode is OFF instead of ON ;
- sprite collision should be FULL ;
- Chipset Extra => A1200 instead of generic ;

(PS : i use Windows 7, you use Windows XP SP3...does it matter ?? :| )

Maybe you should try again before assuming anything..

Collision should never be full (useless CPU usage, there is only one game that needs it..)

Savestate does not include (and never has included) ce mode or sprite collisions or any other other setting that can be changed on the fly...

[Maren]

Well, no idea why or even how you're seeing that. Be sure to check my config and try this new savestate: http://www.fileshost.com/download.php?id=82A241801

[Toni Wilen]

Originally Posted by Maren

That's exactly how I figured out what was causing the slowdown

Exactly the reason for my "not enough information" reply. Always include numbers.

In 2.0.1 CPU usage fluctuates between 12 and 14%, spiking up to 23/28% a couple of times. In this beta, it starts at 14% then goes up to 99/98% and stays there for the rest of the routine.

12-14% seems really too low for A1200 CE-mode. I hope you are using standard test setup: windowed, no filters etc..

Are you using "official" beta or latest winuae.zip? (try both please) Nothing really weird in logs? (like continuous messages)

[dlfrsilver]

Originally Posted by Toni Wilen

Maybe you should try again before assuming anything..

Collision should never be full (useless CPU usage, there is only one game that needs it..)

Savestate does not include (and never has included) ce mode or sprite collisions or any other other setting that can be changed on the fly...

I have a quadricore, so about collision, a little bit less or more doesn't make a big difference.

Thanks about the info concerning savestates, i was not aware about this ^^.

[Toni Wilen]

Originally Posted by dlfrsilver

I have a quadricore, so about collision, a little bit less or more doesn't make a big difference.

Modern CPUs with huge and fast caches and really fast memory busses (especially core i5/i7) won't really care about that but not everyone have those and full collision is the most useless CPU cycle eater ever.

And there is no known AGA program that requires full collision

Thanks about the info concerning savestates, i was not aware about this ^^.

Ok but next time adjust some setting, reload the state and then recheck settings before posting

[Maren]

Originally Posted by Toni Wilen

Exactly the reason for my "not enough information" reply. Always include numbers

Sorry, I thought that information was included somewhere in the logs.

Originally Posted by Toni Wilen

12-14% seems really too low for A1200 CE-mode. I hope you are using standard test setup: windowed, no filters etc..

Ok, here's an update. I erased everything in my WinUAE folder and started with a clean config and now I can see that 12% was indeed a 94%. It totally beats me what was causing that 12% to appear.

With that a lil bit more clear. This is what I have:

1. Routine with vsync on = starts at 94% and goes up to 108%

2. Routine with vsync off = starts at 100% and goes up to 108% (notice that CPU usage will always output 100% or more when vsync is on during A1200 emulation, at least here)

Originally Posted by Toni Wilen

Are you using "official" beta or latest winuae.zip? (try both please) Nothing really weird in logs? (like continuous messages)

Tried it on both builds and same results. No idea about the logs, wouldn't even know what to look for besides these messages and nope, nothing like that was logged

Guess there's a CPU increase, but it isn't nearly as much as previously suggested, it's just that WinUAE is already using a lot of CPU so it only takes a minor increase for things to go wrong.

[dlfrsilver]

the results about my config i posted where done by adjusting.

[Toni Wilen]

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

Beta 6:

- filter panel GUI issues fixed
- arcadia quickstart incorrectly enabled CD mode (b5)
- directory filesystem ERROR_USER_MAPPED_FILE mapped to OBJECT_IN_USE
- directory filesystem: complain about unimplemented error(s) only once
- unminimize changed display size (update to b4 fix)
- window resize was ignored unless both width and height changed (b4)
- OSD had extra gap in right border (b1)
- D3D fullscreen handling update, device loss handling improved, possible ALT-TAB weirdness should be gone now, D3D debug runtime warnings fixed

[hexaae]

Is it by design the fact it doesn't save Filter Settings like "D3D: 2xSaL" in the cfg file?
Whenever I reload WUAE cfg the pop-down gadget is reset to "none".
"Null filter" gets saved instead.

[Toni Wilen]

Originally Posted by hexaae

Is it by design the fact it doesn't save Filter Settings like "D3D: 2xSaL" in the cfg file?
Whenever I reload WUAE cfg the pop-down gadget is reset to "none".
"Null filter" gets saved instead.

It is a bug but it can still work in some specific situations = it worked when I tested

fixed in latest winuae.zip

[Toni Wilen]

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

Beta 7:

- Direct3D errors didn't properly reset back to non-D3D mode
- pixelshader filter configuration save/load didn't work
- window was closed and opened when some filter parameters changed
- use Direct3D9Ex when running on Vista/7 or newer
- less tearing in non-vsync D3D fullscreen mode
- added support for D3D mask/overlay image files (config file only, gfx_filter_mask=<path>) Automatically tiled if image is smaller than display size, uses D3DX function to load image files, .bmp, .dds, .dib, .hdr, .jpg, .pfm, .png, .ppm, and .tga supported (this was requested somewhere in req.UAE Wishlist long time ago or something..)
- skip frames in D3D vsync mode when turbo is enabled
- WinXP center dialogs in fullscreen mode works now properly
- clear D3D mode borders if screen is larger than Amiga display window

[Maren]

About the mask thing:

You see, in MAME, these overlaid images are processed through what seems to be akin to a "Multiply" layer blending mode (more on that here) thus when applying an overlay image such as you end up with something like:


(look like regular scanlines but brighter )

However, WinUAE doesn't seem to be doing anything similar so the result is rather, hmmm....




Basically I'd like to know if this is supposed to happen.

[Toni Wilen]

It only uses alphablending. Nobody said it was supposed to work differently

EDIT: looks like correct blending mode is modulate.

[Dunny]

Toni, just a little query - with the latest round of betas from this thread, every time I start WinUAE from the executable I'm warned that the selected disk image needs a 2.04 or later system ROM. No floppy disks are selected in the quickstart or floppy disk panes.

If I start WinUAE by launching any of my configuration files (default, default A500 or my A1200 config) then the error doesn't appear.

D.

[Toni Wilen]

Originally Posted by Maren

About the mask thing:

winuae.zip uses now "modulate". Not sure if it is correct, looks a bit too dark but I don't use filters or scanlines or stuff

(note: not available if shader filter is enabled)

Originally Posted by Dunny

Toni, just a little query - with the latest round of betas from this thread, every time I start WinUAE from the executable I'm warned that the selected disk image needs a 2.04 or later system ROM. No floppy disks are selected in the quickstart or floppy disk panes.

If I start WinUAE by launching any of my configuration files (default, default A500 or my A1200 config) then the error doesn't appear.

Does it happen if default.uae is removed? (do not delete it, attach it if it "fixes" the problem)

[Dunny]

Removing the Default.uae config file fixed it - however, upon examination of the file it's very, very damaged. I don't know why, but re-installing from the latest release and adding the new executable works a treat....

Sorry to have bothered you with that one.

I might mention that Direct3D fails hard (black screen) in beta 7. I only get a display if I use an RTG mode or if I disable Direct3D on the filters pane. Beta 6 runs Direct3D mode just fine.

I'll attach logs from both beta6 and beta7 for comparison.


PS - It might be completely unrelated, but having been playing a lot of Breathless lately, I find that I cannot run it at any great speed if I have vsync enabled - sound stutters like mad, even with a buffersize set to 4. However, with vsync disabled I get a very smooth 50fps and no sound skipping, even with the most intensive graphics options enabled. Obviously, that's under beta 6 as I can't get beta 7 to output D3D

However, I couldn't say what release this behaviour began, and it's no big deal.

Cheers,

D.

WinUAE_logs.zip

[Toni Wilen]

Originally Posted by Dunny

I might mention that Direct3D fails hard (black screen) in beta 7. I only get a display if I use an RTG mode or if I disable Direct3D on the filters pane. Beta 6 runs Direct3D mode just fine.

Real beta 7 or some alpha?

PS - It might be completely unrelated,

Most likely it is. VSync rarely works properly in too fast modes.

[Dunny]

Originally Posted by Toni Wilen

Real beta 7 or some alpha?

Ah, sorry - your last two zips posted here (they identify themselves at 6 and 7 in the window caption). I might add that I'm running Vista (all drivers fully updated).

D.