Can't finish setting up Needle in Unity, multiple issues

Environment detials:
MacOS Sequoia 15.0
Unity 2021.3.37f1
Needle Unity Package Installer downloaded on 4/11
Needle Engine 4.3.2
Not logged into Needle Cloud
Using a fresh Sample Scene created “With Template” from the Welcome window

The error I’m seeing in the Project Validation window:
“No supported version of Node.js found on your machine. Please install Node.js 18 LTS or 20 LTS. You may need to restart your machine after installation. You currently have Node.js v8.9.1 and NPM 5.5.1 installed.”

I tried installing Node, didn’t fix the problem. Note, I already have NVM installed and many versions of Node that satisfy minimum requirements.

Other issues:

In the Validation Window, there is a section for “Additional npm search paths,” but the input fields are all read-only, no matter how many I add.

From Player Settings / Needle / Needle Engine, clicking Open Cloud works, clicking Create Account doesn’t do anything, and clicking Login doesn’t do anything. There are no errors in the console. When clicking Login, a console debug statement just says “login:” without any other context.

The tutorial linked from the Welcome window is out of date: https://youtu.be/3dB-d1Jo_Mk

Hello Aaron Collegeman! Let’s address your issues one by one.

  1. Node.js Issue: The error indicates that you need to update Node.js, as your current version (v8.9.1) is outdated. You should install Node.js 18 LTS or 20 LTS. This can usually be done via the Node.js official website or using a version manager like nvm. After installing the correct version, restart your machine and verify the installation using the terminal:

    node -v
    npm -v
    
  2. Tutorial Link: If the tutorial linked is outdated, it’s advisable to check the Needle Engine documentation for the latest setup instructions or refer to the Samples Repository for updated examples.

  3. Cloud Features:

    • If the “Create Account” and “Login” buttons are unresponsive, try checking if your internet connection is stable. If issues persist, consider looking for updates to the Needle Engine package or reinstalling it.
    • Please check Unity’s Console and ensure no other errors are present that might conflict with the Needle functionalities.
  4. Additional npm search paths: If the input fields are read-only, this could indicate a configuration lock in the package. Ensure you have the necessary permissions in your Unity project settings, or try resetting your project and starting with the sample scene again.

If you still encounter problems, please share any relevant logs that might help diagnose the issue better. You can obtain logs from the menu item “Help/Needle/Logs”, which could provide further insights. Let me know if you need assistance with any specific step!

1 replies left - Get a PRO license for more AI replies.
thread_dZS25STgQN6ss3iLisQv1G0u
Reply to this message to continue the conversation

{
“ExportInfoGameObjectName”: “Export”,
“ExportInfoGameObjectIsEnabled”: true,
“UnityProjectPath”: “/Users/aaron/repos/StreetMesh/BrowserWebXR/Assets”,
“UnityVersion”: “2021.3.37f1”,
“SceneName”: “CollaborativeSandbox”,
“ProjectPath”: “Needle/CollaborativeSandbox”,
“ProjectDirectoryExists”: false,
“ProjectIsInstalled”: false,
“NeedleEngineInstalled”: false,
“HasNodeInstalled”: true,
“NodeVersion”: “v8.9.1”,
“NpmVersion”: “5.5.1”,
“TypescriptVersion”: “zsh:1: command not found: tsc”,
“HasTokTxInstalled”: true,
“HasMinimumToktxVersionInstalled”: true,
“RenderPipeline”: “Built-in”,
“GzipEnabled”: false,
“NeedleEngineExporterVersion”: “4.3.2”,
“NeedleEngineVersion”: null,
“NeedleEngineSamplesVersion”: null,
“NeedleEngineExporterPath”: “Packages/com.needle.engine-exporter/package.json”,
“NeedleEnginePath”: “/Users/aaron/repos/StreetMesh/BrowserWebXR/Assets/../Needle/CollaborativeSandbox/node_modules/@needle-tools/engine/package.json”,
“FileStats”: null,
“NeedleComponentsInScene”: [
“Needle.Engine.ExportInfo”,
“Needle.Engine.Codegen.ComponentGenerator”,
“Needle.Engine.Shaders.SkyboxExportSettings”,
“Needle.Engine.EditorSync.NeedleEditorSync”,
“Needle.Engine.Gltf.Experimental.progressive.NeedleCompressionSettings”,
“Needle.Engine.Components.SyncedRoom”,
“Needle.Engine.WebXR”,
“Needle.Engine.Components.OrbitControls”,
“Needle.Engine.Components.SpectatorCamera”,
“Needle.Engine.Components.SyncedCamera”,
“Needle.Engine.Components.ObjectRaycaster”,
“Needle.Engine.Components.XRRig”,
“Needle.Engine.Components.XRFlag”,
“Needle.Engine.Components.Deletable”,
“Needle.Engine.Components.SyncedTransform”,
“Needle.Engine.Components.DragControls”,
“Needle.Engine.Components.DeleteBox”,
“Needle.Engine.Components.BoxGizmo”,
“Needle.Engine.Components.Duplicatable”
],
“TypeCacheIsDirty”: false,
“TypeScriptTypes”:
}

Thank you for providing the detailed project information, Aaron. Here’s a breakdown of the issues based on the information you’ve shared:

  1. Node.js Version: You are still using an outdated version of Node.js (v8.9.1). You must upgrade to either Node.js 18 LTS or 20 LTS as previously mentioned. This is crucial since the Needle Engine tools depend on a supported Node.js version. Follow the steps to install the latest version from the Node.js website.

  2. Needle Engine Installation: It appears that the Needle Engine is not installed in the specified project directory (/Users/aaron/repos/StreetMesh/BrowserWebXR/Assets/../Needle/CollaborativeSandbox). You should verify the installation of Needle Engine and make sure that the paths are correctly set up in Unity. Ensure that the Needle package is properly imported into your Unity project.

  3. Typescript Not Found: The line TypescriptVersion: "zsh:1: command not found: tsc" suggests that TypeScript is not installed globally. To install TypeScript, you can run:

    npm install -g typescript
    

    This will ensure that any TypeScript functionality is available for your project.

  4. Needle Engine Samples & Components: It appears you have several Needle components in your scene, but since the Needle Engine is not installed, it may lead to issues with those components. Ensure the samples repository is correctly imported and configured in your project.

  5. Scene Directory: The ProjectDirectoryExists is marked as false. Ensure that the directory requested by the project is created and accessible.

  6. Permissions and NPM Issues: If there are read-only errors when trying to add npm paths, consider checking permissions or running Unity with elevated privileges.

After addressing these specific issues, please restart Unity and see if you can proceed. If problems persist, please share any new error logs or messages you encounter!

0 replies left - Get a PRO license for more AI replies.
thread_dZS25STgQN6ss3iLisQv1G0u
Reply to this message to continue the conversation

None of this has fixed my problem.

Hi Aaron_Collegeman, I’m sorry but I can’t help you right now. You have reached the maximum number of replies. :thinking:. Please try again later or get a PRO license for more AI help.
**

These versions are very old. Have you tried uninstalling old versions of node via nvm?

The additional search paths should indeed also resolve the issue. You should be able to add a new item there and paste your path to the right version.

Hi @Aaron_Collegeman in addition to Felix reply: Do you actually also have Node 8 installed via nvm?