Closed GoogleCodeExporter closed 9 years ago
I've got patches which fix the asserts, but I still can't get anything
rendering on the d3d9 path… Is it possible there is other stuff missing
Chrome side for the d3d9 path?
Original comment by dan...@transgaming.com
on 13 Dec 2011 at 10:50
Canaries should be fine, but if you're building chrome yourself from trunk
there's a bug where D3D9 doesn't work on Vista and up. In theory you should be
able to use the --disable-image-transport-surface command-line flag, but I
think in practice you have to edit some code for it to work (add "0 &&" to line
196 of content/common/gpu/image_transport_surface_win.cc).
Original comment by jbauman@chromium.org
on 13 Dec 2011 at 11:01
Yeah I was trying to use d3d9 on Win7 using the build vangelis linked above. I
wasn't getting any errors, just a white page, even when I had the managed
textures disabled. If it's known not to work, I'll just get my patches cleaned
up and committed tomorrow.
Original comment by dan...@transgaming.com
on 14 Dec 2011 at 1:13
For the time being you'll need to run chrome with
--disble-image-transport-surface if you're using d3d9 (non-ex) on windows 7.
Al is looking into fixing this.
Original comment by vange...@google.com
on 14 Dec 2011 at 10:11
Should be fixed in r923.
Tested in the current canary build in d3d9 mode on win7 and it seems to be
working fine now.
Original comment by dan...@transgaming.com
on 16 Dec 2011 at 11:36
Original issue reported on code.google.com by
vange...@google.com
on 12 Dec 2011 at 8:20