Frequently Asked Questions




Q: Where can I get a new license for HOOPS Communicator?

A: Please review our License Key Overview page for details.

Q: The start_server.bat/sh fails to run, and/or convert_file.bat/sh results in in a "cannot open file" error.

A: Please ensure you run these scripts with Admin privileges, and any output directories have write privileges.

Q: Is the Stream Cache file format backward compatible?

A: The Stream Cache format is backward-compatible starting with HOOPS Communicator 2016 SP2.

Q: What are the file extensions for Communicator/Stream Cache files?

A: There are two primary file types generated by Communicator. An .scs file is a compressed and standalone file containing all of the 3D model data. It is not streamable by the server and will be loaded by the viewer directly via an http request. An .scz file is a single file containing all model data in a streamable form. Its a single file version of a stream cache directory.

Q: Will the node IDs always be the same between loads of the viewer?

A: 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 model. These two lines show how to capture the shift amount from the viewer:

const model = hwv.model;
const nodeOffset = model.getLowestAvailableNodeId();

Now anywhere you need the persistent node ID you would do something like this:

const id = selection.getNodeId() - nodeOffset;

This will always allow you to get back to the persistent ID for retrieving associated application level data.

For more information, see the Assembly Tree Node IDs page.

Q: What's the difference between a PartId and a NodeId?

A: In the Communicator documentation, you may notice that certain functions contain parameters with specific types – for example, the function getNodeLineColor(partId, lineIndex) takes a PartId as a parameter.

But Communicator is, for many users, a Javascript API, so why are there types listed in the documentation?

The object types found in parameters and return values in the Communicator API Reference documentation are extracted from strongly typed objects in Communicator's TypeScript source. Communicator's Web Viewer API is available in both TypeScript and Javascript.

In Javascript, both the PartId and NodeId translate to a generic Javascript number value type (by "value type" we simply mean that variables in Javascript do not have types, but their values do).

Nevertheless, even for Javascript users it's still helpful to know the expected type of object for each parameter, and so the documentation preserves the original TypeScript signatures to let users know the expected type of assembly tree node the function expects as a parameter.

To further clarify, let's walk through a usage scenario. Say, for example, we're using the selectionManager in the Web Viewer and we select a part of the model with a mouse click.

If we then call myViewerInstance.selectionManager.getFirst().getNodeId(), and pass the return value (a NodeId) as the first parameter for getNodeLineColor(partId, lineIndex), would it be valid to pass a NodeId value for the PartId parameter?

In TypeScript, because the Communicator API defines a PartId as a type of NodeId, in our hypothetical call to getNodeLineColor(partId, lineIndex) there will be no type compatibility issues with passing the value of getNodeId() for the PartId parameter.

In terms of API behavior for both TypeScript and Javascript users, as long as the NodeType of the Node in question is indeed a Part (and not a PMI, CADView, Sheet, or other NodeType), then the function will behave as expected.

To query a Node in order to find out its type, call getNodeType().

Q: How do I access the attributes/properties of a CAD file in HC?

A: First you have to make sure to add this option to the converter.exe command line:

--sc_export_attributes "true"

Then you can access the attributes via the XML file saved during conversion and/or in the web client like so:

function selectionChanged(selection: Communicator.Selection.SelectionItem) {
const model = hwv.model;
const parent = model.getNodeParent(selection.getNodeId());
model.getNodeProperties(parent).then(function (response) {
console.log(response);
});
}

You can also access the attributes as you perform the translation to Stream Cache. Use the above-mentioned flag to export the attributes, and specify --output_xml_assemblytree "file.xml". You'll then be able to parse the XML file and get the attributes and other info about the model.

Q: I'm trying SSR and it's not working due to a GL_INVALID_VALUE error -- what does that mean?


warning: SMAA disabled due to GL error: GL_INVALID_VALUE
GL_INVALID_VALUE
GL_INVALID_VALUE
GL_INVALID_VALUE
GL_INVALID_VALUE

A: This usually means that you're trying to run on a VM without a GPU or proper 3D acceleration, or on a machine that has poor integrated graphics. Sometimes an update to the drivers can fix the problem if it has to do with integrated graphics. Oftentimes, there is nothing you can do about this except upgrade run HC on a better machine.

Q: If I'm using the SCS workflow/loading, do I need to run the server?

A: No, but you lose a lot of functionality by going with the SCS workflow, including the streaming mechanism.

Q: What does the "BAD_STREAM_VERSION" message in the Communicator server logs mean?

A: If you're seeing the following error message, you most likely have an old version of the web viewer JavaScript either cached in your browser or in your web application that you are trying to use with a newer version of HOOPS Communicator:

  <OPEN_MODEL_FAILED reason="BAD_STREAM_VERSION" expected="66" actual="59">

Upgrading to the latest version of the web viewer JavaScript should fix this error.

Q: How does HC handle units?

A: A PRC file can have multiple units for different subassemblies, which is something HC keeps track of and resolves. You can query the unit multiplier from the model object which is the same for the whole model using myModel.getUnitMultiplier();.

For more information about units, please see the Working with Units section.

Q: When I start my web application the default viewer just displays a spinner in the bottom left and never does anything else.

A: 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 error that will start you down the correct debugging path.

Q: I'm seeing this error in the web browser debug console:

Could not create canvas: Web page was not allowed to create a WebGL context.

A: This usually means that the machine doesn't have a sufficient graphics card/GPU to run 3D graphics apps in the browser. Often times we'll see this when a user is trying to access HC from a VM or when they are accessing a machine via Microsoft Remote Desktop. RDP disables 3D acceleration (although in some cases it seems not to) so it causes issues.

A good test is to try this link and see if WebGL works: http://webglsamples.org/aquarium/aquarium.html

This will help you determine if the problem is HC specific or not.

Q: I'm seeing a "no status file" error in the web viewer when I try to load it.

A: This indicates there is an issue with your stream cache directory. It's usually one of the following:

Q: Is animation supported in HC?

A: There is no animation framework, but the user can reposition things via the JavaScript API, so animation could theoretically be built on top of HC.

Q: In libconverter on Linux, how do I fix the following error?

undefined reference to 'Communicator::Importer::Init(Communicator::Converter*, std::__cxx11::basic_string, std::allocator >, int)'

A: As of HOOPS Communicator 2019, we use GCC 6.3.1 (specifically, the version from devtoolset-6 6.1 on CentOS 6.9) with -std=c++11. Please note that we are not using the C++11 ABI that is used by default by GCC 5 and later, so code that calls functions in libconverter (and probably any other code that interacts with that code) needs to be compiled with the -D_GLIBCXX_USE_CXX11_ABI=0 flag. Using this flag is likely the solution to the error listed above.

top_level:0