14 December 2009, 21:42 | #1 | |
Registered User
Join Date: Mar 2005
Location: London UK
Posts: 1,532
|
Direct3D onscreen led issue
I think this is the same problem I posted in a similar thread a while back, see the picture below.
This has happend in beta16 and beta17 and then I tested it today in the new stable WinUAE 2.0.0 release and it did the same thing. Seems to only happen when filters are on, I use direct3D Filter. Logs attached. (First Boot of a fresh Install of Classic Workbench and WinUAE 2.0.0) Quote:
I have a Geforce 7600 GS with latest drivers and DirectX 9.0C on Windows XP Home SP3 I did all DirectX tests and all were fine. Last edited by Kitty; 15 December 2009 at 02:34. |
|
15 December 2009, 09:10 | #2 | |||
Registered User
Join Date: Mar 2005
Location: London UK
Posts: 1,532
|
Quote:
If you mean my graphic card drivers, they cant possibly be that buggy, they are official NVidia drivers and work perfectly fine on WinUAE 1.6.1 with on screen leds and any filter mode, like I said this has happend in earlier betas and the latest build, so I believe something has changed in WinUAE since 1.6.1 Also its not just myself who experienced this problem, others have too, how many hosts can have the very same buggy drivers? To say just disable onscreen leds isnt really solving the problem is it. I was discussing this problem on eab irc and was thinking about actually submitting this as a proper bug. Quote:
Was there any other threads I missed that ended in a solution then? Quote:
Im destined to stay on 1.6.1 unless there is some kind of fix Edit Did another test with leds off as you suggested, stills the same results so cant be onscreen leds. My filter setting If filters arnt used there is no problem but as I use filters (as I imagine many others do) WinUAE 2.0.0 is unusable for me Maybe I should make a new thread about this problem if its not related as you suggest. Edit Test with ClassicWBUAE fresh install results were better but its still there. Also I noticed if you load up with onscreens leds then turn them off and reboot they are still stuck there but static with ClassicWB UAE setup WinUAE 2.0.0 Last edited by Kitty; 15 December 2009 at 18:23. |
|||
15 December 2009, 16:32 | #3 |
Registered User
Join Date: May 2009
Location: NY / USA
Posts: 266
|
Same thing happens for me when I turn on the Direct3D filter - glitches to the bottom of the screen.
|
15 December 2009, 17:49 | #4 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,503
|
I consider it display driver bug because all reports have one thing common: NVidia. (and possibly WinXP)
I have ATI desktop and NVidia laptop (Win7): can't duplicate. |
15 December 2009, 18:12 | #5 | |
Registered User
Join Date: Mar 2005
Location: London UK
Posts: 1,532
|
Quote:
So your saying everyone who has a NVidia graphics card will either have to change to an ATI with windows 7 setup or be stuck with WinUAE 1.6.1 for eternity ? |
|
15 December 2009, 18:17 | #6 |
HOL/FTP busy bee
Join Date: Sep 2006
Location: Germany
Age: 46
Posts: 31,519
|
Only happens with onscreen LEDs enabled and far less intrusive in windowed mode here (for DirectX filters). Which GFX card do you use Zandig? I use GeForce 7800 GT on XP
|
15 December 2009, 18:18 | #7 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,503
|
Because onscreen leds was changed to 3D sprites in 2.0 (better performance, free transparency etc..)
|
15 December 2009, 18:24 | #8 |
HOL/FTP busy bee
Join Date: Sep 2006
Location: Germany
Age: 46
Posts: 31,519
|
I'm just wondering if it's something specific for GeForce 7xxx cards. It's quite hard to produce the error anyway.
|
15 December 2009, 20:31 | #9 | |
The Spanish Songstress
Join Date: Jul 2009
Location: Finland
Posts: 114
|
Quote:
Most certainly a DX or a driver bug with those symptoms (gfx mem seems to get corrupted)... Sorry, I haven't verified with the released v2 yet (just got out of a long crunch), but I'll try to see if I can replicate this issue still and report back. |
|
15 December 2009, 20:46 | #10 |
Registered User
Join Date: May 2009
Location: NY / USA
Posts: 266
|
|
15 December 2009, 20:50 | #11 |
HOL/FTP busy bee
Join Date: Sep 2006
Location: Germany
Age: 46
Posts: 31,519
|
Thanks Zandig So much for the 7xxx, but the XP bit is interesting.
|
15 December 2009, 21:07 | #12 |
The Spanish Songstress
Join Date: Jul 2009
Location: Finland
Posts: 114
|
|
23 December 2009, 19:51 | #13 |
Registered User
Join Date: May 2009
Location: NY / USA
Posts: 266
|
WinUAE 2.0.1 Direct3D Filter glitch
Hi Toni,
This glitch is still present in 2.0.1 although not as bad as the previous 2.0 release version. Under any configuration when I enable the Direct3D filter (doesn't matter if it's Point of Bilinear) I get a graphical glitch at the bottom of the screen. Below is a pic of the bootup screen so you can see it clearly: The glitch remains on the workbench screen or anything I run after. Going back to version 1.61 fixes the problem. Also not using the Direct3D filter makes the problem go away. My info: Windows XP / Service Pack 3 Nvidia 9800GT Happy Holidays and thanks for the hard work you do on this great program! |
23 December 2009, 20:06 | #14 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,503
|
Above post merged. XP and Nvidia again..
|
24 December 2009, 08:39 | #15 |
Registered User
Join Date: Mar 2005
Location: Germany
Age: 43
Posts: 73
|
Quick workaround: F12, Switch to Null Filter, exit config window, F12 again, switch back to D3D. Problem "solved".
You'll have to do it every time you start Winuae, though. |
27 December 2009, 05:02 | #16 | ||
Registered User
Join Date: Mar 2005
Location: London UK
Posts: 1,532
|
Quote:
Quote:
This you must realise now is something in WinUAE that needs to be fixed and not just a Geforce/WinXP bug. Not everyone wants to/can afford to upgrade to windows 7. Last edited by Kitty; 27 December 2009 at 05:09. |
||
27 December 2009, 12:53 | #17 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,503
|
Virtual PC does not support 3D hardware. And it STILL is a display driver or OS bug if it stays between WinUAE sessions.
|
27 December 2009, 17:04 | #18 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,503
|
If someone wants this "fixed" someway, I need more information _when_ it does _not_ happen.
All combinations tested (windowed, fullscreen, 16 and 32 bit in filter panel, using wb hand screen only). Test twice to make sure previous test does not change following test. |
27 December 2009, 17:14 | #19 |
Banned
|
wait i saw same issue on my intel card atom pc but it happens only direct3d filter
|
27 December 2009, 18:42 | #20 |
Banned
|
and confirmed it not happens with 1.6.1
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
DirectDraw VS Direct3D centering | msayed1977 | support.WinUAE | 2 | 10 April 2013 19:19 |
Direct3D white scanlines? | NoX1911 | support.WinUAE | 13 | 06 December 2009 11:34 |
A1200 LED to PC-Case LED? | PoliceQuest | support.Hardware | 2 | 30 August 2008 13:09 |
Keyboard led issue | Mad-Matt | support.WinUAE | 7 | 20 November 2007 12:16 |
Direct3D Filter version 1.2.0 | rmzalbar | support.WinUAE | 2 | 21 May 2006 11:18 |
|
|