WinUAE 1.5.1 beta series

[Toni Wilen]

Maybe this fixes d3d fullscreen issues..

[Marcuz]

Originally Posted by Toni Wilen

Or do you mean ONLY direct3d, including .fx-filters ONLY in fullscreen, are broken. Others work exactly like in 1.5.0? (you never said this directly..)

but i have! i said that in windowed mode everything is fine (first post today) ...

(actually, i misunderstood one thing, that there ARE NON-D3D filters: between yesterday crashes and new fx stuff, i did not separated them. my bad)

Direct3D windowed: whats wrong? (note that D3D scaling is now same as non-D3D scaling in old versions. Old scaling was inconsistent)
Direct3D fullscreen: whats wrong? Fullscreen may not be exact same as windowed yet.

Note that I ALWAYS use windowed except if report says "<blahblah> only happens in fullscreen". This is very important part, never forget it

EDIT: do you get better results if you use "full-window" mode?

the only problem, as i said is that of the gui, and only full screen, everything else i pointed are just odd stuff that i thought could help you in deciding which way to do things: the fact that the resizing of D3D is not the same in windowed mode is not a problem when the gui works fine

and yes, full window works fine too.

whatever, it's just a too hot day, i'm sorry if i poorly phrased myself.

last revision DO fix the D3D!
thanks!

[Toni Wilen]

Originally Posted by marco pedrana

last revision DO fix the D3D!
thanks!

Great. Better always repeat the "only in fullscreen"-phrase because I have habit of missing it if it is in another post

btw, d3d can still break if switching to other fullscreen resolution and then back. Another fix later..

[Toni Wilen]

Originally Posted by Toni Wilen

// MessageId: ERROR_NOT_ENOUGH_MEMORY
//
// MessageText:
//
// Not enough storage is available to process this command.
//
#define ERROR_NOT_ENOUGH_MEMORY 8L // dderror

For some reason Windows refuses to reserve that much memory. Not a WinUAE problem.

Increasing paging file size may help. (even if you have more than enough physical RAM!)

[Toni Wilen]

Attached because back2roots ftp server isn't responding.. (which also means no official release until it is fixed)

RC2:

- PAL filter was not selectable
- direct3d fullscreen mode switching really works now (non-flashing fullscreen d3d->other mode switching coming after 1.5.1)
- new autoswitching input handling got confused if multiple USB game controller had same product GUID
- fixed some harmless and ancient thread handle leaks

[Steve]

Seems pretty good to me. The only thing that doesn't work for me is the Direct3D filter. Though this is due to me not having a modern graphics card or the latest DirectX drivers installed on my machine. Still, does it have to crash WinUAE when I try to run the emulator using Direct3D filters? Why can't WinUAE generate an error message letting me know I don't have the required dll files or graphics hardware instead of just crashing?

[Toni Wilen]

Originally Posted by Steve

Seems pretty good to me. The only thing that doesn't work for me is the Direct3D filter. Though this is due to me not having a modern graphics card or the latest DirectX drivers installed on my machine. Still, does it have to crash WinUAE when I try to run the emulator using Direct3D filters? Why can't WinUAE generate an error message letting me know I don't have the required dll files or graphics hardware instead of just crashing?

Maybe because I can't test it myself? Where are the logs and crash dumps..

[Steve]

Originally Posted by Toni Wilen

Maybe because I can't test it myself? Where are the logs and crash dumps..

Ok, here are the log files from the crash. Not sure where the crash dumps are located.

[Marcuz]

works fine here. D3D and PAL are ok in fullscreen too and resizing is visible behinf the GUI all right.

[Toni Wilen]

Originally Posted by Steve

Ok, here are the log files from the crash. Not sure where the crash dumps are located.

What display card?

46-662: D3D: PS=0.0 VS=0.0 Square=0, Pow2=1, Tex Size=1024*1024

Reports no pixel shader or vertex shader version which means it must be extremely old..

[Steve]

Originally Posted by Toni Wilen

What display card?
Reports no pixel shader or vertex shader version which means it must be extremely old..

Yes I've already explained that its not a modern graphics card. Its a heap of shit!

I think its an onboard graphics chip as its made by Intel and has only 4MB of video memory. No I don't expect Direct3D filters to work on it. All I'm saying is that it would be nice if an error message would pop up instead of WinUAE crashing when it can't find the right hardware.

[Toni Wilen]

Originally Posted by Steve

Yes I've already explained that its not a modern graphics card. Its a heap of shit!

I think its an onboard graphics chip as its made by Intel and has only 4MB of video memory. No I don't expect Direct3D filters to work on it. All I'm saying is that it would be nice if an error message would pop up instead of WinUAE crashing when it can't find the right hardware.

Ok, just wanted to confirm the log was correct
Crash will be fixed before final release.

[Dr.Venom]

Originally Posted by Toni Wilen

"In future.." It isn't easy in "fastest possible" modes because windows vsync is stupid.

OK, thanks for confirming.

[hexaae]

No hope to see Apidya introduced bug (?... at least with WUAE 1.4.6 didn't happen for sure) fixed?

Ciao!

[Toni Wilen]

Originally Posted by hexaae

No hope to see Apidya introduced bug (?... at least with WUAE 1.4.6 didn't happen for sure) fixed?

Ciao!

No. can't duplicate easily enough = no fix. ("easy enough" would be for example statefile 1-2s before the problem happens)

[Toni Wilen]

bsdsocket (and most likely uaenet) are broken in rc2 (handle leak fix also closed handles that weren't supposed to be closed..)

[Toni Wilen]

RC3:

- bsdsocket broke in rc2
- D3D filter does not crash if texture creation fails (=non D3D9 compatible display card/driver)
- shader filters renamed to "D3D: <name of filter>" in GUI

Official release date: soon after winuae.net works again

[Marcuz]

cursory test, everything seems ok

[Tony Landais]

I didn't follow much what was happening the past 2 weeks but it seems I am losing ¨some¨ hardware acceleration in fullscreen with DirectX. When I go to the control panel the window refreshes very slowly and the back screen doesn't refresh. Hardware acceleration comes back when I quit or leave DirectX during emulation.
Other problem this time with OpenGL in Fullscreen and Vsync simply doesn't refresh very well. The display jumps or miss some frames... looks worse than not Vsync.
Both DirectX and OpenGLseems to work fine in window mode.

Direct X issue only tested with RC1 and RC3 and I don't think I experienced it with beta 5 or 6.
Open GL seems to be like this since 1.5.0.
Hope it makes sense

[Toni Wilen]

Originally Posted by Tony Landais

I didn't follow much what was happening the past 2 weeks but it seems I am losing ¨some¨ hardware acceleration in fullscreen with DirectX. When I go to the control panel the window refreshes very slowly and the back screen doesn't refresh. Hardware acceleration comes back when I quit or leave DirectX during emulation.
Other problem this time with OpenGL in Fullscreen and Vsync simply doesn't refresh very well. The display jumps or miss some frames... looks worse than not Vsync.
Both DirectX and OpenGLseems to work fine in window mode.

Direct X issue only tested with RC1 and RC3 and I don't think I experienced it with beta 5 or 6.
Open GL seems to be like this since 1.5.0.
Hope it makes sense

DirectX? I guess you mean Direct3D? (DirectX = everything, DirectDraw,DirectSound,Direct3D etc..)

Too late and probably display driver problem if opening GUI causes the problem. I knew that using more "advanced" D3D routine causes all kinds of driver weirdness issues..

btw, "I don't think" and "seems" does not really help either. And not mentioning display card