WinUAE 2.1.0 beta series (was 2.0.2)

[Toni Wilen]

The point was: you complained about input latency in this thread WITHOUT testing using last official version. Which is big NO NO. Nothing to do with your D3D "problem" (which is perfectly on-topic but latency is guaranteed to be nothing new in this beta..)

Warp mode via uae-configuration is fixed in latest beta (no config will fix it in older versions)

I have no idea about video recording (something I don't really care)

"Unfortunately" I rarely care or support obsolete hardware or software. I can't keep adding features without dropping older stuff or result will be even worse mess.

EDIT: directdraw null filter seems to use too much cpu power, perhaps this is some older issue..

[Toni Wilen]

I lied again, non-shader is back (it was only few more lines)
http://www.winuae.net/files/b/winuae.zip "should" work with non-shader capable DX9 compatible cards again. (overlays of course are not supported)

Not really tested, don't have old enough hardware..

[Maren]

Originally Posted by andreas

Maren, telling from my (sore) eyes, this is the VERY same artifact as I can see on your Kid Chaos screenshot far above: last horizontal eighth (or tenth) of the screen feels as if viewed through colored sunglasses, or as if you look into a mirror of which the (narrow) bottom area is covered with dirt.

Indeed, exactly the same, and not only horizontally but vertically as well I was just letting him know that if he happened to spot any of the other existing abnormalities in the image, WinUAE wouldn't be to blame.

[Photon]

Originally Posted by Toni Wilen

The point was: you complained about input latency in this thread WITHOUT testing using last official version. Which is big NO NO. Nothing to do with your D3D "problem" (which is perfectly on-topic but latency is guaranteed to be nothing new in this beta..)

Whoa. Some misunderstanding. All tests were on latest beta, and compared to next latest beta, and I explained the reason for the latency... 25-40 fps with anything except Filter:none on. In both those 'almost latest' betas. I haven't tried an older stable version yet at all! (I have no idea what could have given you that impression...)

Originally Posted by Toni Wilen

Warp mode via uae-configuration is fixed in latest beta (no config will fix it in older versions)

I will start again from a Quickstart config, and see if it works. If that's what you mean?

I will test immediatlement!

No-shader-support is back too \o/


ps. I did disagree with your decision to make an emu that runs fine on very old CPUs demand PS2.0 gfx cards, but I am in no way interfering with the path you think is right for WinUAE, and any decisions you make is yours to make. I'm not the dev of WinUAE, you are. If you think you see a complaint in my posts, it is unintentional or misinterpreted. Or maybe I didn't @#$%^&* check the fps on this machine before If I can code A500 on this laptop using any settings, I'm happy. If not, it will serve as a generic PC<-> Amiga file transfer device, as was intended.

[Photon]

Test results (as always with latest beta):

Direct3D works, gives slightly different scanlines look than DirectDraw in PAL filter (maybe I lowered resolution in between), and 39-45 fps during bootup rather than 37 fps with DDraw.

"uae-configuration gfx_framerate=10" gives "uae-configuration failed returncode 20". Should I get a newer uae-configuration command? This one is from latest stable, most probably. I'm afraid I commented the above line away during next last beta tests, so I'd have to check if it worked with that (do you want me to?)

Config and logs attached.

[Maren]

Here's something that crashes WinUAE:

1. Run WinUAE.
2. Go fullscreen.
3. Open a file selection box (e.g. end+F1)
4. While in there, press F1.

Logs, config and .dmp file: http://www.fileshost.com/download.php?id=F24DC4571

[andreas]

@Photon
In general, "returncode 20" sounds like too old or incompatible kickstart. (AmigaDOS CLI executables may show this if they're made for OS 2.0+ and you attempt to use them with 1.x)
Maybe it works in 3.0 instead of the 3.1 that you used.

[Photon]

Returncode 20 means something only to the one who programmed the CLI command. (Not necessarily Toni.)

I'm pretty sure uae-configuration would work as well with 3.1 as with 3.0.

I started out with the latest beta and the quickstart, ie. 1.3, and then changed kickstart and display settings.

Edit: I don't have kick 3.0 (other than as original chips), but I tried with kick 2.0. It does work (ie. no interruped s-seq), but I notice no 2-300 fps like with my warpmode hotkey, neither with the config's PAL filter, nor with Filter:none. (If that helps.)

Edit: Restarted with quickstart (1.3) and only added the harddrive directory with the s-seq with the uae-configuration command first in it, and it didn't affect the fps then either. 49/50 fps.

[Maren]

Originally Posted by Toni Wilen

Does the problem disappear if you edit winuae.fx and replace

AddressU = Clamp;
AddressV = Clamp;

with "Wrap" like this:

sampler	OverlaySampler = sampler_state {
	Texture	  = (OverlayTexture);
	MinFilter = POINT;
	MagFilter = POINT;
	MipFilter = NONE;
	AddressU  = Wrap;
	AddressV  = Wrap;
};

I know the question wasn't directed at me, but you might want to know that fixed the problem here

[Toni Wilen]

Originally Posted by Photon

"uae-configuration gfx_framerate=10" gives "uae-configuration failed returncode 20". Should I get a newer uae-configuration command? This one is from latest stable, most probably. I'm afraid I commented the above line away during next last beta tests, so I'd have to check if it worked with that (do you want me to?)

Command line syntax is uae-configuration <param> [<value>] (without '=')

Note that uae-configuration does not work if you have configuration that does not need "uae boot rom" (filesystem, bsdsocket, etc.. expansions that need hooks in Amiga memory)

[Toni Wilen]

Originally Posted by Photon

ps. I did disagree with your decision to make an emu that runs fine on very old CPUs demand PS2.0 gfx cards, but I am in no way interfering with the path you think is right for WinUAE, and any decisions you make is yours to make. I'm not the dev of WinUAE, you are. If you think you see a complaint in my posts, it is unintentional or misinterpreted. Or maybe I didn't @#$%^&* check the fps on this machine before If I can code A500 on this laptop using any settings, I'm happy. If not, it will serve as a generic PC<-> Amiga file transfer device, as was intended.

It does not run "fine" if it can't keep stable 50Hz refresh rates (CPU% always under 100%). Also it really does not need Direct3D, DirectDraw without filtering works also fine, scaling is extra feature that is not needed for "fine" running

10 years or so old PC hardware is something I won't care at all. (even 5 years equals near obsolete garbage for me) I know most of you won't agree but I hope it explains why some things can and will happen

I didn't see your post as complaints, I only misunderstood it partly.. (and you should have said CPU% is higher on this and that version, instead of talking about FPS)

[john4p]

Originally Posted by Toni Wilen

You should see some difference if you change horizontal or vertical scaling. (graphics errors in right border in some specific scaling factors if mode is "Clamp")

Hmm...there is no file "winuae.fx" in the WinUAE-folder of my home pc.

But every mask seems to work flawless (at 640x400).

[Toni Wilen]

Originally Posted by john4p

Hmm...there is no file "winuae.fx" in the WinUAE-folder of my home pc.

But every mask seems to work flawless (at 640x400).

You do have it somewhere in plugins. Masks won't work without it. (you are using "too small" resolution to see the problem)

[Maren]

Update: The "wrap" trick works great for plain scanlines, but now that I've tried more complex masks, I can spot a new artifact which's slightly less annoying than the "border dimming". Will make comparison screenshots later.

[Toni Wilen]

Originally Posted by Maren

Update: The "wrap" trick works great for plain scanlines, but now that I've tried more complex masks, I can spot a new artifact which's slightly less annoying than the "border dimming". Will make comparison screenshots later.

try winuae.zip before doing any screenshots, it may be already fixed (if you mean small "seam" appearing where the graphics issue was before "wrap")

[Maren]

Originally Posted by Toni Wilen

try winuae.zip before doing any screenshots, it may be already fixed (if you mean small "seam" appearing where the graphics issue was before "wrap")

Yes, that's exactly what I was seeing, but you've nailed the bugger and now it's perfect

[Maren]

Ok, apparently WinUAE's internal scanlines effect is broken for "Null Filter" (no scanlines appear at all) while the PAL one gets a double-scanline in the middle, but I think I saw this in the non-winuae.zip versions as well.



I'm in a hurry right now but I'll post the logs and everything else as soon as I get a chance.

[Toni Wilen]

Originally Posted by Maren

Ok, apparently WinUAE's internal scanlines effect is broken for "Null Filter" (no scanlines appear at all) while the PAL one gets a double-scanline in the middle, but I think I saw this in the non-winuae.zip versions as well.



I'm in a hurry right now but I'll post the logs and everything else as soon as I get a chance.

What are "internal" scanlines? Display panel scanlines or d3d scanlines?

[Maren]

D3D of course. Ever since filters started working here, I haven't touched the display panel's.

[Toni Wilen]

Originally Posted by Maren

Ok, apparently WinUAE's internal scanlines effect is broken for "Null Filter" (no scanlines appear at all) while the PAL one gets a double-scanline in the middle, but I think I saw this in the non-winuae.zip versions as well.

should be fixed in updated winuae.zip

Originally Posted by Maren

D3D of course. Ever since filters started working here, I haven't touched the display panel's.

Display panel scanlines are more "internal" than filter panel scanlines. (and quite useless now because they are "burned" to emulated display which makes ugly result if there is any scaling..)