Burkhard / SurfingAlien
Thanks for the testing - I suspected that the Octane PDF Guide was wrong - here's what I dragged up from the net about Mac command lines
Because the shell interprets 'words' (alphanumeric strings separated by spaces or tabs),
you need to use
either "escape" spaces or other characters with a backslash: cd /Mac\ OS\ X/abcor type it all with "quotes": cd "/Mac OS X/abc"
So the Octane Guide PDF is completely wrong
with its !!! cd \"/Mac OS X/abc\"
The \" tells the Unix shell to take the quote character " as an actual " within the text and NOT a 'wrapper' to start reading a 'single string with spaces' until it finds the next closing one - such as a file-path***...
So I will now adjust my Mac codings to have NO escaped quote characters ["] - hopefully this will now make everything work for you Mac users.
It'll be in a new beta-i
topic - watch out for it later today...Incidentally
, when you run a Render Frame
[or animation] the exporter checks to see if the specified .ocs project file exists [path+name+.ocs] - if it does not then it is made automatically for you - that's the function of the 'octane_new' .cmd/.command file you might find in your project folder- it is doing nothing 'wrong' when it opens and immediately closes the new .ocs project - it's the only way to get it to make the .ocs file if it's missing, using a basic setup, but then continue separately with the rendering using that .ocs file via the octane.cmd/.command
file, because the command line arguments must differ in the two cases. You should not
get this making+immediate_closing
again when rendering your project, if
the .ocs file exists. If you already have a .ocs file that you have linked to using the Project Configuration
section Use Existing Project
button then no '_new
' command file should get made as it's never needed...