Search Unity

During Play Testing In Editor

Discussion in 'Linux' started by boxhallowed, Jan 30, 2016.

  1. boxhallowed

    boxhallowed

    Joined:
    Mar 31, 2015
    Posts:
    513
    This is what happens when I click the play button in the tester for Unity on my Linux Mint 17.2 (updated) machine. All dependencies are at recommended. Just updated to latest, 5.3.1f1, still happening. Looks a little better than post 2 though.

    OpenGL Grep:
    OpenGL version string: 4.5.0 NVIDIA 352.63


    Import Info:
    System: Host: #####-KGP-M-E-D16
    Kernel: 3.16.0-38-generic x86_64 (64 bit, gcc: 4.8.2)
    Desktop: Xfce 4.12.2 (Gtk 2.24.23)
    Distro: Linux Mint 17.2 Rafaela
    Machine: Mobo: ASUSTeK
    model: KGP(M)E-D16
    version: Rev 1.xxG
    Bios: American Megatrends
    version: 3201 date: 02/19/2013
    CPU(s): 2 Quad core AMD Opteron 6212s (-MCP-SMP-)
    cache: 16384 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm)
    bmips: 41602.4
    Clock Speeds: 1: 1400.00 MHz 2: 1400.00 MHz 3: 1400.00 MHz 4: 2600.00 MHz 5: 1400.00 MHz 6: 1400.00 MHz 7: 1400.00 MHz 8: 1400.00 MHz 9: 1400.00 MHz 10: 1400.00 MHz 11: 1400.00 MHz 12: 2600.00 MHz 13: 1400.00 MHz 14: 1400.00 MHz 15: 1400.00 MHz 16: 2600.00 MHz
    Graphics: Card-1: ASPEED ASPEED Graphics Family (not in use)
    bus-ID: 01:01.0
    Card-2: NVIDIA GK104 [GeForce GTX 770] bus-ID: 04:00.0
    X.Org: 1.15.1
    drivers: nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 1600x900@60.0hz, 1600x900@60.0hz
    GLX Renderer: GeForce GTX 770/PCIe/SSE2 GLX
    Version: 4.5.0 NVIDIA 352.63
    Direct Rendering: Yes
    Audio: Card-1: Creative Labs CA0106 Soundblaster
    driver: snd_ca0106 port: bc00 bus-ID: 01:03.0
    Card-2: NVIDIA GK104 HDMI Audio Controller driver: snd_hda_intel
    bus-ID: 04:00.1
    Sound: Advanced Linux Sound Architecture ver: k3.16.0-38-generic
    Network: Card-1: Intel 82574L Gigabit Network Connection
    driver: e1000e ver: 2.3.2-k port: cc00 bus-ID: 02:00.0
    IF: eth1 state: down mac: <filter>
    Card-2: Intel 82574L Gigabit Network Connection
    driver: e1000e ver: 2.3.2-k port: dc00 bus-ID: 03:00.0
    IF: eth0 state: down mac: <filter>
    Drives: HDD Total Size: 2240.5GB (44.8% used) 1: id: /dev/sda model: WDC_WD5001AALS size: 500.1GB
    2: id: /dev/sdb model: WDC_WD10EZEX size: 1000.2GB 3: id: /dev/sdc model: WDC_WD5000AVVS size: 500.1GB
    4: id: /dev/sdd model: KINGSTON_SV300S3 size: 240.1GB
    Partition: ID: /
    size: 197G used: 23G (13%) fs: ext4 ID: swap-1 size: 25.75GB used: 0.00GB (0%) fs: swap
    RAID: No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
    Sensors: System Temperatures: cpu: 16.6C mobo: N/A gpu: 0.0:49C
    Fan Speeds (in rpm): cpu: N/A
    Info:
    Processes: 402 Uptime: 2 days Memory: 4106.7/24093.8MB Runlevel: 2 Gcc sys: 4.8.4
    Client: Shell (bash 4.3.11) inxi: 1.9.17


    wtf.png
     
    Last edited: Jan 31, 2016
  2. boxhallowed

    boxhallowed

    Joined:
    Mar 31, 2015
    Posts:
    513
    Updating to 5.3.1f1 seemed to help a bit, but I still have the issue. Screenshot_2016-01-30_20-11-52.png
     
  3. boxhallowed

    boxhallowed

    Joined:
    Mar 31, 2015
    Posts:
    513
    I think this has something to do with viewport rendering. When I click and drag where the game button should be, it still seems to be there. The mouse offset in that panel is also wrong for what is shown on the screen when this happens.
    Screenshot_2016-01-30_20-17-08.png
     
  4. boxhallowed

    boxhallowed

    Joined:
    Mar 31, 2015
    Posts:
    513
    Alright, so the first image here is before testing play. I undocked the "game" tab to see if the behaviour continued. It did, as you can see in the next image. Note, how it does not happen in the "scene" tab.

    Screenshot_2016-01-30_20-38-16.png

    Screenshot_2016-01-30_20-39-32.png
     
  5. boxhallowed

    boxhallowed

    Joined:
    Mar 31, 2015
    Posts:
    513
    This will be the last post, sorry for the verbose and numerous post. I just want to seperate the information here. Can anyone confirm if this is happening with KDE, GNOME, or Cinnamon? I am using XFCE and I expect it is the culprit.
     
  6. LukaKotar

    LukaKotar

    Joined:
    Sep 25, 2011
    Posts:
    394
    Did you try selecting a different layout (top right)? What happens if you check "maximize on play" in the game view?

    Edit: I'm not having such problems (Ubuntu 15.10).
     
  7. boxhallowed

    boxhallowed

    Joined:
    Mar 31, 2015
    Posts:
    513
    The first image is a layout switch, the second is "maximize". Luckily! The maximize one seems to work. So I will ride along with that for a while. I would still love a confirmation of UI though.

    layout.png fullscreen.png
     
  8. boxhallowed

    boxhallowed

    Joined:
    Mar 31, 2015
    Posts:
    513
    What is your UI though? I am using XFCE, are you using GNOME, KDE, Cinnamon, ICWM (I kid :p). Also, another interesting note. The first image here is normal on the room I am testing, the second image is after I switch to another scene/room during test play. Now, I know switching rooms isn't recommended anyhow, but it is something that works on Windows, but doesn't work here.

    Screenshot_2016-01-30_21-24-05.png
    Screenshot_2016-01-30_21-24-22.png
     
  9. LukaKotar

    LukaKotar

    Joined:
    Sep 25, 2011
    Posts:
    394
    I use the Unity desktop environment (default in Ubuntu).
     
  10. boxhallowed

    boxhallowed

    Joined:
    Mar 31, 2015
    Posts:
    513
    Ah, I am using Linux Mint with XFCE. So I am going to chalk it up to that. Do any devs here have any idea if they would be so kind as to give XFCE a little love?
     
  11. FuzzyQuills

    FuzzyQuills

    Joined:
    Jun 8, 2013
    Posts:
    2,871
    Strange... I don't have such a bug, and I use XFCE. (Well, XFCE with mainstream Ubuntu 15.10)

    EDIT: Oh yea, that game is SO SMASH BROS. :p
     
    Last edited: Feb 2, 2016
  12. LukaKotar

    LukaKotar

    Joined:
    Sep 25, 2011
    Posts:
    394
    I just encountered this problem myself, it seems to be caused by trying to set resolution through code (using Screen.SetResolution()). I'm pretty sure this is ignored in editor on Mac and Windows. In any case, you can prevent it from running in the editor using platform defines:
    Code (CSharp):
    1. #if !UNITY_EDITOR
    2.     Screen.SetResolution(x, y, fullscreen);
    3. #endif
     
  13. Tak

    Tak

    Joined:
    Mar 8, 2010
    Posts:
    1,001
    Hm, we'll look into this.