Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: VirtualBox Gets Accelerated Direct3D Support

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    14,594

    Default VirtualBox Gets Accelerated Direct3D Support

    Phoronix: VirtualBox Gets Accelerated Direct3D Support

    Last month VirtualBox 2.1 was released with several interesting changes and among them was support for OpenGL. With this latest open-source virtualization software from Sun Microsystems, it became possible to run some OpenGL programs within a guest virtual machine while allowing the host system's graphics card to accelerate the drawing...

    http://www.phoronix.com/vr.php?view=NzAyNA

  2. #2
    Join Date
    Sep 2008
    Posts
    113

    Default

    Of course the performance is going to be poor, but look at this way: WineD3D can only get better, and it's the only factor in getting your games to run!
    Does a game have a problem with the .net framework, or steam, or copy protection or some other stupid thing? Well since it's running natively in windows, that won't be an issue anymore!

    You're not going to be able to play Crysis without a beast of a machine, but at least I can play Age of Empires 2.

  3. #3
    Join Date
    Dec 2008
    Posts
    985

    Default

    Quote Originally Posted by superppl View Post
    Does a game have a problem with the .net framework, or steam, or copy protection or some other stupid thing? Well since it's running natively in windows, that won't be an issue anymore!
    Exactly, this is a very interesting development.

  4. #4
    Join Date
    Aug 2008
    Location
    California, USA
    Posts
    196

    Default

    YEAH!!! Now you guys think this will actually release?

    *COUGH* Unlike XServer 1.6 *COUGH*

  5. #5
    Join Date
    Jan 2007
    Location
    Au
    Posts
    174

    Default

    I'm more interested by the fact that virtualbox decided to pick up wine as their direct3d implementation - hopefully it means wine gets more developers from Sun/Innotek working on d3d.

  6. #6
    Join Date
    Jan 2009
    Posts
    3

    Default

    Quote Originally Posted by hmmm View Post
    I'm more interested by the fact that virtualbox decided to pick up wine as their direct3d implementation - hopefully it means wine gets more developers from Sun/Innotek working on d3d.
    I think it will mean big things for Wined3d if Sun gets involved with that. I believe thats a area where Wine could use more help, but I guess they could use help in anyway they can get.

  7. #7
    Join Date
    May 2008
    Location
    Germany/NRW
    Posts
    510

    Default

    IMHO this does nothing but in some rare cases (when anything except wine's direct3d-implementation keep a game from working with wine) remove the need to reboot to play a game. And you still need a windows-license. I don't see what's so exciting here.

    I'm more interested by the fact that virtualbox decided to pick up wine as their direct3d implementation - hopefully it means wine gets more developers from Sun/Innotek working on d3d.
    Yep, that'd be a nice thing.

  8. #8
    Join Date
    Sep 2008
    Posts
    113

    Default

    Well, Parallels is also using WineD3D, but it doesn't look like they contributed anything back. But this could be different since the Virtual Box devs actually work with the open source community.

  9. #9
    Join Date
    Jun 2008
    Location
    Perth, Scotland
    Posts
    435

    Default

    Excellent!! I've been waiting for this for ages and it's now more important for me than ever because my desktop is now also a server and a router, meaning I can't reboot into Windows without cutting everything off.

  10. #10

    Default

    I would recommend to use Wine for gaming and not to use VirtualBox. Their opengl driver will never perform (the same for a real d3d driver) as well as a native OpenGL driver and for that reason D3D performance will be (a lot) lower than Wine's, so just use Wine.

    One of the reason for the lack of OpenGL performance has to do with VirtualBox being a virtual machine. They want all opengl commands to pass through their own opengl layer and cache them in order to allow you to resume programs. If they directly passed all data to native opengl they would be able to reach more performance. This is also the reason why adding new opengl extensions is tricky (in case of GLX not all new extensions like glsl have a glx protocol if they are directly using GLX).

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •