I am experimenting with a NDMF optimization plugin that could turn rarely-updated synced parameters into local parameters, and sync them using a multiplexer, in order to let the avatar build with synced parameters above the current hard limit of 256 bits.
In RenameParametersHook.cs:199, there is a validation checking that the total bits used by synced parameters is within legal bounds.
However, this validation phase runs before the NDMF BuildPhase.Optimizing phase, which can potentially reduce the number of synced parameters within legal bounds.
This prematurely marks the avatar as not being successful.
Would it be possible to defer, mute, or address this validation phase?
I am experimenting with a NDMF optimization plugin that could turn rarely-updated synced parameters into local parameters, and sync them using a multiplexer, in order to let the avatar build with synced parameters above the current hard limit of 256 bits.
In RenameParametersHook.cs:199, there is a validation checking that the total bits used by synced parameters is within legal bounds.
However, this validation phase runs before the NDMF BuildPhase.Optimizing phase, which can potentially reduce the number of synced parameters within legal bounds.
This prematurely marks the avatar as not being successful.
Would it be possible to defer, mute, or address this validation phase?