|
Yes, Direct3D9Ex requires the new graphics
subsystem that was introduced with Windows Vista. The reason why you lost the context/device
when the screen saver kicks in is a desktop switch. While your browser runs in
a general user desktop the screen saver uses the same desktop as the
login/security system. Direct3D9 always throw away all devices when such an
desktop switch happens. You should be able to test this by locking the desktop
(windows key + L) instead of waiting for the screen saver. -Ralf From: owner-public_webgl@khronos.org
[mailto:owner-public_webgl@khronos.org] On Behalf Of Alexey Marinichev Windows XP does not implement Direct3D9Ex interface.
According to the comment in Display.cpp: // Use Direct3D9Ex if available. Among
other things, this version is less // inclined to report a lost context, for
example when the user switches // desktop. Direct3D9Ex is available in
Windows Vista and later if suitable drivers are available. On Tue, Feb 22, 2011 at 1:51 PM, Mark Callow <callow_mark@hicorp.co.jp> wrote: It was WindowsXP so I guess it must have been the screen saver. Why
does that cause a loss of context? Regards
Screensaver should not, at least in theory, affect Chrome in
any OS other than Windows XP. Context lost event is also fired if GPU process crashes. On Mon, Feb 21, 2011 at 4:52 PM, Steve Baker <steve@sjbaker.org>
wrote:
----------------------------------------------------------- |