[FEEDBACK] Control the [not sync] parameters from Expressions Menu
available in future release
thakyuu
[Transrated]
In the current Expressions Menu, only the parameter to sync specified in the Expression Parameters can be operated.
Since there is a limit of up to 16 parameters to sync, it is wasteful to assign parameters to sync to operate from the Expressions Menu, even for things that do not need to be synced.
Examples of parameters that do not need to be synced are camera gimmicks that allow you to control depth of field and FoV.
This only needs to work in its own Local, and we think it is wasteful to consume sync parameters.
As a solution, we propose that you can operate parameters that are not specified in the Expression Parameters from the Expressions Menu.
[Japanese(Original)]
[FEEDBACK] Expression Menuから[同期しない]パラメーターを操作したい
現状Expression MenuではExpression Parameterに指定した同期するパラメーターしか操作できません
同期するパラメータは16個までの制約があるため、同期が不要な物にまでExpression Menuからの操作を行うために同期するパラメータを割り当てるのは不合理です。
同期する必要の無いパラメーターの例として、被写界深度やFoVのコントロールを行えるカメラギミックなどが挙げられます。
これは、自身のLocalでのみ機能すればよく、同期するパラメータを消費するのは不合理と考えます。
解決策として、Expression Parameterに指定していないパラメーターを、Expression Menuから操作できる様にする事を提案します。
Log In
HK
available in future release
Dor․
Chipping in with my use case - I'd like to optimize memory usage (programmer OCD thing, I like things to be as optimized as possible), there are a variety of avatars that use radial menus to switch between materials like skin/hair colors or items like various hairstyles, most of them don't exceed a handful of options, meaning they could be stored with 2 to 3 bits using binary counting with bools (as opposed to 8 with a float), and on the unsynced side you need a float for the "dummy" radial menu and a bool for each option to know which option is currently being changed, however since this unsynced side is not supported by the SDK at the moment, it means that it requires these parameters to be synced, it's still a net positive when converting two or more radial menus to a couple of bits (8 for the float + 1 per option + the bits actually needed to make each option function as opposed to 8 per option), for example 2 radial menus with 4 variations each would require 14 bits, as opposed to 16 if each option had it's own float, 3 such options would require 17 as opposed to 24, the more options the greater the benefit, but it could be even better if we didn't need to sync the radial float and the menu opens state bools in the first place, changing the above examples to 4 bits as opposed to 16 and 6 as opposed to 24, respectively.
DrBlackRat
Kinda sad that this is still not a thing, espacially now with OSC. Since if you want to controll something via your Menu you have to waste parameters for it.
HOBaRT
Please implement local/synced parameters for the menus. I have an avatar I'm working on that needs all 128 bits as synced bools for sub-8-bit integers and some other stuff, meaning I have none left to make sensible menus so everything has to be a bool toggle.
Local parameters on the menu would let me easily use parameter drivers to drive the synced bits in a sane fashion (e.g. radial puppet+buttons) instead of creating 128 individual toggles.
sophiа
i think the better way to implement this is the ability to add parameters but set them as local or non synced in the parameter list and they don't count towards your 128 synced ones. this would have alot of uses like password locks, vrc lens, huds, and especially once we get avatar dynamics there's alot of uses for local parameters and we have parameter drivers to make the local animations manipulate a few global parameters.
Demirramon
This would be incredibily useful and wouldn't cause any extra cost in their network