# Unable to Load Engine Binary in HOOPS Communicator 2024.5.0

**URL:** <https://forum.techsoft3d.com/t/unable-to-load-engine-binary-in-hoops-communicator-2024-5-0/4642>\
**Category:** HOOPS Visualize Web\
**Tags:** code, sample, webviewer, learn\
**Created:** [May 12, 2025, 3:35pm UTC](https://forum.techsoft3d.com/t/unable-to-load-engine-binary-in-hoops-communicator-2024-5-0/4642 "2025-05-12T15:35:10Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![raja.r](https://avatars.discourse-cdn.com/v4/letter/r/a3d4f5/32.png) [@raja.r](https://forum.techsoft3d.com/u/raja.r)\
**Post date:** [May 12, 2025, 3:35pm UTC](https://forum.techsoft3d.com/t/unable-to-load-engine-binary-in-hoops-communicator-2024-5-0/4642/1 "2025-05-12T15:35:10Z")

</div>

**Description:**

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

```auto
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:

```auto
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!

---

<div class="post-metadata">

**Author:** ![tino](https://avatars.discourse-cdn.com/v4/letter/t/9dc877/32.png) [@tino](https://forum.techsoft3d.com/u/tino)\
**Post date:** [May 12, 2025, 4:01pm UTC](https://forum.techsoft3d.com/t/unable-to-load-engine-binary-in-hoops-communicator-2024-5-0/4642/2 "2025-05-12T16:01:33Z")

</div>

Please see our docs on this topic:

> **[ESM — HOOPS Communicator Documentation](https://docs.techsoft3d.com/communicator/latest/overview/esm.html#the-esm)**

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_ .

---

<div class="post-metadata">

**Author:** ![raja.r](https://avatars.discourse-cdn.com/v4/letter/r/a3d4f5/32.png) [@raja.r](https://forum.techsoft3d.com/u/raja.r)\
**Post date:** [May 14, 2025, 3:00am UTC](https://forum.techsoft3d.com/t/unable-to-load-engine-binary-in-hoops-communicator-2024-5-0/4642/3 "2025-05-14T03:00:08Z")

</div>

**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:

```auto
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?

---

<div class="post-metadata">

**Author:** ![tino](https://avatars.discourse-cdn.com/v4/letter/t/9dc877/32.png) [@tino](https://forum.techsoft3d.com/u/tino)\
**Post date:** [May 14, 2025, 11:46am UTC](https://forum.techsoft3d.com/t/unable-to-load-engine-binary-in-hoops-communicator-2024-5-0/4642/4 "2025-05-14T11:46:22Z")

</div>

Just for clarify, my link was specific to ESM. If you are using UMD (which supports RequireJS), information in our docs is available [here:](https://docs.techsoft3d.com/communicator/latest/overview/esm.html#the-umd)

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.

---

<div class="post-metadata">

**Author:** ![raja.r](https://avatars.discourse-cdn.com/v4/letter/r/a3d4f5/32.png) [@raja.r](https://forum.techsoft3d.com/u/raja.r)\
**Post date:** [May 14, 2025, 2:05pm UTC](https://forum.techsoft3d.com/t/unable-to-load-engine-binary-in-hoops-communicator-2024-5-0/4642/5 "2025-05-14T14:05:05Z")

</div>

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.”

---

<div class="post-metadata">

**Author:** ![tino](https://avatars.discourse-cdn.com/v4/letter/t/9dc877/32.png) [@tino](https://forum.techsoft3d.com/u/tino)\
**Post date:** [May 14, 2025, 2:30pm UTC](https://forum.techsoft3d.com/t/unable-to-load-engine-binary-in-hoops-communicator-2024-5-0/4642/6 "2025-05-14T14:30:45Z")

</div>

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](https://us1.discourse-cdn.com/flex020/uploads/techsoft3d/original/2X/6/65ba8ad32530b0d4d6dcaab384df9b94f9439593.png)

---

<div class="post-metadata">

**Author:** ![bgupta](https://avatars.discourse-cdn.com/v4/letter/b/8baadc/32.png) [@bgupta](https://forum.techsoft3d.com/u/bgupta)\
**Post date:** [May 19, 2025, 6:30am UTC](https://forum.techsoft3d.com/t/unable-to-load-engine-binary-in-hoops-communicator-2024-5-0/4642/7 "2025-05-19T06:30:16Z")

</div>

this.hwv = new Communicator.WebViewer({  
containerId: objectId,  
buffer: modelUrl  
});

nothing more

---

<div class="post-metadata">

**Author:** ![tino](https://avatars.discourse-cdn.com/v4/letter/t/9dc877/32.png) [@tino](https://forum.techsoft3d.com/u/tino)\
**Post date:** [May 19, 2025, 10:46am UTC](https://forum.techsoft3d.com/t/unable-to-load-engine-binary-in-hoops-communicator-2024-5-0/4642/8 "2025-05-19T10:46:08Z")

</div>

Hello @bgupta,

Did you have a specific question on your code snippet? My last post was on reviewing the Communicator logs which your post does not seem to be related to.

Thanks,  
Tino