Lynisra 0 Posted May 24, 2022 Type of Bug: Interface-related(?) • Description: ObjectMover's tint panel's Auto-Update incorrectly setting up Saturation values. • Evidence (Chat message/Screenshot): • Steps to reproduce: Selecting an object without any Saturation while the Tint-Panel is set to "Auto-update" • Expected result: Saturation to display it's number. • Observed result: When a Gob doesn't have any Saturation value, the ObjectMover will show it to be 100, making any further Tint-changes update the Gob and saturate it. • Reproduction rate: 100% when an object is selected. • Additional information: It does not automatically Saturate objects, it merely displays the wrong value, however when the window is being used, it will Saturate things properly using the slider. Share this post Link to post
Razmataz 14 Posted May 28, 2022 @MindScape, let me know if this is also a problem with my commands / addonmsg output. Share this post Link to post
MindScape 66 Posted June 3, 2022 On 5/28/2022 at 10:26 AM, Razmataz said: @MindScape, let me know if this is also a problem with my commands / addonmsg output. The slider has some hacks for switching automatically between saturation for tint vs overlay since tint used to not have saturation. With the update these hacks make it incorrectly reset saturation to 100. Pretty sure I fixed this in the OM update to support new tint systems, but that hasn’t been pushed yet. Share this post Link to post