VersionSectionRiskImpactNote
6000.0.0b16Fixes
DX12
FixRemoving assert that was added accidentally "ReleaseDynamicVBOFrame: Expected node in client scratch release queue" in dx12. Explanation: This was a previous fix were ReleaseDynamimcVBOFrame: Unexpected frame kept spamming. This fix did not remove another assert "ReleaseDynamicVBOFrame: Expected node in client scratch release queue" which is now included in this change. The expectation is that dx12 should now not produce any TTY errors when opening / closing projects.
6000.0.0b15Fixes
DX12
FixRemoving assert that was added accidentally "ReleaseDynamicVBOFrame: Expected node in client scratch release queue" in dx12. Explanation: This was a previous fix were ReleaseDynamimcVBOFrame: Unexpected frame kept spamming. This fix did not remove another assert "ReleaseDynamicVBOFrame: Expected node in client scratch release queue" which is now included in this change. The expectation is that dx12 should now not produce any TTY errors when opening / closing projects.
6000.0.0b13Fixes
DX12
FixRemoving assert that was added accidentally "ReleaseDynamicVBOFrame: Expected node in client scratch release queue" in dx12. Explanation: This was a previous fix were ReleaseDynamimcVBOFrame: Unexpected frame kept spamming. This fix did not remove another assert "ReleaseDynamicVBOFrame: Expected node in client scratch release queue" which is now included in this change. The expectation is that dx12 should now not produce any TTY errors when opening / closing projects.
6000.0.0b12Fixes
DX12
FixRemoving assert that was added accidentally "ReleaseDynamicVBOFrame: Expected node in client scratch release queue" in dx12. Explanation: This was a previous fix were ReleaseDynamimcVBOFrame: Unexpected frame kept spamming. This fix did not remove another assert "ReleaseDynamicVBOFrame: Expected node in client scratch release queue" which is now included in this change. The expectation is that dx12 should now not produce any TTY errors when opening / closing projects.
6000.0.0b11Fixes
DX12
FixRemoving assert that was added accidentally "ReleaseDynamicVBOFrame: Expected node in client scratch release queue" in dx12. Explanation: This was a previous fix were ReleaseDynamimcVBOFrame: Unexpected frame kept spamming. This fix did not remove another assert "ReleaseDynamicVBOFrame: Expected node in client scratch release queue" which is now included in this change. The expectation is that dx12 should now not produce any TTY errors when opening / closing projects.

Pick your Unity version

Unity Releases compares releases against the version your project is on. Picking it now keeps Compare versions focused on what changes between where you are and where you might be going.