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. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice
  4. Dismiss Notice

Resolved I hope I'm in the right category.. Getting errors after a build

Discussion in 'Editor & General Support' started by DragonFhangDev, May 30, 2021.

  1. DragonFhangDev

    DragonFhangDev

    Joined:
    Oct 22, 2019
    Posts:
    32
    Hey guys. So I have no idea what's going on and I'm trying to do some research on the issues I'm seeing. I'm getting a lot of different answers but not sure what exactly to do but it looks like a GUI issue maybe?

    I'm on version 2020.3.10f1 LTS
    I've attached the image with the issues I'm experiencing.

     
  2. Kurt-Dekker

    Kurt-Dekker

    Joined:
    Mar 16, 2013
    Posts:
    36,780
    That filepath looks suspicious to me, like it might have illegal filename characters that some part of the tools can't handle.

    It looks like perhaps it was originally done as "Garrison: A Mercenary's Story" and I know the colon :)) character won't work...

    Make an empty project, put one scene in it, add it to build settings, build that, make sure that works first.
     
  3. DragonFhangDev

    DragonFhangDev

    Joined:
    Oct 22, 2019
    Posts:
    32

    That is interesting as I've done the builds just fine before updating to 2020. I used to be on 2019's LTS, I'll give your suggestion a shot real quick though.
     
  4. DragonFhangDev

    DragonFhangDev

    Joined:
    Oct 22, 2019
    Posts:
    32
    Well I'll be damned...... It was one little character that messed me up for 48 hours. It's all fixed up and everything works now. Weird how that update from 2019 to 2020 messed that up.

    Thank you Kurt, I honestly never would have guessed that was the issue.
     
  5. Kurt-Dekker

    Kurt-Dekker

    Joined:
    Mar 16, 2013
    Posts:
    36,780
    Interesting... glad to hear that you're back on track.

    Generally file and path names should be as "sanitized" as possible: nothing but alphanumerics really (letters and numbers). Ideally not even spaces. Spaces cause a whole host of other shell-related subprocess problems.

    In an ideal world any UTF-8 character can be used for any purpose at all. In practice, there may be dozens or hundreds of pieces of middleware used for any piece of complex software (such as Unity and all the build tools), and if even one of those stumbles on a bad character, BOOM, we're dead in the water.