Octane’s native color picker can definitely be a bit clunky when you’re trying to sample precise values directly out of complex reference images or texture sheets, especially with color spaces factored in.
When the internal sampler is giving me a hard time, I usually just drop the reference into an ...

Finding efficient ways to bring SketchUp models into Octane while keeping things clean can be a bit of a headache, so this is super helpful.

I can confirm the adaptive sampling part is a bit confusing in the demo build. It might be worth testing the same scene with a fresh default kernel and checking if any older render settings carried over. If it still doesn't kick in, it definitely sounds like something the devs should look into ...

I've seen similar issues before, and in my case it helped to double-check that both the plugin and Octane versions matched exactly. If everything is up to date, try testing with a fresh scene and reset the render settings to rule out a project-specific problem. That can save a lot of troubleshooting ...

The render node part is actually a huge bonus that a lot of new users overlook. If you already have an older machine sitting around, using it as a render node can give you a pretty noticeable speed boost without needing another full license. Makes the subscription a lot more flexible than it first ...

Good to know. Rendering issues can be really frustrating because they often look like a software bug when they're actually caused by a setting or compatibility problem. It'll probably save someone else a lot of troubleshooting time.

A lot of weird Octane issues end up being driver or plugin-version related more than the actual scene. I’d try a clean GPU driver install first and also make sure the Octane plugin version exactly matches the standalone/core version. Disabling any overclock can help too - Octane tends to expose ...