FIXED: Websocket DAT not working

Bugs
1

Websocket DAT not working, not able to connect to any address (no call backs or pings)

was following this tutorial and got stuck. seems like a few other people have encountered same issue with 2022 build.

have also tested the Websocket DAT operator snippet with default address - also not working

Windows 10 2022.32120
also not working in Windows 10 2022.24200

Can confirm Websocket DAT working properly in Windows 10 Build 2021.16960

2

Same issue here ! it did trick me for a while:)

Not Working
2022.32660

Working:
2020.26630

On Windows 10 / 19045.2965

3

Hmm I was having some issues with the websocket dat too, ill swap to an older version and see if my issues go away

4

So, using the Snippet, clearing what’s in the tables, if you connect to echo.websocket.events, and run the runMe DAT, you don’t get the following ?

image
image1725Ă—851 76.9 KB

Same issue for @oliviano @GRNCH ?

5

thanks for the replies - correct - it seems like it’s unable to connect.

Reset / Active on websocket1 doesn’t seem to do anything, nor does running the runMe script… just nothing… no logs in Textport either

image
image1956Ă—1275 128 KB

6

If you set the environment variable TOUCH_TEXT_CONSOLE=1 and restart TouchDesigner then any Websocket errors will be output in a separate console window. Can you send what errors you receive (if any) when connecting to ws://echo.websocket.events?

1 Like
7

I expect this is the same issue that others were running into in this thread:

We have fixed this bug in our newly released official build: 2022.33600.

Please try this build out and let us know how it works for you.