Omniverse play and stop button

Hi, got a problem with flow simulation. I tried create->flow->preset. Works fine for the first play. When I stop the animation and press play again, omniverse create always crash.

→ there is an update to this problem, it seems that it is not just with flow simulation. When i press play->stop->play my omniverse create crash.

Hello, could you please share your log? Might help narrow down why it crashed.

1 Like

Thank you for your reply. What service in the log will I get it?

this is from service Auth–

`2021-08-09 11:16:29,832 | Connection error
Traceback (most recent call last):
File “_build\python\lib\asyncio\windows_events.py”, line 457, in finish_recv
OSError: [WinError 64] The specified network name is no longer available

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “_build\python_lib\websockets\protocol.py”, line 827, in transfer_data
File “_build\python_lib\websockets\protocol.py”, line 895, in read_message
File “_build\python_lib\websockets\protocol.py”, line 971, in read_data_frame
File “_build\python_lib\websockets\protocol.py”, line 1047, in read_frame
File “_build\python_lib\websockets\framing.py”, line 105, in read
File “_build\python\lib\asyncio\streams.py”, line 723, in readexactly
File “_build\python\lib\asyncio\streams.py”, line 517, in _wait_for_data
File “_build\python\lib\asyncio\proactor_events.py”, line 280, in _loop_reading
File “_build\python\lib\asyncio\windows_events.py”, line 812, in _poll
File “_build\python\lib\asyncio\windows_events.py”, line 461, in finish_recv
ConnectionResetError: [WinError 64] The specified network name is no longer available

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “_build\idl.py\idl\connection\transport\ws.py”, line 320, in _listen
File “_build\python_lib\websockets\protocol.py”, line 509, in recv
File “_build\python_lib\websockets\protocol.py”, line 803, in ensure_open
websockets.exceptions.ConnectionClosedError: code = 1006 (connection closed abnormally [internal]), no reason
2021-08-09 11:16:29,833 | Connection error
Traceback (most recent call last):
File “_build\python\lib\asyncio\windows_events.py”, line 457, in finish_recv
OSError: [WinError 64] The specified network name is no longer available

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “_build\python_lib\websockets\protocol.py”, line 827, in transfer_data
File “_build\python_lib\websockets\protocol.py”, line 895, in read_message
File “_build\python_lib\websockets\protocol.py”, line 971, in read_data_frame
File “_build\python_lib\websockets\protocol.py”, line 1047, in read_frame
File “_build\python_lib\websockets\framing.py”, line 105, in read
File “_build\python\lib\asyncio\streams.py”, line 723, in readexactly
File “_build\python\lib\asyncio\streams.py”, line 517, in _wait_for_data
File “_build\python\lib\asyncio\proactor_events.py”, line 280, in _loop_reading
File “_build\python\lib\asyncio\windows_events.py”, line 812, in _poll
File “_build\python\lib\asyncio\windows_events.py”, line 461, in finish_recv
ConnectionResetError: [WinError 64] The specified network name is no longer available

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “_build\idl.py\idl\connection\transport\ws.py”, line 320, in _listen
File “_build\python_lib\websockets\protocol.py”, line 509, in recv
File “_build\python_lib\websockets\protocol.py”, line 803, in ensure_open
websockets.exceptions.ConnectionClosedError: code = 1006 (connection closed abnormally [internal]), no reason
2021-08-11 17:50:40,023 | Connection error
Traceback (most recent call last):
File “_build\python\lib\asyncio\windows_events.py”, line 457, in finish_recv
OSError: [WinError 64] The specified network name is no longer available

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “_build\python_lib\websockets\protocol.py”, line 827, in transfer_data
File “_build\python_lib\websockets\protocol.py”, line 895, in read_message
File “_build\python_lib\websockets\protocol.py”, line 971, in read_data_frame
File “_build\python_lib\websockets\protocol.py”, line 1047, in read_frame
File “_build\python_lib\websockets\framing.py”, line 105, in read
File “_build\python\lib\asyncio\streams.py”, line 723, in readexactly
File “_build\python\lib\asyncio\streams.py”, line 517, in _wait_for_data
File “_build\python\lib\asyncio\proactor_events.py”, line 280, in _loop_reading
File “_build\python\lib\asyncio\windows_events.py”, line 812, in _poll
File “_build\python\lib\asyncio\windows_events.py”, line 461, in finish_recv
ConnectionResetError: [WinError 64] The specified network name is no longer available

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “_build\idl.py\idl\connection\transport\ws.py”, line 320, in _listen
File “_build\python_lib\websockets\protocol.py”, line 509, in recv
File “_build\python_lib\websockets\protocol.py”, line 803, in ensure_open
websockets.exceptions.ConnectionClosedError: code = 1006 (connection closed abnormally [internal]), no reason
2021-08-11 17:50:40,029 | Connection error
Traceback (most recent call last):
File “_build\python\lib\asyncio\windows_events.py”, line 457, in finish_recv
OSError: [WinError 64] The specified network name is no longer available

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “_build\python_lib\websockets\protocol.py”, line 827, in transfer_data
File “_build\python_lib\websockets\protocol.py”, line 895, in read_message
File “_build\python_lib\websockets\protocol.py”, line 971, in read_data_frame
File “_build\python_lib\websockets\protocol.py”, line 1047, in read_frame
File “_build\python_lib\websockets\framing.py”, line 105, in read
File “_build\python\lib\asyncio\streams.py”, line 723, in readexactly
File “_build\python\lib\asyncio\streams.py”, line 517, in _wait_for_data
File “_build\python\lib\asyncio\proactor_events.py”, line 280, in _loop_reading
File “_build\python\lib\asyncio\windows_events.py”, line 812, in _poll
File “_build\python\lib\asyncio\windows_events.py”, line 461, in finish_recv
ConnectionResetError: [WinError 64] The specified network name is no longer available

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “_build\idl.py\idl\connection\transport\ws.py”, line 320, in _listen
File “_build\python_lib\websockets\protocol.py”, line 509, in recv
File “_build\python_lib\websockets\protocol.py”, line 803, in ensure_open
websockets.exceptions.ConnectionClosedError: code = 1006 (connection closed abnormally [internal]), no reason
2021-08-19 01:16:52,184 | Connection error
Traceback (most recent call last):
File “_build\python\lib\asyncio\windows_events.py”, line 457, in finish_recv
OSError: [WinError 64] The specified network name is no longer available

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “_build\python_lib\websockets\protocol.py”, line 827, in transfer_data
File “_build\python_lib\websockets\protocol.py”, line 895, in read_message
File “_build\python_lib\websockets\protocol.py”, line 971, in read_data_frame
File “_build\python_lib\websockets\protocol.py”, line 1047, in read_frame
File “_build\python_lib\websockets\framing.py”, line 105, in read
File “_build\python\lib\asyncio\streams.py”, line 723, in readexactly
File “_build\python\lib\asyncio\streams.py”, line 517, in _wait_for_data
File “_build\python\lib\asyncio\proactor_events.py”, line 280, in _loop_reading
File “_build\python\lib\asyncio\windows_events.py”, line 812, in _poll
File “_build\python\lib\asyncio\windows_events.py”, line 461, in finish_recv
ConnectionResetError: [WinError 64] The specified network name is no longer available

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “_build\idl.py\idl\connection\transport\ws.py”, line 320, in _listen
File “_build\python_lib\websockets\protocol.py”, line 509, in recv
File “_build\python_lib\websockets\protocol.py”, line 803, in ensure_open
websockets.exceptions.ConnectionClosedError: code = 1006 (connection closed abnormally [internal]), no reason
2021-08-19 01:16:52,192 | Connection error
Traceback (most recent call last):
File “_build\python\lib\asyncio\windows_events.py”, line 457, in finish_recv
OSError: [WinError 64] The specified network name is no longer available

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “_build\python_lib\websockets\protocol.py”, line 827, in transfer_data
File “_build\python_lib\websockets\protocol.py”, line 895, in read_message
File “_build\python_lib\websockets\protocol.py”, line 971, in read_data_frame
File “_build\python_lib\websockets\protocol.py”, line 1047, in read_frame
File “_build\python_lib\websockets\framing.py”, line 105, in read
File “_build\python\lib\asyncio\streams.py”, line 723, in readexactly
File “_build\python\lib\asyncio\streams.py”, line 517, in _wait_for_data
File “_build\python\lib\asyncio\proactor_events.py”, line 280, in _loop_reading
File “_build\python\lib\asyncio\windows_events.py”, line 812, in _poll
File “_build\python\lib\asyncio\windows_events.py”, line 461, in finish_recv
ConnectionResetError: [WinError 64] The specified network name is no longer available

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “_build\idl.py\idl\connection\transport\ws.py”, line 320, in _listen
File “_build\python_lib\websockets\protocol.py”, line 509, in recv
File “_build\python_lib\websockets\protocol.py”, line 803, in ensure_open
websockets.exceptions.ConnectionClosedError: code = 1006 (connection closed abnormally [internal]), no reason`

Thanks for the logs @milan5! The development team is reviewing them and will get back to you soon!

LogFolder
The log snippet in your reply does not quite look like a typical Create log. In the console window, there is a folder icon that should take you to a full .log file. Can you share this log?

Hi areidmeyer,

Thank you for the advice. Now I know that. It seems that the new update Create 2021.3.2 removed the crash and I can’t recreate it now. I will close this one. Thanks.