Search Issue Tracker
Fixed
Fixed in 1.13.1
Votes
0
Found in [Package]
1.13.0
Issue ID
ISXB-1430
Regression
Yes
Build profiles cause Editor to be stuck in infinite restart loop when input type is old and global is New or Both
{}Steps to Reproduce{}: # On a project where the Input System is set to {}Both{}, create a new build profile (I’ve tested with Web and Facebook Instant Games as targets). Set the Input System to {}Old{}.
- The editor will prompt you to restart, and show a warning window saying that your project is using the new input system but the player settings is set to the old input system, and ask if you want to restart and swap back to using {}Both{}.
Actual results:
Clicking Yes restarts the editor but triggers the warning to come up again, which causes an infinite loop until the user presses No or force quits Unity. This error only occurs with build profiles and not when changing the global project settings.
Expected results:
Clicking Yes will restart the editor and set the player settings back to Both
*See attached Google Drive links for videos of expected and actual behavior.
Reproducible with versions:* 6000.2.0a3
Not reproducible with versions: 6000.0.29f1, 6000.1.0a4
Can’t test with versions:
Tested on (OS): MacOS (ARM64)
Notes:
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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Resolution Note (fix version 1.13.1):
Fixed a problem with the logic to get the active player settings object that cause an infinit reimport loop.