OTOY Forums

kartata wrote:Hey,

first time user here. Really love it so far. Has been running quite stable, despite a few crashes.
My question: Am I seeing this right, that in this developement stage the procedural nodes and shaders and OSL textures don't work? Or is it just me?

Best,
David

It’s only OSL shaders added by the user or loaded after octane starts. Will be fixed soon as per the FAQ, but otherwise all other procedurals work as they do on cuda.

Goldorak wrote: It’s only OSL shaders added by the user or loaded after octane starts. Will be fixed soon as per the FAQ, but otherwise all other procedurals work as they do on cuda.

I am not sure, if I am doint it right but the C4D-nodes don't seem to work for me either. Gradient or noise will do nothing of I plug them into the diffuse, contrary to the Octane gradient or noise which work just fine.

kartata wrote:

Goldorak wrote: It’s only OSL shaders added by the user or loaded after octane starts. Will be fixed soon as per the FAQ, but otherwise all other procedurals work as they do on cuda.

I am not sure, if I am doint it right but the C4D-nodes don't seem to work for me either. Gradient or noise will do nothing of I plug them into the diffuse, contrary to the Octane gradient or noise which work just fine.

That might be a different issue then. Can you share a screenshot?

Goldorak wrote: That might be a different issue then. Can you share a screenshot?

Sure thing!

kartata wrote:

Goldorak wrote: That might be a different issue then. Can you share a screenshot?

Sure thing!

Ok I see the issue - it’s using the OSL version of the maxon noises which were added in 2020.1 - and as noted in the FAQ, these have been temporarily disabled until PR2. For PR1, you can turn off “use osl” in the settings for maxon noises and it should then render the noises to a texture, which will work the same as in Octane 2019 and earlier.

Sweet, thanks!

Octane X is great. Even at such an early stage of development! There is applause for that
However, I have a problem with the preview resolution in the Octane Live Viewer Window. In my MacBook Pro 16 ", which has an approx 4K screen, this preview has a resolution of almost 1800px, where on a normal Full HD monitor it will be around 700-800px. And this resolution translates into the preview rendering time. Setting the resolution to 1000x1000 px rendering time of course gets shorter, but the render window is too small to see details.
So I have a request, is it possible to set the settings to scale the preview to 2x? So that the Retina screen does not display the image in accordance with its pixels, which are simply too small.

For some reason , Octane won't let me navigate in the Live Viwer using the Mighty Mouse middle button. Any ideas why? I can rotate and zoom, but not pan. Be great if we could have our own button set-ups for this.

Just wanted to add how good this version of Octane/C4D is. It crashes sure, but it's SO much more stable than before. Just gobbles up huge scenes, and is a joy to work with. I'm only using a single RX 5700XT (at the moment) and it's already a game changer over C4D's Physical renderer. How are other Mac users finding it?

—-Duplicate post, sorry——

Hello.
I'm so glad to meet Octane X.
I just wondered that the next step of my computer setting. I have a Mid-2015 Macbook Pro which is quite old.
I'm considering buying new stuff between eGPU (5700XT) and latest Macbook Pro (AMD Radeon Pro 5500M with 4GB).
I don't know how 5500M is good compared with 5700XT. But my laptop is quite old anyway. so that's why I'm thinking about buying a new MacBook pro too
*Sadly, I can't buy both