Release Notes 3.2 – September 30, 2026
1 What’s new?
1.1 New Features / Enhancements in vs | studio
1.1.1 New Editors for open vs | plus
With Release 3.2, two new editors are introduced. In the open vs | plus Parameters editor, users can define central parameters that can be used in their own open vs | plus scripts. The new open vs | plus Script editor allows the creation of custom extensions. The implementation is based on an integrated LUA development environment. The feature is available for vs | plus version 8.0.0 and later and requires the “mango” flavour as well as additional licenses for open vs | plus.
Note: The use of open vs | plus enables the execution of user-defined scripts and advanced functions. As a result, security-relevant risks may arise. Therefore, it should only be used by appropriately qualified and trained users.
1.1.2 Compatibility Mode for Data Exchange
When exporting node versions, a target version of vs | studio can now be selected. This allows data to be exported specifically for older versions and ensures compatibility during data exchange. If the export contains information that is not supported by the selected target version, the user will be notified accordingly.
1.1.3 vs | plus 10.0
Release 3.2 introduces support for vs | plus 10.0. vs | studio now enables the creation of new node versions and the migration of existing projects to the new vs | plus 10.0 version. As part of this enhancement, the display element types Relay and Flasher have been replaced by Digital Outputs.
In addition, the PT memory processing in vs | plus 10.0 has been revised and extended with support for CAM and SREM messages. As a result, serial CAM and SREM messages can now be sent to vs | plus 10.0 from the Test Bench in addition to analog R09 telegrams.
1.1.4 Support for OCIT-C 2.0, 2.1, und 2.2
To improve compatibility during data import into vs | studio, the OCIT-C versions 2.0, 2.1, and 2.2 are now supported.
1.1.1 Enhanced OCIT Import (All Versions)
open vs | plus scripts can now also be imported via OCIT. The functionality is available for vs | plus from version 8.0.0.
1.1.2 Editor: Inputs (Logical)
- The input type “Virtual Input” has been renamed to “open vs | plus Input” and is now identified as a serial input.
- When selecting the physical input, the channel number is now also displayed in the drop-down menu. This makes entries easier to identify and sort.
1.1.3 Editor: Traffic Stream Connections
- Inputs with the detector type “Public Transport Memory” must now be assigned to a traffic stream.
- When selecting a traffic stream, the ID number is now also displayed in the drop-down menu. This simplifies the assignment and sorting of entries.
1.1.4 Editor: Public Transport Memory Parameters
- Recording a rest time is now only possible for parallel inputs.
- Recording a delay time for check-out caller is no longer supported. This change may cause existing configurations that were previously valid to be displayed as invalid. In this case, only the configured delay time of the check-out caller needs to be removed.
1.1.5 Various Editors
- Horizontal scrolling using the Shift key and mouse wheel is now supported.
- Additional warnings indicate when recorded data is exclusively OCIT-I compliant or exclusively OCIT-C compliant, but does not comply with both standards.
1.1.6 Extended Data Reconstruction via OIVD
The reconstruction of vs | plus data during the import of an OIVD with VCB data has been enhanced. Traffic stream connections can now also be restored even if no traffic stream has been assigned to them.
1.1.7 Completely Revised Test Bench
With the Release 3.2, the Test Bench has been fundamentally redesigned. In addition to significantly improved performance, optimized memory management and reduced resource consumption provide greater efficiency and stability in daily operation.
Furthermore, the Test Bench now supports the display of cycle seconds in green as well as time measurements using “Snap-In”. In combination with vs | plus 10.0.0, SREM and CAM messages can also be sent directly from the Test Bench.
The revision is complemented by a new filter function for the signal timing plan, which allows the displayed information to be specifically adapted to the respective requirements.
1.1.8 Migration from .NET 8 to .NET 10
With this release, our applications have been updated from .NET 8 to .NET 10. Operation requires the .NET 10 Runtime (version 10.0.10 or higher). This may either already be installed or can be installed together with the release.
1.2 New Features / Enhancements (vs | mate)
1.2.1 Window Position at Startup
vs | mate now stores the last used window position, analogous to vs | studio. Provided that the monitor configuration remains unchanged, it will be restored automatically at the next startup.
1.2.2 Improved Performance
Supplies are loaded faster.
1.2.3 Revised SignalControl for PTV Vissim
The SignalControl for PTV Vissim has been technically revised and now offers higher performance, optimized memory management, and more efficient use of system resources.
1.2.4 New Process Data for PT Traffic Streams and PT Memory Inputs
The process data in vs | mate has been extended with two new tabs. Public Transport Traffic Streams (for all vs | plus versions) and Public Transport Memory Inputs (from vs | plus 10.0.0) display public transport specific process data from vs | plus. This provides users with a more detailed insight into the current operating status and allows relevant information about public transport functions to be viewed directly in vs | mate.
1.3 Improvements & Bug Fixes (vs | studio)
1.3.1 Uppercase / Lowercase Handling for User Name (Login)
The login is now case-insensitive with respect to the user name.
1.3.2 Improved Performance and Stability
With this update, numerous optimizations have been made to vs | studio to further improve performance and stability in daily use.
- Faster and smoother operation, especially during longer working sessions.
- Resolution of issues that could lead to increased memory consumption over time.
- Improved stability and reliability during long-term use.
1.3.3 Correction of the Display of Signal Group Chambers
If a signal group chamber was used only in the additional patterns, the display in the Signal Programs, Frame Signal Plans, Demand Control, and Test Bench editors was incorrect. This has been corrected in the aforementioned editors as well as in the reporting of these editors.
1.3.4 AMLi-entry Was Negated
The AMLi-Entry (for public transport memory) in the Traffic Stream Connections editor was displayed as negated. This has been corrected so that when selecting the AMLi-entry, it is written instead of being suppressed.
1.3.5 Lines and Routes Are Now Required When Using the PT Memory
The definition of Lines and Routes is now mandatory when using PT memory traffic streams. Consequently, the PT memory dataset definition must also reference a Lines and Routes dataset.
1.3.6 The Order in Reporting Has Been Adjusted
The order in reporting did not correspond to the order of the editors in the main menu of the node version. This has been adjusted accordingly.
1.3.7 Visualization of External Nodes, e.g. with PTV Vissim
The visualization of external nodes has been improved and two fundamental issues have been resolved. Firstly, when establishing the connection to the external node, it is now checked whether the connection exists. Secondly, the status is now displayed correctly in the event of an error.
2 Known Issues
2.1 open vs | plus Editor (vs | studio)
When displaying the completion list, it may occur that it is not shown directly at the mouse pointer but offset. Workaround: Simply press Ctrl + Space again so that the display is rebuilt.