Search Issue Tracker
Fixed
Fixed in 6000.0.42f1, 6000.1.0b10, 6000.2.0a7, 7000.0.0a23
Votes
7
Found in
6000.0.40f1
6000.1.0b8
6000.2.0a5
Issue ID
UUM-98557
Regression
Yes
Different build sizes between Editor build and command-line build when "Static Batching" is enabled
Reproduction steps:
1. Open the attached "repro_IN-95316" project
2. Open the "Build Settings.../Build Profiles" window ("File -> Build Settings.../Build Profiles")
3. Build the project by pressing the "Build" button
4. Once the build completes, open the "Windows Terminal" and change the active path to the Editor path (to the same version that was used in the previous steps)
5. Build via command-line using this command: .\Unity.exe -projectPath $projectPath -quit -batchmode -buildTarget "win64" -buildWindows64Player $targetDestination -logFile $logFile
6. Once the build is completed, compare the sizes of both builds
Expected result: Both builds are of the same size
Actual result: Command-line build takes up more space (~1.34 GB) than the Editor build (~1.25 GB)
Reproducible with: 6000.0.40f1, 6000.1.0b8, 6000.2.0a5
Not reproducible with: 2022.3.59f1
Reproducible on: Windows 10 (22H2), Windows 11 (23H2) (user's)
Not reproducible on: No other environments tested
Notes:
- $projectPath is the full path to you Unity project folder (i.e. "C:\Projects\repro_IN-95316")
- $targetDestination is the full path, including the executable name, of where you want the build to be created (i.e. "C:\Projects\repro_IN-95316\Builds\CommandLineBuild\CommandLineBuildExecutable.exe")
- $logFile is the full path of where you want the build log to be saved (i.e. "C:\Projects\repro_IN-95316\Builds\CommandLineBuild\command_line_build_log.txt")
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Add comment