OctaneRender™ for Blender 1.33 - 4.0 beta Win [OBSOLETE]

[Sixthlaw]

Hey There,

I am having a currently having an in issue in regards to saving with an earlier version of the Blender-Octane program (1.30). Now when I open this in 1.33 it just comes up with the "error: check console for more messages". I am currently working on a major client project so it couldn't have really come at a worse time! :O

Is this due to the way I have installed the new plugin and programs or does this happen with files from the last build? I would love some help!

Regards,

Sixthlaw

[JimStar]

I am currently working on a major client project so it couldn't have really come at a worse time! :O

Never ever use the testing major versions of any software on currently worked urgent projects.

when I open this in 1.33 it just comes up with the "error: check console for more messages"

Please, check console for more messages.

[Sixthlaw]

Hey Jimstar,

Thanks for the quick reply.

I understand that I shouldn't be using the Dev version for Projects - I would also like to mention how awesome I think your work is and my massive appreciation for your contribution you have made to octane! More people post problems here than appreciation, so that's mine!

In regards to the error Message, I have attached it to this post. Just to be clear, the entire scene was working fine in the previous version and all textures/materials were created using OCTANE texture and material nodes. All objects in the scene are still using those nodes though, which makes me confused as to why its producing this error...'

have I missed something?

Regards,

Sixthlaw

[JimStar]

These warning messages are not errors. They are just for your convenience, to let you know that not all materials in the scene are Octane nodes... It does not interfere with render, just default material will be rendered in this case.

So, the only error here - is in the second screenshot at bottom. Octane complains here that it can't find the image files of textures in these paths. So, just check that the needed image files are present in these folders.

[MattRM]

I have been using the alembic export feature with great success. I have notice that both thinlens and orthographic transfer over to octane standalone but if i use the panolens in blender, the alembic node in standalone is without a camera pin.

So im not sure if the blenderoctane is not exporting the panolens data or standalone is not reading the panolens data in the alembic file?

Or some way to switch to the pano lens once in standalone.

Hi r-username,

How do you do to make the Alembic export working ?

Thanks,

Matt

[MattRM]

Hi all,

Oki, I found was only possible to export Alembic file in /tmp\... with export_alembic name only, and also write file from rendering (seems to be png, but no need thems).
There is a way to put an output path for alembic file and possibility to choose the name ?

Thanks,

ps : work only with /tmp\ path for me.

[MattRM]

Hi again

I know I asked many things but will be possible to have the "layer map" tool in the Octane for blender ?
Could be really great too

I also saw that in alembic file, when you exported the scene with 2 GPU, if one is not enable, the exporter jumps 1 frame, like 1-3-5-7 instead of 1-2-3-4-5-6-7. Also, motion blur not works for animated object (transform object not deform of course)

Thanks,

Matt

[ephdot]

First Alembic Export & now Movable Proxies functional?! Hot diggity damn! Good form Jim.

[ROUBAL]

Hi, thank you very much for all these improvements. this said I encounter a big trouble with the Instances unofficial exporter. I posted a report in the link below, but as this problem occurs only with the Blender 2.69 for Octane version and didn't occur in early versions, it may have something to do with the behaviour of Blender for Octane. Specially because the addons install seems to chose a different path than the one specified by the user when attempting to install the instances exporter addon !

Please look at my report with screen shots on this page :

http://render.otoy.com/forum/viewtopic. ... 51#p173151

Thanks in advance.

Philippe.

[JimStar]

ROUBAL
Sorry, I have no time to debug all non-official scripts which have some issues, but at first glance looking at your screenshots I see that it's not the problem of this plugin. It is the script's developers task - to not interfere with official OctaneRender plugin namespace inside Blender. E.g. - only Otoy has priority to use "octane" name for render-settings object (or any other objects), and if some script developers decide to use the same instead of e.g. "octane_instances" of "octane_export" - you will get into troubles. But not the official plugin is cause of these issues. And it's not the official plugin's task - to change its namespace to let some script to work...
Those things are easy to fix, you just need to ask the script developers...