WinUAE 1.5.0 beta series

[Toni Wilen]

Originally Posted by marco pedrana

just a question: the problems with Picasso mode full screen + filters reported a page ago, are still there, right?

everything is fine in full screen (UAE 800 x 600 16BIT) until i enable filters (any filter, even null filter, > error is "createdevice failed") or whenever inside the emulation i try to change the resolution through prefs.

It is prolly something i do wrong, but i'm not sure what.

I don't know. I can't duplicate it and all bug reports so far have been quite unclear..

- does it ONLY happen in 16 bit fullscreen?
- does it only happen if display-panel display settings matches Picasso96 resolution?
- does new Picasso96 checkboxes in GUI change anything?
- step-by-step instructions. (does filter needs to be enabled after or before picasso96 screen is active etc..)
- what is the exact complete error message
(dumps are useless, crash happens because something failed earlier)

[Marcuz]

Originally Posted by Toni Wilen

- does it ONLY happen in 16 bit fullscreen?
- does it only happen if display-panel display settings matches Picasso96 resolution?

the picasso resolutions crash happens on full screen only.

changing of resolution:
crash happens if the resolution in the display panel is, for instance 640*480 32 BIT: inside emulation is, as said, 800*600 16BIT and it works until you change inside emulation.

with a bigger display panel setting with 16BIT (for instance 1280*800 16BIT) you can change the prefs inside WB to whatever you like 8, 16 and 32 BIT but it keeps working.

i am puzzled: aren't the picasso settings meant to override any setting you put in the display panel? or just the windowed/fullscreen option?

- does new Picasso96 checkboxes in GUI change anything?

ahem, where it is? do you mean "faster RTG"?
with Faster RTG off OpenGL changes don't crash winuae

- step-by-step instructions. (does filter needs to be enabled after or before picasso96 screen is active etc..)

either you start with filters on (any filter) or you switch it on after boot, it crash; with Direct3d, if you do it after the emulation is started, the error is this:
CreateDevice Failed, 80004005 S=1 F=0000 C=4005 (16389) ()
with OpenGL it just crashes.
with Null Filter, sometimes it works (if you just check enable, without doing changes)

