Reference
Troubleshooting
Find the message or symptom you see, then follow the steps. If you still need help, see Contact support.
Connection
| What you see | What to do |
|---|---|
| ForgeNode Unavailable or Checking ForgeNode… | Open ForgeNode on this workstation and check that its badge is ONLINE. Then refresh the workspace. |
| ForgeNode Health Only | ForgeNode is running but not accepting work from this browser. Check the ForgeNode dashboard for a license or setup message, then open a project and use Retry local ForgeNode access. |
| Enable local ForgeNode access / Retry local ForgeNode access | Choose it and allow the browser prompt to access apps and services on this device. If you blocked it, allow local network access for loudgears.com in the browser's site settings. See Allow local access. |
| CLOUD DEGRADED in ForgeNode | Check the workstation's internet connection. |
A lost connection between the browser and ForgeNode does not mean a run failed. Check the run in the Solve Queue before doing anything else.
ForgeNode setup
| What you see | What to do |
|---|---|
| SETUP REQUIRED or DEPENDENCIES REQUIRED | Choose Install / Repair Dependencies and wait for it to finish. |
| DEVICE SETUP REQUIRED / DEVICE ATTESTATION REQUIRED | Run Install / Repair Dependencies again. It initialises the workstation's identity. License activation is a separate step. |
| Activate License keeps coming back | Complete the activation page in the browser. If you removed this device under Manage your devices, close and reopen ForgeNode before activating again. |
| This activation link has expired | Go back to ForgeNode and choose Activate License again. |
| Download unavailable on the download page | Your workspace has no plan that includes ForgeNode. Choose a plan, or ask your administrator. |
| CUDA / GPU shows GPU routes unavailable | The workstation has no usable NVIDIA GPU. Use CPU Standard, or update the NVIDIA driver and restart ForgeNode. |
Restart required after hibernation
ForgeNode's first run on a computer must start from a fresh Windows start-up. That first run proves the workstation's identity to Microsoft Azure Attestation, and Windows cannot give that proof after it resumes from hibernation (S4) until it is restarted.
- If Windows resumed from hibernation since its last restart and ForgeNode has not yet completed a run on this computer, the installer shows a restart notice when it finishes, and the workspace shows Computer restart required — new analysis blocked or Connected · New analysis blocked · Restart computer before you submit. Restart Windows (Start > Power > Restart), then open ForgeNode again. Shutting down and powering on with Fast Startup is not a substitute for Restart.
- After the first run has succeeded, hibernation no longer matters: later runs start normally after the workstation resumes.
- Reinstalling ForgeNode or resetting its local data makes the next run a first run again.
Boot state unverified — new analysis blocked means ForgeNode could not confirm the workstation's start-up state. Restarting Windows usually resolves it.
Starting a run
| What you see | What to do |
|---|---|
| Add to FEA queue is disabled | Check that you selected one STEP file, the load case is bound (or the manual override is saved), a route is available, ForgeNode is connected, and your plan has analyses left. |
| Save or re-save a Fitment snapshot | Choose Load vehicle loads again, or save your manual override. Loading geometry alone assigns no load. |
| A run of an IGES or X_T file fails | IGES and X_T import is in beta. Export the wheel as STEP from your CAD system and run it again. |
| Choose a STEP … file | STEP, IGES and Parasolid X_T are accepted (IGES and X_T with an up-to-date ForgeNode). Export the wheel to one of these formats. |
| This ForgeNode cannot load X_T files | Update ForgeNode, or export STEP. See Exporting X_T. |
| This X_T was written by a Parasolid version ForgeNode cannot read | Export the wheel again as X_T from a current CAD release, or export STEP. |
| This ForgeNode accepts STEP only | Update ForgeNode to load IGES, or export the wheel to STEP. |
| The IGES surfaces do not close into a solid | The surfaces leave gaps larger than 0.1 mm. Export the wheel as a solid IGES or as STEP. See Exporting IGES. |
| This IGES file contains more than one body | Export only the wheel, as a single solid. |
| This IGES export contains … damaged surface(s) that cannot be repaired | ForgeNode repairs common IGES defects automatically; these surfaces were beyond repair. Export the wheel as STEP. |
| ForgeNode could not repair the surfaces of this IGES export / could not mesh the surfaces | IGES stores many rounded surfaces as approximations. ForgeNode repairs most of them automatically and checks meshing before the analysis; this file was beyond repair. Export the wheel as STEP. |
| …outside the size of a wheel. Check the units of the export. | The IGES declares the wrong length unit. Export it again with the correct unit, or export STEP. |
| …export X_T, not X_B / …complete Parasolid text (X_T) header | The file is a binary or truncated Parasolid export. Export text X_T (.x_t) again. |
| ForgeNode could not read this X_T file / could not convert this X_T file | The export could not be decoded. Export the wheel again as text X_T, or export STEP. |
| ForgeNode could not rebuild this X_T as a closed analytic solid | The rebuilt surfaces did not close into one solid that meshes. Export only the wheel as one body, or export STEP. |
| Geometry files must be … no more than 50 MB | Simplify or re-export the model to reduce the file size. |
| No public load case available | Choose another matching vehicle, or use an approved manual override. |
During and after a run
| What you see | What to do |
|---|---|
| The geometry check reports several solid bodies | Remove the extra bodies (caps, bolts, reference solids) so the file contains one wheel solid, then choose Replace CAD file. |
| Run error · retry available | Read the diagnostic, fix the cause if one is given, then choose Retry / continue run. The same file and load snapshot are reused. |
| Run error · stopped | Read What to do next in the diagnostic. Start a new analysis once the cause is fixed. The credit was released. |
| A run seems stuck | Open the Solve Queue, select the run, and check the latest stage in the Job Inspector. Keep ForgeNode running. |
Viewing results
| What you see | What to do |
|---|---|
| Analysis complete · result unavailable | Do not run the analysis again. Check or update ForgeNode, then reopen the run. On the project page, try Recover local result. |
| The 3D view keeps loading | Open the result on the workstation that ran it, with ForgeNode running. Use Retry original 3D result. |
| Only the numerical summary is shown | You are on a different computer from the one that ran the analysis. The 3D fields are stored on that workstation. |
| FEA FAILED | This is an engineering verdict, not an error. Review the hotspots, safety factor, and load case, then strengthen the design. |
| Download PDF Packet is disabled | Reports need a verified result. Wait for verification to finish, or open the result on the workstation that ran it. |
Contact support
Open Support from the account menu, or go to Support, and choose New request. From a failed run, Get help with this run in the Job Inspector attaches the run for you. Replies appear on the request and as an unread count in the account menu. If you cannot sign in, email info@loudgears.com.
Include:
- the project ID and the Operation or job ID (from the Job Inspector);
- the ForgeNode version (from the dashboard or Download ForgeNode);
- the exact message and the last stage shown.
Do not send your CAD file unless support asks for it and your organisation allows it.