DirectX 3D Acceleration Problem

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
Tif
Posts: 3
Joined: 29. Sep 2013, 08:26

DirectX 3D Acceleration Problem

Post by Tif »

I'm a bit of a nostalgia buff. I've installed VirtualBox on my mac (OSX Mountain Lion) and found a way to install The Sims 2 (same version I used to play) and even figured out how to get the 3d acceleration to work. Here's the issue:

I have gotten the following error code upon trying to start up my game: "Direct3d returned an error: D3DERR_INVALIDCALL!! The application will now terminate."

Running dxdiag and testing the DirectX 3d acceleration gives only the following error: "Direct3D 7 test results: Failure at step 40 (Creating flipping primary surface with one back buffer): HRESULT = 0x88760064 (error code)" 8 and 9 work just fine.

Please help me! I've been working on trying to figure this out all night. :-/
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: DirectX 3D Acceleration Problem

Post by mpack »

Direct7 is not supported, only Direct8/9. Only Windows XP and later is supported (you don't say what you're using). I believe there's some experimental support for Direct10 for use in Win7 and later (Aero theme support).

For details see "Guest Additions | Hardware Accelerated Graphics" in the User Manual.
Tif
Posts: 3
Joined: 29. Sep 2013, 08:26

Re: DirectX 3D Acceleration Problem

Post by Tif »

Sorry, I'm running XP. Thought I included that.
Tif
Posts: 3
Joined: 29. Sep 2013, 08:26

Re: DirectX 3D Acceleration Problem

Post by Tif »

I just looked in the manual in the area you described, but it doesn't have any information that might help me.

Isn't there something I can do?
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: DirectX 3D Acceleration Problem

Post by mpack »

As I said, Direct7 is not supported, meaning there's no drivers written for it. So if your app can't use anything else then no, there's nothing you can do.
Post Reply