(CCK 3.10) Auto Generation Option loss #8
Comments
|
My tool is made for those not using the CVRAvatar autogen and as such has been excluded from the tool. The copying from CVRAvatar to the parameter asset not doing a deepcopy is also a CCK bug that is reported on the feedback board. While I could copy the autogen to the parameters asset, I would not be able to reference the original assets, as the parameter asset is meant to be shared between avatars- meaning the reference to the objects would be wrong. Basically, this is not in scope of what the tool is meant to do and as such will probably not happen. Personally I avoid the autogen completely due to how broken it can be. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Auto Generation Option loss
The NAK Modular Setting did notr store Auto Generation Options available on some type of the AAS. Such as Color, Toggle, Dropdown, & Slider.
Say I copied my original AAS from
CCKAvatarintoNAKModularSettingfile. And then usingNAKSimpleAASParametercomponent to re-merge along with other AAS modules. If I resync it, my AAS is updated with my original setting along with other modular settings, except their Auto Generation Options. Additionally, with some type, their default value did not copied from the AAS to theNAKSimpleAASParameterasset due to either CCK bug or this.Consider adding such features that preserves OR prepare these Auto Generation Options right from
NAKModularSettingasset file.Screenshots
Don't worry, I can just get out of the prefab discarding the change.
The text was updated successfully, but these errors were encountered: