This update merges a bunch of recent beta versions into the stable channel, along with a couple new additions.
New features in 1.29.10:
Bug fixes in 1.29.10:
- Added Stop All Storyboards action.
- Added TimeHelpers script functions to format laptimes and session times more easily.
- TimeHelpers.SecondsToLaptime: converts total seconds (83.12345) to a formatted laptime (1:23.123).
- TimeHelpers.SecondsToSessionTime: converts total seconds (11933.12345) to a formatted session time including hours (03:18:53).
- Theme Editor should now also run in 64-bit mode which allows it to use more memory which is useful for larger themes. Possibly up to 2 GB theme files can now be exported. Note we still recommend much smaller theme files.
Updates merged from beta 1.29.9:New features:
- Fixed a bug where doubleclicking an item could sometimes move it out of its folder or parent item.
- Fixed a bug where the right-click menu on a Widget would no longer have the "Add Subwidget" option.
- Fixed crash on closing Script performance window.
- Add the ability to group theme items by folders in the Theme Explorer. Read more about folders here!
- Add 'Seconds Format' to any gap/interval special bindings, which control the way the seconds portion of a gap time is formatted. For example, use the default "0.000" to get 3 decimals, or use "0.0" to get a single decimal, etc.
- You can now use team ID as a target for a camera focus change. To target a specific team by their ID, add "T" in front of the team ID in the Value of the camera change action. For example, to target team 12345 use "T12345".
- Add the ability to specify Actions on a Driver Picker, which get executed when the selected driver changes.
- Updated the ATVO Nuget package to version 1.2.0 for support of the latest Intellisense and auto-complete in Visual Studio Code.
Updates merged from beta 1.29.8:New features:
- Fixed a bug where your computer culture/language settings could cause theme settings to read incorrectly in ATVO.
Widgets can now be clipped
visually by a rectangular region of your overlay. When clipping is enabled, only the region of the Widget within the clipping rectangle will be visible. Anything outside of the clipping rectangle will be clipped (hidden).
You can define the clipping rectangle using coordinates (Left, Top, Width, Height measured with respect to the overlay window), or by selecting another Widget to act as the 'Clipping Widget'. When you select a clipping widget, the boundaries of the clipping widget define the visible region of your widget. More information: Forum threadTest:
this change required an update of the way Widgets are rendered when running ATVO. Please check for any abnormal positioning, sizing or other unintended changes. Also test the performance of NDI when using the "old" NDI v1 and please let us know if you think performance is negatively affected. Please test this even if you are not using the clipping feature!Bug fixes:
Fixed a bug where Input dataset was not updating when new inputs were added to the theme or when inputs were renamed or removed.