Search Issue Tracker
By Design
Votes
0
Found in
2020.2.0a8
2020.2.0a20
Issue ID
1267029
Regression
Yes
[Preset] Unity Remote properties are missing in the Preset of Editor Settings
When preset of "Editor Settings" is created from Project Settings window, "Unity Remote" properties are missing in the Preset, refer attache video
Steps to repro:
1. Create a new project
2. Edit > Project Settings > Editor
3. Create preset of Editor Settings
4. Project window > EditorSetttings preset > Select
Actual Result:
Unity Remote properties are missing in the Preset of Editor Settings
Expected Result:
Unity Remote Properties should be available in the preset of Editor Settings
Occurring on:
2020.2.0a20, 2020.2.0a8
Working fine:
2020.2.0a7, 2020.1.1f1
Environment:
Windows10 and macOS 10.15
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on CheckGameObjectsAndAddMissingRequiredComponents when opening a specific project
- Batch Mode and Cloud Build get stuck at 'Scanning for ADB Devices' when building for the Android or iOS platforms
- HDRP LightLateUpdate allocates every frame for each light in the scene when in Play Mode
- [IL2CPP] Custom attribute on delegate return value not present in IL2CPP builds
- Unexpected transformations occur when executing 2D Vertex Shaders
Resolution Note (2020.2.9f1):
Editor Settings are a strange beast. Part of the settings are global values (like Remote Unity values) that are persisted in C++ and not part of a SerializedObject. Par of the settings are a SerializedObject that can be copied and used as a preset.
When displaying the Editor Settings SettingsWindow we show all the settings: Global values and Serialized values.
When displaying the Editor Preset Settings we are NOT displaying the global values because ALL PRESETS would share the same values anyway.
Why did it seem to work with version 2020.2a7?
The UI would show the Unity Remote values but it wouldn't be modifying the preset data. It would be modifying the global values thus affecting the values of ALL presets. So in wasn't really working either :)