HOOPS Web Viewer

This usually means that the user’s machine doesn’t have a sufficient graphics card/GPU to run 3D graphics apps in the browser. Often times we’ll see this when the user is trying to access HOOPS Communicator from a VM or …

A PRC file can have multiple units for different subassemblies which is something HOOPS Communicator keeps track of and resolves. You can query the unit multiplier from the model object which is the same for the whole mo…

Yes the IDs for a node in the HOOPS Communicator web viewer are persistent

No. The Web GL viewer in HOOPS Communicator was written from the ground up to work with our streaming technology and leverages 20+ years of graphics experts in our development team.

Yes, this is a supported function of HOOPS Communicator

Yes, but loading multiple models in the same scene requires accounting for a shift in node IDs. Here’s how to do this: After you’ve loaded your first model, you’ll want to keep track of the shift before loading a new mo…

This indicates there is an issue with your stream cache directory. It’s usually one of the following: The root file in your stream cache is corrupt/damaged/not there The stream cache directory is not accessible fro…

Yes. I recommend that each customer build out their own viewer, but using the sample is perfectly fine, and you can hide the model tree by editing some of the JavaScript UI classes that are built into the sample viewer.…

This means there was some kind of error in your JavaScript or error contacting the Service Broker that wasn’t handled. Open the debugger in your web browser and have a look at the console output. There is usually an erro…