Search Issue Tracker

Fixed in 2018.3.X

Votes

0

Found in

2018.3.0a7

2018.3.0a8

Issue ID

1068870

Regression

Yes

Null reference exception on tweaking the pre muscle settings of a avatar when scene view is in focus

Themes

-

Null reference exception on tweaking the pre-muscle settings of an avatar when scene view is in focus.

Steps To Reproduce:

1. Open the attached Project.
2. Project > Mean Looking Troll > Mean Looking TrollAvatar
3. Inspector > Configure Avatar
4. Muscle & Settings > Pre-Muscle Settings.
5. Change the slider value of any body part.
6. Change the additional Settings and hit 'Apply'.

Actual Result:
1. Tweaking the slider in pre-Muscle setting throws Nulle reference and GUI error.
2. Changing additional settings and applying throws "EndLayoutGroup" error.

Note: Make sure that the scene view is in focus.

Reproducible On:
2018.3.0a8, 2018.3.0a7

Not Reproducible On:
2018.3.0a6

Environment:
Occurs On windows and Mac.

Comments (6)

  1. dagerob

    Mar 12, 2019 23:50

    I still have this bug on Windows 2018.3.3f1

  2. irenya

    Dec 30, 2018 22:23

    Had exactly the same problem running 2018.3.0f2 both on Mac and Windows.
    I can change everything in the muscle group preview area and there aren't any errors.
    As soon as I drag any slider in the per-muscle settings, i get the error mentioned above and cannot move around in the scene anymore. There's also a second error:
    "GUI Error: You are pushing more GUIClips than you are popping. Make sure they are balanced.
    UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr) "
    This one appears once every two of the other type.
    Incidentally (not sure if this is related), while in the muscle group preview the scene is fully dark, as soon as i drag a slider in the per-muscle one, the scene shows the default grid and looks brighter. Game view always look the same.

  3. andrejpetelin

    Dec 30, 2018 22:16

    I got the exact same bug in 2018.3.0f2 on Windows.

  4. andrejpetelin

    Dec 30, 2018 22:16

    I got the exact same bug in 2018.3.0f2 on Windows, so not alpha or beta.

  5. andrejpetelin

    Dec 30, 2018 22:16

    I got the exact same bug in 2018.3.0f2 on Windows, so not alpha or beta.

  6. andrejpetelin

    Dec 30, 2018 22:16

    I got the exact same bug in 2018.3.0f2 on Windows, so not alpha or beta.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.