OTOY Forums

Hmm, no it is a new scene. Can validate that it indeed works?

I also got this new problem, with 1.00,1.01,1.02 and 1.03 that it kees asking for the .obj everytime I render a new frame or animation. So I guess I need to start fresh :O

edit * Seems another cleanup/reinstall fixed the problem!

Reinstall the plugin?

face

Yeah it worked.. Its strange, this is the second time this type of thing happens.. When suddenly things that usually worked, just doesnt work anymore. And Im always going through un-installing old plug ins, and check the addons folder etc.. Anyway, Im rendering away now

I've been experimenting with this plugin for a few days and it works great so far, thanks a lot for all the hard work.

I have one problem though. I can't get the SI camera to export properly with the scene. I reinstalled the addon twice and made sure I had microsoft visual C++ installed but so far no luck. The camera is really far away from the objects.

Is there some secret trickery involved I don't know about ?

I'm using Soft2Octane 3.03 with SI 2013 SP1 64.

Thanks,

- Ronald

another problem I've run into is that I have an Octane scene where several Obj's are merged into a geometrygroup node, and I can't get the group to render and load the animated object on every frame at the same time.

When I activate "overwrite existing project", it will the refresh the animated object on every frame but won't render the geometrygroup I've set in SI.

But when I deactivate "overwrite existing project" it renders the geometrygroup I've set, but renders the same object on every frame.

I also tried adding a "render target node" and setting that one in the Soft2Octane PPG in SI, but it makes no difference.

When I leave "mesh to render" and "render target name" set to default, it will sometimes render the right geometrygroup, but renders the same objects on every frame.

Did I run into some limitations ?

- Ronald

The camera should match perfect, only one thing which can be, is that the SI scene has an pixel ratio unlike 1.
You can check this, if you delete the camera interest and make the camera a parent of the scene root.
Or build a new one which match the other camera position and make the steps from above.
The camera srt in the transform ppg in Softimage should now match the camera data in Octane.

"Mesh to render" includes geometry groups. You can also set the geometry group name in this field.

If the scene isn´t to big, you can send it to me and i will take a look...

face

hey, thanks for the fast reply. I think I solved the camera issue. I suspect it was a wrong scaling preference in Octane. I assumed that when I leave the default to decimeters in both SI and Octane things should be fine, but after changing the prefs in Octane to meters the camera exported fine. Changing the units in SI doesn't seem to affect anything but the camera aperture.

Going to look into the issue with the geometrygroups and rendertargets tomorrow, probably a user error as well.

Another thing I ran into is that some ICE instances seem to export with a negative scale. I had some instances scattered on a ground mesh in a few scenes, and they all end up on the backside of the plane.

Hm, the scale should affect all. ICE, geometrys and cameras. Maybe there is something wrong.

The ICE prblem should be solved. Don´t know if the plugin is updated on the first side here.
Take a look 1 or two pages back, there should be a download of a dll which you can swap with the old one.

face

Ah thanks, I downloaded the one in the first posting assuming it would include the latest dll's.

I think the problem might be that I assume too much

- Ronald

Brilliant ! Replacing the DLL fixed the scaling problem.

Thanks, I owe you a beer or two

- Ronald