OTOY Forums

thanks a lot,
will try it this afternoon and I'll be able to tell you if the problem is solved.
thanks again

Great

Sorry, I take this opportunity, can you tell me if there is a plugin development that supports the instances?
I'm trying to solve the problem by grasshopper, with many difficulties!

Hi Sam,
i've a similar problem..here the string text..

There was an error parsing the command-line arguments:

Couldn't read argument value from string '8,02123006609122E-02' Argument: (--cam-pos-y)

USAGE:

octane [-t <node name>] [-m <string>] [-r <filename>] [-l <filename>]
[-n <filename>] [--imager-exposure <float>] [--daylight-sundir-z
<float>] [--daylight-sundir-y <float>] [--daylight-sundir-x
<float>] [--cam-lensshift-right <float>] [--cam-lensshift-up
<float>] [--cam-aperture <float>] [--cam-focaldepth <float>]
[--cam-fov <float>] [--cam-motion-up-z <float>]
[--cam-motion-up-y <float>] [--cam-motion-up-x <float>]
[--cam-motion-target-z <float>] [--cam-motion-target-y <float>]
[--cam-motion-target-x <float>] [--cam-motion-pos-z <float>]
[--cam-motion-pos-y <float>] [--cam-motion-pos-x <float>]
[--cam-up-z <float>] [--cam-up-y <float>] [--cam-up-x <float>]
[--cam-target-z <float>] [--cam-target-y <float>]
[--cam-target-x <float>] [--cam-pos-z <float>] [--cam-pos-y
<float>] [--cam-pos-x <float>] [-q] [-g <int>] ... [-s <int>]
[--output-exr-tm <filename>] [--output-exr <filename>]
[--output-png16 <filename>] [-o <filename>] [--film-height
<int>] [--film-width <int>] [-e] [--] [--version] [-h]
<filename>


Where:

-t <node name>, --target-node <node name>
Name of the render target node to render

-m <string>, --mesh-node <string>
Name of the mesh node to render.

-r <filename>, --relink-meshnode <filename>
Load the given OBJ mesh file into the mesh node given with
--mesh-node.

-l <filename>, --link-meshnode <filename>
Create a new mesh node from the given OBJ mesh file

-n <filename>, --new <filename>
Create a new OCS project file from given command line arguments

--imager-exposure <float>
Imager Exposure Amount

--daylight-sundir-z <float>
Daylight Sun Direction Vector Z Component

--daylight-sundir-y <float>
Daylight Sun Direction Vector Y Component

--daylight-sundir-x <float>
Daylight Sun Direction Vector X Component

--cam-lensshift-right <float>
Lens Shift Right

--cam-lensshift-up <float>
Lens Shift Up

--cam-aperture <float>
Camera Aperture Radius

--cam-focaldepth <float>
Camera Focal Depth

--cam-fov <float>
Camera FOV (degrees)

--cam-motion-up-z <float>
Camera Up Motion 2nd Vector Z Component

--cam-motion-up-y <float>
Camera Up Motion 2nd Vector Y Component

--cam-motion-up-x <float>
Camera Up Motion 2nd Vector X Component

--cam-motion-target-z <float>
Camera Target Motion 2nd Position Z Component

--cam-motion-target-y <float>
Camera Target Motion 2nd Position Y Component

--cam-motion-target-x <float>
Camera Target Motion 2nd Position X Component

--cam-motion-pos-z <float>
Camera Motion 2nd Position Z Component

--cam-motion-pos-y <float>
Camera Motion 2nd Position Y Component

--cam-motion-pos-x <float>
Camera Motion 2nd Position X Component

--cam-up-z <float>
Camera Up Vector Z Component

--cam-up-y <float>
Camera Up Vector Y Component

--cam-up-x <float>
Camera Up Vector X Component

--cam-target-z <float>
Camera Target Position Z Component

--cam-target-y <float>
Camera Target Position Y Component

--cam-target-x <float>
Camera Target Position X Component

--cam-pos-z <float>
Camera Position Z Component

--cam-pos-y <float>
Camera Position Y Component

--cam-pos-x <float>
Camera Position X Component

-q, --quiet
Start Application without splash and minimized window

-g <int>, --gpu <int> (accepted multiple times)
add GPU device to use for rendering (0 = first)

-s <int>, --samples <int>
Maximum number of samples per pixel (maxsamples)

--output-exr-tm <filename>
Output tonemapped EXR image file when maxsamples is reached

--output-exr <filename>
Output EXR image file when maxsamples is reached

--output-png16 <filename>
Output 16-bit PNG image file when maxsamples is reached

-o <filename>, --output-png <filename>
Output PNG image file when maxsamples is reached

--film-height <int>
Film height

--film-width <int>
Film width

-e, --exit
Close the application when rendering is done

--, --ignore_rest
Ignores the rest of the labeled arguments following this flag.

--version
Displays version information and exits.

-h, --help
Displays usage information and exits.

<filename>
.OCS Project scene file


OctaneRender

....thanks

any ideas??

I can tell you what the problem is, not necessarily how to fix it without the code infront of me...

Basically how this works is it uses the command line (cmd) to launch octane with certain parameters... So --cam-pos-y is trying to tell it the Y position.

However, the exporter isn't giving it a float (a decimal number), it's giving a string (since it has E-2) in it). Also I believe the comma could make a difference, though it may depend on where you are in the world and what language settings your pc has.

If I were having this problem (and I wanted to work-around it rather than solve it) (I don't actually use the exporter, I prefer to do it manually) I would reduce the number of digits in my camera position (in the Rhino properties panel) and camera target to a regular number, so your where yours would be '0,0802123006609122', Sam's plugin would read it as '8,02123006609122E-02'. I would suggest setting it to something more like 0,08 - where the plugin won't need the scientific abbreviation. Just remember that you'd need to make sure that that camera x,y,z and target x,y,z are all not being abbreviated.

TL;DR: Octane is receiving a string (alpha characters) in the camera position/target but it can only read a float (decimal number).



EDIT:
Sorry I just read the previous posts, it seems to be due to the comma, are you sure you've updated to the file that SamPage posted here? http://render.otoy.com/forum/viewtopic. ... 20#p102836

I am no expert of strings, even I do not understand much, but the plugin should have inserted it correctly ..