Search Unity

Running Unity in VirtualBox

Discussion in 'Editor & General Support' started by iwillbenice, Sep 2, 2018.

  1. iwillbenice

    iwillbenice

    Joined:
    Jun 7, 2013
    Posts:
    22
    Hi guys, I installed Unity2018.2.6f1 on guest VM Windows 7 sp1, Ultimate.

    On guest OS:
    I installed VirtualBox GuestAdditions
    Enabled 3d acceleration and 2d video acceleration
    Gave 2 virtual CPU cores to VM.
    Gave 4 GB RAM to VM.
    Gave 256 MB VRAM to VM.

    I'm trying to make it run on my laptop:

    Dell Latitude E6540
    Intel Core i5-4200M CPU @ 2.5GHz (2 physical, 4 virtual CPUs)
    12 GB DDR3L RAM
    Intel HD Graphics 4600 integrated graphic card with 1GB VRAM

    I am runningsame Windows 7 sp1, Ultimate as host OS.

    Reason i'm doing this is I want to have Linux as host OS and Unity for Linux is beta and not so stable, so I wanted to try this first instead of dual boot.

    Take a look at attached screenshot to see what I get when I start Unity.
    Editor.log is also attached to post.
    Also another screenshot showing that I can open build window.

    I think that main problem is in this:

    ```
    Assertion failed on expression: 'SUCCEEDED(hr)'
    (Filename: C:\buildslave\unity\build\Runtime/GfxDevice/d3d11/D3D11Window.cpp Line: 73)

    d3d11: swap chain: w=688 h=291 fmt=28
    d3d11: failed to create swap chain [0x887a0001]
    ```

    yet not sure and can't find anything about this online.

    Thing is that Unity actually works (at least some of it) and not renders. I can open build settings and hit build button (see screenshot).

    Can anyone help me? It seems like I need something to configure with graphics, but i'm not sure is it possible in VM at all?

    I plan to run small projects on it with simple 2d graphics, without postprocessing or any fancy stuff, so I think I won't need much of GPU power at all so I thought to try with VM.

    Thanks
     

    Attached Files:

    ivitz likes this.
  2. turbanov

    turbanov

    Joined:
    Dec 22, 2014
    Posts:
    59
    Try using a -force-glcore switch.
     
  3. ivitz

    ivitz

    Joined:
    May 1, 2017
    Posts:
    2
    I have the exact same issue. Did you find the solution?