- Scripting Backend - Non active build profile should check its player settings scripting backend and not global one to display warning

Unity: Build Settings Window

Player Settings

Common

Configuration

Fixed

6.0.X

Won't Fix

6.1.X

Fix already landed in 6000.0

Fixed the bug where build profiles that show a warning in their settings UI based on the scripting backend were using a method that retrieved the project settings player settings value, instead of the build profile player setting value.

Steps to reproduce:

1. Open File > Build Profiles

2. Create two build profiles and player settings to them (press Customize Player Settings)

3. Change the scripting backend to IL2CPP (make sure it's not installed) and then make the build profile active. Make sure the other one is set to Mono

Actual results: All build profiles will show the script backend warning in the UI, even though one of them is set to Mono

Expected results: Each build profile should show the warning depending on it's player settings value

- Scripting Backend - Non active build profile should check its player settings scripting backend and not global one to display warning

Unity: Build Settings Window

Fixed

Won't Fix

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

- Scripting Backend - Non active build profile should check its player settings scripting backend and not global one to display warning

Unity: Build Settings Window

Statuses

Fixed

Won't Fix

Resolution Notes

6.1.XWon't FixFix already landed in 6000.0

6.0.XFixedFixed the bug where build profiles that show a warning in their settings UI based on the scripting backend were using a method that retrieved the project settings player settings value, instead of the build profile player setting value.

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?