Search Issue Tracker
Fixed
Fixed in 6000.5.0a6
Under Consideration for 6000.4.X
Votes
0
Found in
6000.4.0b5
6000.5.0a5
Issue ID
UUM-131716
Regression
No
Obsolete warning for Converters.RunInBatchMode is confusing and lacks clarity
Reproduction Steps:
- Install Unity 6.5 alpha (version 6.5.0a1 or newer).
- In a script or tooling code, call the method {{{}Converters.RunInBatchMode(...){}}}.
- Observe the compiler warning (CS0618) and the associated message in the Console.
Actual Result:
The method is marked as obsolete with a warning message stating it will be removed and that one should "use the UI". The message is abrupt, does not explain the technical rationale, and causes concern for users who rely on this API for automated import pipelines and custom tooling. The warning implies there is no programmatic alternative.
Expected Result:
The API should be kept, and instead showing a console warning. It should clearly communicate the technical reason for why UI is a better approach. (e.g., the API's unpredictable behavior) and offer clearer guidance. The recommended phrasing is:
{{"Using this API can lead to incomplete or unpredictable conversion outcomes. For reliable results, please perform the conversion via the dedicated window: {}Window > Rendering > Render Pipeline Converter.{}"}}
Reproducible in Versions:
Unity 6.4 and above
Additional Context:
https://discussions.unity.com/t/planned-breaking-changes-in-unity-6-5/1694205/35
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
- 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
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
Resolution Note:
Fixed in 6000.5.0a6
Resolution Note (fix version 6000.5.0a6):
Fixed in 6000.5.0a6