Unity

What's new in this version:

Fixed:
- Android: Fixed rendering artifacts when using HDR rendering with MSAA on sold Mali Bifrost GPUs
- Asset Pipeline: The Assembly version is no longer included in the script type hashes that was used for script type dependencies
- Build Pipeline: During Player build, the progress bar would display the message "Bunding and compressing data", which contains a typo. This has been fixed to read "Bundling and compressing data"
- Burst: Fixed a crash when a call to System.Diagnostics.Debugger.Break from a Burst-compiled job or function pointer was called without a debugger attached
- DX12: Fixed GPU hang due to corrupt SRV
- Editor: Fixed an issue with the progress bar on windows when user code drives it in "non-modal" way
- Editor: Fixed crash in some progress bar scenarios that resulted in recursive repaints (e.g. after turning on raytracing support in HDRP
- GI: Fixed an issue of a missing occlusion when baking LODs with the CPU lightmapper
- GI: Make the default skybox probe and ambient probe automatically baked until a first manual bake is done
- Graphics: Fixed a Severe one frame Motion blur artifacts issue that occurred on editing of blend shapes
- Graphics: Fixed an incorrect GeometryJob Fence initialisation that caused graphical corruption in UI canvas rendering
- Graphics: Fixed an issue where ComputeShader.SetConstantBuffer caused a freeze
- IL2CPP: Emit compilable C++ code for C# string literals containing the "//" character sequence
- IL2CPP: Ensure that FieldInfo objects for the same base class field from two different derived types do not match
- IL2CPP: Fixed an incorrect behavior of asynchronous file stream reads
- IL2CPP: Fixed an issue with re-throwing an exception from a catch that includes a nested try/catch block
- iOS: Fixed an issue where UnityWebRequest sometimes got stuck on iOS 14.2+ when using ARFoundation
- Kernel: Fixed random crash while executing TLSAllocator::FrameMaintenance
- Linux: Automatically install toolchain for building Linux IL2CPP players when Linux IL2CPP component present
- Package: Fixed an issue where Burst would erroneously error on BurstCompile.CompileFunctionPointer calls when building for the DOTS Runtime
- Package: Fixed an issue where clang segmentation fault on iOS when member function debug information were emitted, it is disabled for this platform now
- Package: Fixed an issue where explicitly casting from an int to IntPtr would not sign extend the value
- Package: Fixed DOTS Runtime JobProducer Bursting code to support JobProducers with multiple generic arguments, complex job wrapper and generic jobs
- Package: Fixed managed implementations of blend_epi32 and mm256_blend_epi32 intrinsics on Mono
- Package: Intrinsics: Neon - fixed vget_low and vget_high producing suboptimal code
- Package Manager: Fixed an issue where users cannot use downloaded filter for the My Assets tab in Package Manager UI
- Particles: Fixed an issue where Rate over Distance emission sets particle ages correctly
- Profiler: Fixed an issue with sending enable/disable recording messages to connected players, where the player would not respond to the message correctly
- Scripting: Fixed an issue where Response files list (csc.rsp) was not passed up to external compilers
- Serialization: Fixed a crash when opening the Preset window on an object containing SerializeReference with instances accessible from multiple property path
- Shaders: Fixed an issue where the Shader compiler did not handles CR line endings
- Shaders: Fixed an issue where the Shader compiler would generate calls to bitfieldExtract when building for OpenGL ES 3 or WebGL 2
- Shaders: Fixed incorrect code being generated for GATHER_PO instruction on Vulkan
- Text: Fixed an issue where changes to TextMesh.color could be rendered a frame too early
- UI: Fixed an issue where if a aspectRatioFitter has a parent assigned afterwards the cached parent wouldn't update properly
- UI Toolkit: Binding operations are done asynchronously to improve performance and avoid editor lockup
- UI Toolkit: Fixed an issue where Right-click context menu on properties would not show on every bound field
- UI Toolkit: Fixed an issue where UQuery: Query<VisualElement> would not correctly returns all elements
- UI Toolkit: Fixed an issue with Focus() method on TextField controls
- UI Toolkit: Fixed Element not visible after being hidden/shown in a specific sequence issue
- UI Toolkit: Fixed missing icons when the atlas render texture was destroyed by the engine
- UI Toolkit: Fixed wrong addressing of dynamic transforms issue when new atlas slot is used
- Video: Fixed an issue where the VideoPlayer.frameReady was not invoked for some frames
- Video: [MacOS] Fixed an issue where UrlSource streaming stuttered in Video Player
- XR: Fixed a deadlock when Windows player is invisible with VR enabled
- XR: Updated the verified AR Foundation related packages to 4.0.10. Please see the AR Foundation package changelog for details

API Changes:
- GI: Added: Added two new callbacks: LightProbes.needsRetetrahedralization which is called whenever the current registered probes and tetrahedralization are out of sync, and LightProbes.tetrahedralizationCompleted which fires after (re-)tetrahedralization is done.
- UI Toolkit: Changed: ChangeEvent are now called on bound field when value is first set on the control and matches default value

Changes:
- Graphics: Update SRP packages to 10.3.1 (1300426)
- Package Manager: Update com.unity.purchasing to 2.2.2
- Timeline: Updated Timeline package to version 1.4.6

Improvements:
- Package: Update ProBuilder to 4.5.0.
- Package: Upgrading input system package to 1.0.2
- Scripting: Added support for Unity Version Defines in Assembly definition import options
- This feature improvement allows scripts to easily specify different code snippets for different unity version ranges. This is especially useful for introducing calls to newly added public APIs, in which case these API calls needs to be guarded by defines based on a unity version range of a given unity version or later.
- Unity version range expression syntax is the same as package version range expressions. Unity version format differs from package version format, thus Unity version expressions are evaluated based on some rules specific to the Unity version format:
- Comparison of release types follows the following rules: a<b<f=c<p<x. So eg. an alpha version is always smaller (earlier) than a beta version, regardless of the Incremental version.
- The unity versions are allowed to have suffixes (e.g 2020.1.3-bonfire) which are ignored by the unity version comparison code
- Chinese releases are equivalent to public releases (f) so for the sake of comparison in the version range expression 2020.1f3 would be equal to 2020.1c3[
- experimental releases don't include an Incremental Version - e.g. everything after 2020.2.1x would be treated as suffix and ignored by the version comparison.
- Scripting: Improved code readability and naming consistency with the Unity 2021.2 and 2021.1 codebase
- Shaders: Shaders can now use UNITY_PLATFORM_<PLATFORM_NAME> defines to specialize compilation per build target platform (examples: UNITY_PLATFORM_OSX, UNITY_PLATFORM_WINDOWS).