Closed
Bug 601597
Opened 14 years ago
Closed 3 years ago
since D3D10 landed black flikering rectangles appears instead of trasparent frame
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: fxtech, Assigned: bas.schouten)
Details
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:2.0b7pre) Gecko/20101002 Firefox/4.0b7pre Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0b7pre) Gecko/20101002 Firefox/4.0b7pre since layers.use-d3d10 landed some site like arewefastyet.org or other site that use trasparent layer have black box instead. anyone have the same issue ? Adapter DescriptionNVIDIA GeForce 7600 GS Vendor ID10deDevice ID0392Adapter RAM512Adapter Driversnvd3dumDriver Version8.17.12.6063Driver Date9-10-2010Direct2D EnabledtrueDirectWrite EnabledtrueGPU Accelerated Windows1/1 Direct3D 10 Reproducible: Always Steps to Reproduce: 1. set layers.use-d3d10 to true 2A. go to www.google.com , search for whatever 3A. move to mouse on the upper side up and down and part of the site become black 4A. result http://i.imgur.com/tcLTs.png the issue affect even all the type of form box , an example is the forum form box http://i.imgur.com/nufyq.png Actual Results: the result is a black rectangle on all the area that should trasparent or underlined as the text writtend in a form box another simple test is to run the http://ie.microsoft.com/testdrive/Performance/PsychedelicBrowsing/Default.html and check if the lower part of the screen is a black box or trasparent layer i am using windows 7 with a DX9 card and DX10 library PS: performance on ie9 psychedelic test jump from around 1050 to 1650 point Adapter DescriptionNVIDIA GeForce 7600 GS Vendor ID10deDevice ID0392Adapter RAM512Adapter Driversnvd3dumDriver Version8.17.12.6063Driver Date9-10-2010Direct2D EnabledtrueDirectWrite EnabledtrueGPU Accelerated Windows1/1 Direct3D 10
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → bas.schouten
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Updated•14 years ago
|
blocking2.0: --- → ?
Assignee | ||
Comment 1•14 years ago
|
||
This should not block until we have a reported case with a DX10 card. (I haven't had the opportunity to try yet) Although I'm expecting it to reproduce on DX10 cards as well.
Comment 2•14 years ago
|
||
Please renominate if this ever happens with a DX10 card.
blocking2.0: ? → ---
Assignee | ||
Comment 3•14 years ago
|
||
I cannot reproduce this on my DX10 card much to my surprise, I'd like to know if someone can!
are you using nvidia card ? could you post detail about the driver used ? could you try with the latest beta driver ? http://www.nvidia.com/object/win7-winvista-32bit-260.63-beta-driver.html PS: also arewefastyet.org for my is black
Assignee | ||
Comment 5•14 years ago
|
||
(In reply to comment #4) > are you using nvidia card ? could you post detail about the driver used ? > > could you try with the latest beta driver ? > > http://www.nvidia.com/object/win7-winvista-32bit-260.63-beta-driver.html > > PS: also arewefastyet.org for my is black I'm tried with an NVidia GT230M, GT8800, and an ATI 5850, not using the beta driver but I doubt it'll matter, I can try later though. I wonder if there's some limitation to D3D10 level9_3 which I've failed to take into account.
Comment 6•14 years ago
|
||
I get this on my 6800GS. D3D10 gets a much better score though ;)
just some news ,with the build of this week , if i disable accelerate-all , loading the page www.badtaste.it www.anandtech.com etc firefox become completly unresponsive as soon as page i scrolled (but it did not crash). - Enabling accelerate-all (using D3D10) all is ok but the black flikering rectangle still here every time that a trasparent layer is used or on text forms. (im that case flash player clipping over chrome toolbar is ok) - Enabling accelerate-all (using D3D9) no black rectangle and trasparent layer are ok , but flash plugin paint over chrome toolbar when scrolled. And scrolling work on www.badtaste.it (this site use a trasparent layer for advertising)
User agent Mozilla/5.0 (Windows NT 6.1; rv:5.0) Gecko/20100101 Firefox/5.0 NVIDIA GeForce Go 7600ID produttore10deID dispositivo0398RAM scheda grafica128 Driver scheda graficanvd3dum nvwgf2um,nvwgf2umVersione driver8.17.12.7550 Data aggiornamento driver6-15-2011Direct2D attivofalseDirect Write attivofalse (6.1.7601.17563, font cache 5,07 MB) Rendering WebGLGoogle Inc. -- ANGLE -- OpenGL ES 2.0 (ANGLE 0.0.0.611) Finestre con accelerazione GPU1/1 Direct3D 9 Hi, the problem still persist with different driver. Explorer 9 use d2d without problem, http://ie.microsoft.com/testdrive/Performance/FishBowl/Default.html show about 25 fps at 50 fish. Firefox show 0 fps at 50 fish. If I turn on d2d i see many black box Firefox with forced d2d is considerably faster and render without artefact (same as Explorer9) on this site http://srufaculty.sru.edu/david.dailey/svg/balloon.svg
Reporter | ||
Comment 10•13 years ago
|
||
just a little update , i am using aurora 9.0a2 , now all is ok , just a little glitch. I still have black rectangle on auurora tab button , search engine , and tabs name just when firefox start, but if i minimize and maximize the windows or if i pass the mouse over the tab all the glitch gone and i am able to use D2D accelerated layer even with a DX9 cart on windows 7 (D2D force true and , DX9 prefer true) Graphics Adapter DescriptionNVIDIA GeForce 7600 GSVendor ID10deDevice ID0392Adapter RAM512Adapter Driversnvd3dumDriver Version8.17.12.8538Driver Date9-22-2011Adapter RAM (GPU #2)UnknownAdapter Drivers (GPU #2)UnknownDirect2D EnabledtrueDirectWrite Enabledtrue (6.1.7600.20905)ClearType ParametersGamma: 2200 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 300 WebGL RendererGoogle Inc. -- ANGLE (NVIDIA GeForce 7600 GS) -- OpenGL ES 2.0 (ANGLE 0.0.0.740)GPU Accelerated Windows1/1 Direct3D 9
Reporter | ||
Comment 11•13 years ago
|
||
before http://i.imgur.com/rlzWj.png after http://i.imgur.com/cFSr7.png
Assignee | ||
Updated•3 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•