Unable to Load Engine Binary in HOOPS Communicator 2024.5.0

HOOPS Communicator
, , ,
1

Description:

I’m trying to initialize the WebViewer using HOOPS Communicator version 2024.5.0, but I’m encountering the following error:

Uncaught (in promise) Unable to load engine binary
EX11034-INV-Federated.rvt 8_0.scz /reason Unsupported file version /error

Here are the parameters I’m using to create the viewer:

const params = {
  boundingPreviewMode: 0,
  containerId: "viewer2D",
  endpointUri: "wss://qa2-api.in.invicara.com/graphicssvc?fileSetId=a989fec8-4ae9-47fe-921b-277c578dd657&nsfilter=43IPUT_fzVylUAV&token=...&serverVersion=4",
  enginePath: ".", // <-- this might be the issue?
  model: "EX11034-INV-Federated.rvt 8_0.scz",
  rendererType: 0,
  streamCutoffScale: 0,
  streamMode: 2
};
const _viewer = new window.Communicator.WebViewer(params);

Everything was working fine in previous versions. But after upgrading to 2024.5.0, the viewer fails to load with this error. The console stack trace points to the createInstance method in hoops-web-viewer.umd.js.

Questions:

  1. Is there a change in the engine binary loading behavior in version 2024.5.0?
  2. Do I need to update the enginePath or include additional assets?
  3. What is the correct setup or directory structure expected for loading the engine in this version?

Any help or guidance would be appreciated. Thank you!

2

Please see our docs on this topic:

In the above link, there is the following excerpt:

You can see an example of using the ESM in <COMMUNICATOR_INSTALL_DIR>/web_viewer/examples/esm.html and <COMMUNICATOR_INSTALL_DIR>/web_viewer/examples/esm.js .

3

Migration Issue from 2023_sp3 to 2025.3.0 – WebSocket Connection Failed

We are currently migrating our application from 2023_sp3 to 2025.3.0, and we’re encountering the following error during model load:

modelLoadFailure: async (modelName, reason, error) => {
    console.error('/modelName', modelName, '/reason', reason, '/error', error);
}

Error Details:

  • Model Name: EX11034-INV-Federated.rvt 8_0.scz
  • Reason: "WebSocket connection failed."

We have updated both our server and client versions to the latest as per the official documentation for 2025.3.0.

We would appreciate any guidance or suggestions to resolve this WebSocket issue in the newer version. Has anyone else experienced a similar problem after upgrading to 2025.3.0?

4

Just for clarify, my link was specific to ESM. If you are using UMD (which supports RequireJS), information in our docs is available here:

Also, you had previously mentioned upgrading to version 2024.5.0 in your original post. But now you are trying to upgrade to 2025.3.0. Were you able to upgrade to v2024.5.0? Or are you skipping it and going to straight to 2025.3.0.

5

I’m currently using version 2023_SP1 without any issues. I tried updating to 2023_SP2, and it worked fine. But when I tried switching to a random version like 2024.3.1, and later to the latest version 2025.3.0 (which is my final goal), I ran into a problem both times.

i have followed same document for UMD.

The error message I got was:

  • Model Name: EX11034-INV-Federated.rvt 8_0.scz
  • Reason: “WebSocket connection failed.”
6

There may be more information on the error in the web browser dev console. Also, the communicator logs might provide additional details (but admittedly, I’m not sure on that). To quickly find where the log files are generated, you can find this on the server CMD window:

image
image976×230 9.35 KB