Version 1.9.11.45 Changes
Last updated
Last updated
This version adds the first 8 characters of the GUID that identifies a translator or combiner to the bottom of the hover balloon in the Logic Flows user interface. This makes it easier to equate the graphical element to the API and/or backup files.
Warning: This feature should only be used in very specific situations as described below. By enabling this checkbox you are eliminating a safety check in your system.
After double clicking on a translator in Logic Flows and clicking the Advanced link, you will now see an additional checkbox called Disable Recursion Detection. Turning this checkbox on will generate a warning for confirmation and then will bypass the recursion detection settings on that translator.
This option should rarely if ever be used. It is removing a protection. In most cases if your flow is being disabled due to the recursion detection system, it means there is flawed logic that is executing in a loop. Without the recursion detection such a loop could cause the CPU to spike to 100% and cause significant sluggishness or lockups. This is what recursion detection strives to prevent. However, in certain rare situations, many highspeed changes may be normal and not a sign of a loop. For example if the start point is a fader gain setting, moving the fader can cause lots of data which can create a false positive in the recursion detection. In these cases it is usually better to alter the detection settings to support the quantity of data you expect rather than to disable the detection. But in certain cases it may still be desirable to disable it completely for a translator and this option allows that.
Disabling recursion detection is only available in logic flows at this point in time. It is not available in the user panel generated flows or within SapPropertyRouter translations. See more on this subject below.
Warning: Turning this option on yields a logic flow config file for that particular flow that is not backwards compatible with previous software versions. If you enable this option on a translator and then downgrade to a previous version of software, the flow item will not load into the system. This is due to additional constructor fields necessary to store the parameter. That field is only present in the stored API command if the option is enabled. And since that constructor parameter does not exist in older versions of software, the system running older software versions will not construct a translator with this option enabled.
Recursion detection within a SapProperty router has been modified such that it is disabled at the router level, but still happens at the source and destination level. This to prevent a problem where occasionally the router level translation was being disabled by recursion detection when large numbers of route changes were taking place at the same time (such as scene changes) or where many sources were receiving signal values at the same time. Instead recursion will be detected at the source or destination and passed through the central router level regardless of frequency. If you have values that are not transitioning through an active route in a SapProperty router, it is worth checking whether the source, destination, or router translation has been disabled by the recursion detector and if so adjust the recursion settings.