i attach 2 configurations: the first it works (until you mess with the resolutions, the second doesn't start (D3D filters).

edit:
often Winuae doesn't start at all when you press "start", if after a previous crash you have restarted it (maybe is the previous dump being written?)

i've also checked: the change of resolution forces the crash even with "faster RTG" switched off

hope this helps: i'll be away all the week so i cannot check further tweaks until wednesday 09/03

[Ed Cruse]

I found a weird problem with 1500b11. I would send you a screen shot except the problem doesn’t show up on the screen shots, so I will try to describe the problem. When the Amiga comes up everything looks good, pointer is at top of screen. I’m using a WB window on my WB screen, the window is slightly shorter and down allowing the WB screen title bar to be seen. The WB screen title bar has the copyright info and the WB window title bar says Workbench. As I move the pointer down the WB screen title bar is duplicated every one or two pixels of movement, as I move the pointer back up the WB window title bar is duplicated every one or two pixels of movement. Hitting F12 and then OK clears it up, but moving the pointer again causes the same problem.

The way I cause the problem is to use "Matchhost and RTG color depth if possible" = set, full screen, and 8/16 RTG. I didn’t try all the modes, but it appears to be common with all RTG modes using 8 and 16 bit. I did try 640x480, 1024x768, 1280x1024. I was not able to cause any problems with windowed mode. Native modes seems to work also.

PC settings:
1024x768x32

Graphics Card Settings:
RTG ram = 32megs
Matchhost and RTG color depth if possible = set
Scale instead of switching resolution = set/not set
8-bit(*) – did not change
R5G6B5PC(*) – did not change
(24bit) – did not change
B8G8R8A8(*) – did not change

Display Settings:
Primary Display Driver (1024x768)
1280x1024 32 Default
640x480
FullScreen
FullScreen
Hires (Normal)
Everyframe
60 FPS
Double = set

Filter Settings:
Filter = enabled
Scale2x 2x(16bit/32bit)
Horiz size = 1x
Vert size = 1x
Autoscale = not set

Amiga Settings:
RTG 640x480x8/16
RTG 1024x768x8/16
RTG 1280x1024x8/16

[Toni Wilen]

Originally Posted by marco pedrana

OpenGL (D3D filters).

You do know that OGL/D3D is not working. Read changelogs..
If other filters crash = bug.

[crusader86x]

Hello Mr Wilen,

I think I have found a small bug which seems to be introduced with coding the "save state" option. Most times I use the "quick save state" option by redefining the keyboard it saves my game regulary if I don´t use it a few minutes. It shouldn´t do that.

Can you fix that?

[Toni Wilen]

Originally Posted by crusader86x

Hello Mr Wilen,

I think I have found a small bug which seems to be introduced with coding the "save state" option. Most times I use the "quick save state" option by redefining the keyboard it saves my game regulary if I don´t use it a few minutes. It shouldn´t do that.

Can you fix that?

"State recording" checkbox enabled? (it does not work very well anyway..)

[crusader86x]

No it´s disabled and sometimes the quick save state works fine at all, sometimes it doesn´t. Besides this the save state option fails averaged once every 10 times I think. But it is a nice function at all!

[Toni Wilen]

Originally Posted by crusader86x

No it´s disabled and sometimes the quick save state works fine at all, sometimes it doesn´t. Besides this the save state option fails averaged once every 10 times I think. But it is a nice function at all!

"not working" STILL isn't a bug report (=autoignored)

[Toni Wilen]

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

Beta 12:

- hardfile creation: sparse file option added (sparse file = non-written parts of file do not take space on HD, NTFSv5+ required)
- IDE harddrive emulation LBA48 support implemented (>128G hardfiles) NOTE! READ THIS: http://eab.abime.net/showthread.php?t=35801
- memwatch breakpoints with value detection improved if size is word or byte
- CD32 CD frame interrupt was not always cleared (Liberation CD32, perhaps others, JIT still needs to be disabled)
- mousehack (tablet) mode fix, partially broken since 1.4.6 (not tested, I need to borrow my brother's tablet first..)
- Picasso96 tweaks

[turrican3]

i can't launch it, error message :
windows xp sp2

[crusader86x]

Originally Posted by Toni Wilen

"not working" STILL isn't a bug report (=autoignored)

I tried to say that it does not work correctly if its works

[Toni Wilen]

Originally Posted by turrican3

i can't launch it, error message :

EDIT: Updated.

Oops, used wrong function, that one is Vista/Server 2008 only.. Updating soon..

[Toni Wilen]

Originally Posted by crusader86x

I tried to say that it does not work correctly if its works

Which is totally useless information. Crashes? Does not do nothing? (not even create empty file), creates faulty statefile that does not load? How do you use shortcuts? Default shortcuts or input-panel configured? etc..

Try again.

(and finally, is this really 1.5beta problem?)

[Steve]

Originally Posted by Toni Wilen

CD32 CD frame interrupt was not always cleared (Liberation CD32, perhaps others, JIT still needs to be disabled)

Liberation CD32 works perfectly now. Thanks Toni!

[Thom87]

Hi Toni.

It seems to JIT check box is broken again, I have tested only with beta 12.
If will useful I can compare other betas. Screenshots attached.

Thom

[Toni Wilen]

Originally Posted by Thom87

Hi Toni.

It seems to JIT check box is broken again, I have tested only with beta 12.
If will useful I can compare other betas. Screenshots attached.

Thom

What is exactly broken? I re-enabled direct/indirect setting on the fly (but it may not yet work properly)

[Thom87]

Originally Posted by Toni Wilen

What is exactly broken? I re-enabled direct/indirect setting on the fly (but it may not yet work properly)

If we compare to other betas (b9,b10,b11) "force settings" check box not changing to grey (inactive) others check boxes when is selected. You can still change those settings (constant jump, hard flush,no flags, FPU support), only switch/selection cannot be changed is "Direct" & "Indirect" it will always back to "Direct" if will tried to change.

Edit: I have checked when emulation was not running yet. The same is in quick start mode.

Sorry for my English. I hope You can understand what I mean.
Thom

[andreas]

Originally Posted by crusader86x

Besides this the save state option fails averaged once every 10 times I think.

Confirmed; but only if you save with EXTREMELY fast games, i. e. shoot-em ups at later levels with lots and lots of action, then this might happen once in a blue moon. Hence I always try hard to save twice, i. e. to have one backup state if I'm beyond level 10 and do not really want to replay the game all up to this point because the save state got trashed...(yes this has happened with the 0.8.xx and 0.9.xx series in the past)
Toni, I do know how hard it is to kill all side-effects there, because the blitter sometimes just shows one the way it wants to "finish", and one can't do much about it

Everybody note that saving the state with extremely fast games requires millisecond-exact accuracy. A tiny bit too early, blitter has not finished properly and after loading the state file it will guru or freeze emulation (reset works though).

[crusader86x]

I usually play "Enemy - Tempest of Violence". Its my fovourite game, but it isn´t that fast.

[smoorke]

Problems with save states are not beta specific. Please stay on topic as described in beta posting rules