Oliver Hickman

the "start script" message doesn't seem to start any node process in Max. I cannot get any of the help or example files to start. No error messages in the console. If I double click on the script.node object it opens up the directory of the files so I assume it's not a missing asset issue. Anyone else having this problem?

the "start script" message doesn't seem to start any node process in Max. I cannot get any of the help or example files to start. No error m

start-script-not-starting-script

Platform? System? Errors in the Max window?Support Info?

Maybe best to drop a line into support with as many details as you can muster

Ah ha! Turns out my Node installation was all kinds a screwed up and a bit out of date. Fixing this as solved my problem if there's anyone else out there with this issue.

Similar problem but I restarted Max and it fixed it.

ships with an internal bundled version of 

Therefore it should be mostly decoupled from your local install unless otherwise stated using the 

attributes. The latter is not really relevant though for most use-cases and we attempt to stick with 

 stream. If you are curious about the binary versions used, they are available via the 

) to get an insight into why your scripts are failing as it's otherwise very hard to pin point any potential issues to 

 itself or the referenced script on disk. This is especially important if you are using previously worked on 

Projects that might have dependencies installed on disk that might not match in terms of the

version being used, compiled against etc.

But yeah, glad to read you guys have it up and running. We are interested in hearing what people use it for and highly support sharing within the community.

Node For Max ships with an internal bundled version of Node and NPM . Therefore it should be mostly decoupled from your local install unless otherwise stated using the @node and @npm attributes. The latter is not really relevant though for most use-cases and we attempt to stick with Node's LTS stream. If you are curious about the binary versions used, they are available via the script status message (for convenience use check the node.script help file and check the node.debug 'Global Stats' tab).

In general we highly advise to use the node.debug utility (check the Node For Max Guide) to get an insight into why your scripts are failing as it's otherwise very hard to pin point any potential issues to node.script itself or the referenced script on disk. This is especially important if you are using previously worked on Node Projects that might have dependencies installed on disk that might not match in terms of the version being used, compiled against etc.

Perhaps you should had a 'node' forum section... or it will be quite mixed with javascript subject...

start script not starting script