Any Direct3D implementation on top of these Mesa drivers?

[cesss]

Installing your Mesa drivers in my Virtualbox VMs has greatly improved graphics compatibility. However, there's one application (Revit 2019) that won't use Mesa if Direct3D is not detected. It doesn't detect D3D, so it defaults to its own software renderer, but something strange happens because that renderer has become really slow (about 30 seconds per frame!!) after installing the Mesa drivers. I checked that all kinds of hardware acceleration are disabled for this VM. It runs Windows 7 64bit, latest service pack, and Virtualbox is 5.2.18.

Somehow, I have the feeling that if there was any Direct3D implementation that could be used on top of the Mesa drivers, then it would work fine... Is there any such implementation? Thanks!

[pal1000]

I only know about WineD3D which is incorporated in Virtualbox guest additions and doesn't do a very good job (#9). It may be woefully out-of-date. For D3D9 software rendering on Windows 7 I recommend Google Swiftshader.

[cesss]

I don't understand what's happening with my VM. On a Sierra host, the Revit built-in software gfx implementation works fine. On High Sierra, it renders a couple frames, gets stuck for 1 minute or so, and then it becomes responsible again. I thought it was because of installing the Mesa drivers, but it's not. There's something weird going on...

[cesss]

Very, very strange... the issue I'm experiencing in Virtualbox is related to the gfx window size, and it seems to affect both Windows and Linux hosts. It's like if the back buffer was too expensive to copy or something when the window size is big. Very strange. Of course this is not an issue in your drivers, but I'm surprised to face this... totally new to me.

[cesss]

Finally, it turns out that all the strange behavior I was getting is because of this bug in VirtualBox. I'm closing the issue, as it's unrelated to the Mesa drivers.