07-25-2018, 09:25 AM
Actually that is the behaviour ( not related to V1.16 RC1, it always have been like this, please post V1.16 RC1 related stuff on it's thread as it is easier to me to keep overview of stable and unstable versions ).
However, this was a design decision long ago to not send every patch changing every time even though it didn't change.
The patch module doesn't know about the current value of the destination, only what it sent last. This was in the first place to limit the communication (and so slowing down) of the expander modules. Some patch values btw. will be updated every time, like triggers that are limited in time.
I will think about to let that go for the internal settings/values.
However, this was a design decision long ago to not send every patch changing every time even though it didn't change.
The patch module doesn't know about the current value of the destination, only what it sent last. This was in the first place to limit the communication (and so slowing down) of the expander modules. Some patch values btw. will be updated every time, like triggers that are limited in time.
I will think about to let that go for the internal settings/values.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!