Opened 10 years ago
Closed 8 years ago
#13282 closed defect (obsolete)
GPU tests don't work with WDDM driver
Reported by: | teo8976 | Owned by: | |
---|---|---|---|
Component: | WDDM | Version: | VirtualBox 4.3.14 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Linux |
Description
I installed the guest additions on a Windows 7 64bit guest on Ubuntu 14.04 host, and I chose to install the "experimental" WDDM drivers instead of the "basic" GPU acceleration support.
By the name "experimental" I do expect it to have some issues, but I would expect it to at least mostly work. Something that doesn't even remotely work should not be called "experimental", it should be called "not even worth trying", "not fit for release" or "non-working", to make it clear that it's of interest only to developers that are willing to help fix it, but a complete waste of time to end users.
I've tried some openGL benchmarks such as FurMark, TessMark and GPUTest.
GPUTest crashes as soon as you click the button to start the test. TessMark doesn't even open (I guess it crashes immediately at startup)
FurMark creates a black window (where you're supposed to see an animated 3D scene). If you drag the window around, for each new mouse movement a new frame is rendered which you can see for a fraction of a second, then it's all black again.
Other programs that use graphics systematically crash, e.g. Max/Jitter.
Change History (2)
comment:1 by , 10 years ago
priority: | critical → major |
---|---|
Summary: | Experimental WDDM driver is completely broken, not even remotely usable → GPU tests don't work with WDDM driver |
comment:2 by , 8 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
You did a bold statement here but actually it's not that easy as you think. The reason for the crashes you see is not necessarily the WDDM driver but it might be also your host 3D graphics environment. For example, Intel 3D graphics drivers on Linux are known to cause many trouble. There are many users for which the WDDM guest driver work so I don't think that is completely broken is appropriate here.
Also it would be helpful if you would provide a bit more information. The bare minimum on information we expect is a VBox.log file of such a VM session.