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

A couple of differences/issues in 2018.1

Discussion in 'Editor & General Support' started by dgoyette, Jun 15, 2018.

  1. dgoyette

    dgoyette

    Joined:
    Jul 1, 2016
    Posts:
    4,113
    After upgrading from Unity 2017.4 to 2018.1, there are a couple of small things that are different. Curious if I should consider these bugs, merely changes, or things I can change with settings.
    • When pressing Ctrl-P to enter play mode, Unity no longer gives any visual indication that it's starting Play mode. In 2017.4, the Play button would immediately look like it was pressed, so I knew that Unity had received my request to play. A second or two later, the game would play. Under 2018.1, however, pressing Ctrl-P causes no visual change until the game is really in play mode. This has caused me to think that I just didn't hit Ctrl-P properly.
    • At the bottom right corner, I almost constantly have an empty light baking progress bar, even when no lighting is being baked, and when Auto Generate lighting is off. This just sound more like a bug...
    • Under 2017.4, I could write the following into a script: `StartCoroutine(MyRoutine())`; If MyRoutine didn't exist, intellisense would prompt me to create the method, and would properly create MyRoutine with a return type of IEnumerator. Under 2018.1, the method it creates is of type String instead.
    Anyone have a sense of whether each of these is a bug I should report, or whether some of these can be resolved through some settings changes?
     
  2. dgoyette

    dgoyette

    Joined:
    Jul 1, 2016
    Posts:
    4,113
    Looks like this is fixed in 2018.1.5.