WinUAE 2.1.0 beta series (was 2.0.2)

[Ed Cruse]

I downloaded the latest B5 and didn't have any crashing problems but the first two problems are still there. The first two problems are with full screen, Windowed, NTSC and PAL. I also noticed that when using the other filters with D3D and the size is really big, bilinear gets used like it's supposed to be, with null the size is correct but point is used.

[hexaae]

Originally Posted by Ed Cruse

Shouldn't the extra settings show bilinear and point, I only see bilinear. Also when displaying bilinear with D3D checked, the display looks like point.

I can confirm this. Moreover the "filter" gadget settings are not stored when you save UAE cfg (e.g. D3D: 2xSaL) but it's always "none" when you reload...

[Toni Wilen]

Point/Bilinear setting works as designed. Try to understand how the selection works first

[Dunny]

Originally Posted by Toni Wilen

Point/Bilinear setting works as designed. Try to understand how the selection works first

Confirmed, though enabling bilinear filtering by moving a slider control is probably the worst, most non-intuitive UI decision I've seen in a very long time ;-)

But then, this is WinUAE so it's totally in-keeping with the rest of the UI! We know how much you hate that sort of thing

D.

[Toni Wilen]

Originally Posted by Dunny

Confirmed, though enabling bilinear filtering by moving a slider control is probably the worst, most non-intuitive UI decision I've seen in a very long time ;-)

But then, this is WinUAE so it's totally in-keeping with the rest of the UI! We know how much you hate that sort of thing

D.

Yeah, it was quickest way to have it in GUI without new objects

[turrican3]

Many doesn't work anymore with filters, do we have to report it ?
I don't think so because because you seem to be aware.
ps i just bought windows 7 is there incompatibility left ?

[Toni Wilen]

Originally Posted by turrican3

Many doesn't work anymore with filters, do we have to report it ?
I don't think so because because you seem to be aware.
ps i just bought windows 7 is there incompatibility left ?

What do you mean by not work?

I have used Windows 7 since first public betas.

[Toni Wilen]

winuae.zip updated again (24.01.2010). Fixes wrong scaling when d3d is combined with non-1x software filter.

[hexaae]

Originally Posted by Toni Wilen

winuae.zip updated again (24.01.2010). Fixes wrong scaling when d3d is combined with non-1x software filter.

Filter settings (e.g. D3D: 2xSaL) are not yet saved in the config file. When you reload the cfg it is set to "none".

[Maren]

Native on screen LED regression.

[Maren]

CPU usage skyrockets during this routine from the "Official Commodore France A1200 demo" by Digital, creating an overall slowdown.

I know CE 68020 emulation remains experimental, but since this works ok in 2.0.1, I thought maybe it was worth mentioning.

Same config as above. Get the savestate here: http://www.fileshost.com/download.php?id=F2B691741

Cheers.

[UncleSpam]

Originally Posted by Maren

CPU usage skyrockets during this routine from the "Official Commodore France A1200 demo" by Digital, creating an overall slowdown.

I know CE 68020 emulation remains experimental, but since this works ok in 2.0.1, I thought maybe it was worth mentioning.

Same config as above. Get the savestate here: http://www.fileshost.com/download.php?id=F2B691741

Cheers.

Since I had that demo handy, I tried it. From a CPU usage of 40% on average, it spiked to slightly over 50% during that segment.

FYI, I'm running in cycle exact mode, otherwise I get graphic glitches during the demo.

- Bogdan

[john4p]

Great, now we can combine scalers with bilinear filtering and transparent scanlines.

But with hq2x there are glitchy lines and other gfx errors with Direct3D active:



Without Direct3D it's perfect as always:



Note there is no stretching involved (just the exact double resolution).


The implementation of the ComboBox containing "Bilinear", "Scanline transparency" and "Scanline level" seems to have a bug:

as soon as you select the 2nd option you can't select the first (Bilinear) anymore. And as soon as you select the 3rd option you can't select any of the first two anymore...

[Toni Wilen]

Originally Posted by john4p

The implementation of the ComboBox containing "Bilinear", "Scanline transparency" and "Scanline level" seems to have a bug:

This was already fixed in winuae.zip "alpha update".

[Toni Wilen]

Originally Posted by john4p

But with hq2x there are glitchy lines and other gfx errors with Direct3D active:

I assume this is not 2.0.2 beta specific?

[Toni Wilen]

Originally Posted by Maren

CPU usage skyrockets during this routine from the "Official Commodore France A1200 demo" by Digital, creating an overall slowdown.

I know CE 68020 emulation remains experimental, but since this works ok in 2.0.1, I thought maybe it was worth mentioning.

I don't see any CPU usage difference between betas and 2.0.1 using A1200 most compatible quickstart.

[Maren]

Would it be of any help if I posted the logs for the demo running on 2.0.1 for comparison?

[Toni Wilen]

Originally Posted by Maren

Would it be of any help if I posted the logs for the demo running on 2.0.1 for comparison?

You won't see any useful differences in logs.. Check CPU% on screen led.

[Maren]

Originally Posted by Toni Wilen

Check CPU% on screen led.

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

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.

[dlfrsilver]

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

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

I'm having the same result as UncleSpam