Error Executing DMX Script from Client Connection When Using Version 3.4

Version 3.4 introduced a bug that prevented DMX client connections from working.

This was due to the AppData/Dmx/TerminationBytes registry key not processing the escaped string correctly.¬† \r\n should be processed as 2 bytes, one Carriage Return and one Linefeed.¬† Unfortunately the string was not un-escaped¬† and the termination string was processed as 4 bytes, ‘\’, ‘r’, ‘\’, ‘n’.

Here is a Wikipedia article on Escape Characters for those who are interested.

Resolution

Version 3.5 has been released to resolve this issue.

By | Updated On November 3, 2023 10:44 am | No Comments | Categories: | Tags:


INTEG Process Group, inc. © 2023

Real-Time
Mon - Fri, 8am - 4pm EST
P: 724-933-9350
PureChat
Always Available
Contact Form
sales@integpg.com
support@integpg.com

@integpg
@jniordev
8748