r/unrealengine
Last Week In Unreal: 963 commits on ue6-main; 172 on ue5-main | Epic made the UE5 global package version physically unextendable
- upvotes
- 39
- comments
- 8
Post
Highlighted: the lines this signal was extracted from
Epic has effectively frozen the UE5 object version enum. Now, new entries will fail to compile, and global package version changes are expected to happen from UE6/Main instead. If you maintain a fork with custom object versions appended to the UE5 enum, this is one of those small commits that can break your build for a reason that isn't immediately obvious. If a UE5-only global bump is ever unavoidable, the commit says to use the UE4 enum's slot instead. There were a few other interesting ones this week: On ue6-main: AVBOIT shipped, and it is off by default: Adaptive Voxel-Based Order Independent Transparency for Nanite and non-Nanite translucency landed on both branches the same day. r.OIT.Method defaults to AVBOIT, but the shader permutations are a project opt-in via r.AVBOIT.Support, which is read-only and defaults off, so the practical default is unchanged. There is a content constraint worth knowing before you evaluate it: translucent materials must output their own luminance only, because materials that sample scene color self-composite the background and the resolve adds it again. Refraction and distortion are future work. UBA's memory watchdog was throttling against the wrong number: Both percentage thresholds were applied to the commit limit rather than to the quantity each came from. On a 274 GB machine the kill threshold sat at 100.9% of physical RAM and...
Keep reading with a free account
The rest of this post, and every signal for Epic Games, is in your free account.
Also quoted as evidence
[comment u/ProfitAggressive1059] the UE5 enum lock is such a quiet but massive signal, they really are drawing a hard line between 5 and 6 now