Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.1.0b10
Issue ID
1011754
Regression
No
IL2CPP for Windows Standalone Development Build runs unexpectedly slow with Script Debugging turned on
Reproduction steps:
1. Open the attached project "VehicleToolsIL2CPPTest.zip";
2. Go to Player Settings;
3. Change Scripting Backend to Mono;
4. Open the Profiler window;
5. Open the Build Settings;
6. Make sure Development Build and Script Debugging both are still enabled on Build settings;
7. Select Build and Run;
8. Observe the results in the Profiler window.
Expected results: test with IL2CPP should give the same time in the GraphicsOverlay.Update() as with the Mono backend - about 3ms.
Actual results: GraphicsOverlay.Update() reaches ~100 or more ms (especially if you try to move the car in the game).
Reproduced on: 2018.1.0b10, 2018.1.0b11, 2018.2.0a5.
Note: Didn't test on lower versions than 2018.1.0b10, as IL2CPP Managed Debugger for Standalone Players was released only in this version.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Audio Mixer does not change volume when lowering volume on an Audio Mixer loaded from AssetBundles
- Error “Value cannot be null. Parameter name: key UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)” thrown and Addressables build fails when "Include in Build" is disabled and using Addressables For Android package
- “error CS0433: The type 'CodeBinaryOperatorType' exists in both 'System.CodeDom and 'System" compilation errors are thrown when opening a specific project
- Metal Vertex Shader warning is being thrown when creating a VR Template Project
- Asset database warning is thrown when declaring font variable in the USS text file
Add comment