OTOY Forums

wireframex wrote:2015 SP2

Thanks,
i hope, with the quick preview, you mean the render region. If this is correct, there is a bug.

The shaders must be replaced, yes. thats because you can use compounds.
The old shaders had some inputs, which were not the real parameters i had used for the Octane shaders.
It would be to complicated to switch it across a shader compound. For now all inputs are real inputs, which are also used to generate the shader nodes.

This can also be the problem with the material preview.
Try to close Softimage, start it again, use a clear scene and make some materials, i think then the shaderball is working.
The problem here, Softimage seems to save some layouts and/or parameters of the shaders with the scene.

face

face wrote:

wireframex wrote:2015 SP2

Thanks,
i hope, with the quick preview, you mean the render region. If this is correct, there is a bug.face

Yes it is the quick preview [q]

face wrote:Try to close Softimage, start it again, use a clear scene and make some materials, i think then the shaderball is working.
The problem here, Softimage seems to save some layouts and/or parameters of the shaders with the scene.
face

1- I changed preferences for Octane renderer engine.
2- Just created scene with a simple sphere and a new material from Material Manager
3 - The only things I can change are the colour and image map --> Reflection/Glossy for example are not viewed in the shaderball view

wireframex wrote:1- I changed preferences for Octane renderer engine.
2- Just created scene with a simple sphere and a new material from Material Manager
3 - The only things I can change are the colour and image map --> Reflection/Glossy for example are not viewed in the shaderball view

I have made it and this is the result:

I don't have this result at all.
I will send you my result this evening.
Phil

wireframex wrote:I don't have this result at all.
I will send you my result this evening.
Phil

Can you attach a scene file, you can send it as pm?

I can also make a build wich will save the shaderball as an ocs file, which you can open in Octane standalone, to see how it looks.
For this you must say me a save location because it is hard coded, something like "d:\tree\"

You can also take a look into the Octane log, there should be some errors if some connections or parameters are invalid.

face

I can also make a build wich will save the shaderball as an ocs file

At first ICE implemented
But export materials to ocs is cool. May be "C:\OctaneRenderTree"?

Gescort wrote:At first ICE implemented
But export materials to ocs is cool. May be "C:\OctaneRenderTree"?

Will have a look at it

Now i have solved the two issues with the imager, which had also affect the postpro shader, and the region.
Also instances are included.
But for now i haven´t time to make a build, will try it as soon as possible.

face

One question which interests me after the long time i had needed to make this version, how compares this to the old one?

face

All is ok

Found the pb in shaderball preference ...

Sorry
Phil

wireframex wrote:All is ok

Found the pb in shaderball preference ...

Sorry
Phil

Uh cool
Realy no problem, better it was your problem than mine. Much better

face