OTOY Forums

I am not sure, but I think that you would have to simply remame the folder and the python file inside, as they have same name whatever the version is and so it is confusing to Blender.

kavorka wrote:Is it possible to have both 1.17 and 2.02 installed, so we I can check which one I want to use? Right now it seems like it is either one or the other.

You'd have to rename several variables and tags inside many files. Too much annoying work.

I just use 1.17 and export separately geometry or camera, depending on needs. If in this 2.02 version all that was changed is commenting out some lines, then it doesn’t work any differently. It's not fixed, just disabled.

Do animations work with 2.02?

I was trying to use 1.17 and do a cam update, but it deleted my materials like rendering the images does.
So I was gonna try with 2.02. Problem is we have our scripts on a dropbox, so if I replace it with 2.02, my coworkers get updated automatically and they need 1.17 for their workflow.

kavorka wrote:I was trying to use 1.17 and do a cam update, but it deleted my materials like rendering the images does.

This shouldn't happen. Check if you have "write materials into ocs" enabled. It should be disabled

Also, how do you create materials in Octane? Do you just tweak the default ones (integrated into the .obj node), or do you create separate nodes/macros? I do the latter, because it's much more flexible.

If I try to render the image, the whole .ocs gets corrupted - it doesn't even load. Maybe you are using some other version than 1.17? (yeah, the situation is a confusing mess )

I dont have it enabled.
It loads but deletes everything but one material for me.

I have a question, If you have 2 render targets, each with a different camera node and click update camera, what node does it update?

kavorka wrote:I have a question, If you have 2 render targets, each with a different camera node and click update camera, what node does it update?

None. It will update the camera node that Octane uses as default when you click on a mesh node. Whatever camera node is connected in the "preview configuration" macro. Which seem to be outdated now in 1.5, and called "old preview configuration".

Thanks Matej you are great.

A clarification: this thread is still stickied, but the unofficial plugin version posted here is obsolete.

The latest version, that properly works for Octane standalone 1.5 & 2.0 and has support for particle export incorporated can be found in this thread: Community Plugin 1.50 - fixed for Octane 1.5+

The version here is tagged as 2.02, but is older an not really fixed, than the version (currently 1.51) in the above link. Can some moderator un-sticky this thread and sticky the one in the above link?

Hello,
I am trying to export a particle system with the plug in and I cant...
This is the error I get:
I have exported really high detailed geometry for that scene and it exported perfectly!
Could someone help me on that PS issue? (note: it renders fine in the plug in it just does not export to standalone)
Thank you in advance!
Stelios

you mean you have the official plugin?
If so, export it as alembic, it actually exports everythin from the particle system. The unofficial plugin doesn't which means that the result in Octane isnt always the same as what you see in Blender (unless you only useg the settings that get exported.