Web Viewer example not working -- the play() request was interrupted by a new load request

Omniverse Core Platform Kit Application Streaming
1

I’ve been trying to follow the example at Stream on a Workstation — Guide: Embedded Web Viewer – the USD Viewer build and the npm install work fine. However, when I go to open the web page, it tends to get either to the stage of loading assets and then hang, or get to showing loaded assets but there is still no display. In the Chromium developer console, the errors that show at the end (in this case it got stuck on the loading assets screen) are:

image
image542×873 126 KB

And on the USD viewer console, some of the earliest errors are:
main: thread_init: already added for thread
2025-01-21 14:03:46 [65,069ms] [Error] [carb.livestream-rtc.plugin] nvstPushStreamData error for eye 0, stream 0x7e2fd0010e20: 0x800b0000
2025-01-21 14:03:46 [65,233ms] [Warning] [omni.fabric.plugin] Warning: attribute viewportHandle not found for bucket id 7e

2025-01-21 14:03:46 [65,236ms] [Warning] [carb.livestream-rtc.plugin] sendCustomMessageToClient: send failure: 0x800b1000 ({“event_type”: “updateProgressActivity”, “payload”: {“text”: “”}})

Any ideas what might be happening here? (This is all running on a single machine, so I wouldn’t expect firewall rules to be an issue here.)

2

Yes that is strange. Can you load “anything”? Even the default test scene? I am trying to figure out if it is the specific USD file you are loading, or the general setup.

3

We’re looking into this. In the meantime, can you see if the non-streaming USD Viewer version works:repo launch -- --/app/auto_load_usd="${app}/../samples/stage01.usdor ./repo.sh launch -- --/app/auto_load_usd="\${app}/../samples/stage01.usd. You’ll need to allow shader cache to compile for a few minutes if it hasn’t yet on the computer you launch this on.

4

This is happening during the initial load of the default scene01.usd. If I bring up the USD Viewer window after the errors occur, I can see that it loaded the scene and is displaying it OK. I just don’t see it streaming to the browser display at all.

5

Yes, the non-streaming USD Viewer works fine.

1 Like
6

Can you provide us full logs of this so we can try to track it down.

7

Here are the logs I could gather.
usd-viewer.log (47.9 KB)
web-streamer-devconsole.log (5.0 KB)

8

Thanks. We will take a look

9

FYI, I just tried the example on another Linux machine – a desktop machine this time – and it failed pretty much the same way.