01 August 2008, 17:59 | #201 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
Maybe this fixes d3d fullscreen issues..
Last edited by Toni Wilen; 05 August 2008 at 16:06. |
01 August 2008, 18:37 | #202 | ||
Registered User
Join Date: Jun 2002
Location: .
Age: 48
Posts: 5,562
|
Quote:
(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) Quote:
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! |
||
01 August 2008, 19:29 | #203 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
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.. |
03 August 2008, 09:37 | #204 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
Increasing paging file size may help. (even if you have more than enough physical RAM!)
|
03 August 2008, 13:18 | #205 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
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 Last edited by Toni Wilen; 16 August 2008 at 21:07. |
03 August 2008, 13:34 | #206 |
I Identify as an Ewok
Join Date: Jul 2001
Location: North Lincolnshire
Age: 45
Posts: 2,356
|
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?
|
03 August 2008, 13:40 | #207 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
Quote:
|
|
03 August 2008, 14:15 | #208 |
I Identify as an Ewok
Join Date: Jul 2001
Location: North Lincolnshire
Age: 45
Posts: 2,356
|
Ok, here are the log files from the crash. Not sure where the crash dumps are located.
|
03 August 2008, 14:36 | #209 |
Registered User
Join Date: Jun 2002
Location: .
Age: 48
Posts: 5,562
|
works fine here. D3D and PAL are ok in fullscreen too and resizing is visible behinf the GUI all right.
|
03 August 2008, 14:45 | #210 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
|
03 August 2008, 15:13 | #211 | |
I Identify as an Ewok
Join Date: Jul 2001
Location: North Lincolnshire
Age: 45
Posts: 2,356
|
Quote:
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. |
|
03 August 2008, 16:04 | #212 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
Quote:
Crash will be fixed before final release. |
|
03 August 2008, 21:35 | #213 |
Registered User
Join Date: Jul 2008
Location: Netherlands
Posts: 485
|
|
04 August 2008, 00:37 | #214 |
Bug hunter
Join Date: Jul 2006
Location: Italy
Age: 48
Posts: 2,171
|
No hope to see Apidya introduced bug (?... at least with WUAE 1.4.6 didn't happen for sure) fixed?
Ciao! |
04 August 2008, 07:53 | #215 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
No. can't duplicate easily enough = no fix. ("easy enough" would be for example statefile 1-2s before the problem happens)
Last edited by Toni Wilen; 04 August 2008 at 08:19. |
04 August 2008, 16:07 | #216 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
bsdsocket (and most likely uaenet) are broken in rc2 (handle leak fix also closed handles that weren't supposed to be closed..)
|
04 August 2008, 20:33 | #217 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
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 Last edited by Toni Wilen; 16 August 2008 at 21:07. |
04 August 2008, 21:26 | #218 |
Registered User
Join Date: Jun 2002
Location: .
Age: 48
Posts: 5,562
|
cursory test, everything seems ok
|
04 August 2008, 22:25 | #219 |
Zone Friend
Join Date: Mar 2003
Location: uk
Posts: 426
|
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 |
04 August 2008, 23:02 | #220 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
Quote:
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 |
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
WinUAE 2.5.1 beta series | Toni Wilen | support.WinUAE | 69 | 22 December 2012 10:22 |
WinUAE 2.3.3 beta series | Toni Wilen | support.WinUAE | 124 | 17 September 2011 15:48 |
WinUAE 2.3.2 beta series | Toni Wilen | support.WinUAE | 79 | 31 May 2011 19:39 |
WinUAE 2.3.0 beta series (was 2.2.1) | Toni Wilen | support.WinUAE | 229 | 22 September 2010 19:20 |
|
|