Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Voting for the Unity Awards are OPEN! We’re looking to celebrate creators across games, industry, film, and many more categories. Cast your vote now for all categories
    Dismiss Notice
  3. Dismiss Notice

Bug Several serious issues

Discussion in 'Linux' started by gBraca, Jun 29, 2018.

  1. gBraca

    gBraca

    Joined:
    Jun 29, 2018
    Posts:
    8
    Greetings.

    I'm writing to ask about two main issues we've been having with Unity while developing a project.

    First and foremost, Unity was used on Linux (two with Debian 9 & one with Linux Mint 17) with version 2018.2.0b5. I'd be lying if I said there weren't problems, such as random crashes, incompatibilities between laptops with the same version of Unity and OS, &c.

    Issue #1:
    When opening a project made with the same version of Unity on a different computer (both with Debian 9), within seconds, all assets used in the game turned white (as in "textureless"). I tried all suggestions I found on the Internet; but to no avail. It was as if the textures weren't even in the project, even though they were according to the other laptop. The main difference between both laptops was that one had a dedicated GPU and the other didn't; while the one with the issue was the one that did have one.
    Unfortunately, I had to continue the project on a lower end laptop, with everything that it implies.

    1) Is there any way to avoid the textures problem, or is there something I might be missing here?

    Issue #2:
    Upon learning I was using a beta version of Unity, I tried installing a stable version on the laptop with the problem. Here's a first question:

    2a) How does one uninstall Unity?

    This might sound noobish; but the program is not installed through a package manager but through an assistan that seems to download/copy/paste files. I couldn't find information about it on / nor /home. This is crucial to ensure a proper fresh, new installation.

    Then, trying to bring the project from version 2018.2.0b5 to 2018.1.5f1, I can see almost nothing of what I had built on the Scenes in version 2018.2.0b5. It doesn't matter if I 'reimport all', or add each asset individually, &c. So far I wasn't able to find a solution and, if I can't, I'll have to consider migrating the project to a different tool, since it's hard to work with random crashes, runtime crashes, or freezes during the loading screen. Not to mention performance issues.

    To sum up:
    2b) Is there a way to properly migrate a project made in version 2018.2.0b5 to version 2018.1.5f1 (or any stable version)?

    Suggestion: it'd be convenient if it was clearly indicated which Linux versions are stable and which are on beta, unless there is no stable version on Linux. Figure having to migrate a project to another tool (with all it implies) for not being able to solve these problems.

    Thank you for your time.
     
  2. DominoM

    DominoM

    Joined:
    Nov 24, 2016
    Posts:
    460
    2017.4.4f1 is the current version to use for stability. 2018 shouldn't be considered stable until 2018.4.x