OTOY Forums

Painting textures using BodyPaint doeasn't update in Octane LV even with Check Paint textures turned on. And yes, I'm using C4D Bitmap node. I reported this year ago... Every time there is need to restart LV to see changes.
Also painting on Octane materials doesn't work at all.

Changes in Bitmap node ( C4D Baked ) doesn't update in OGL view.

Switching painting to Bump channel after painting in Color channel, cause that Octane loosing changes that were done in Color channel.

Generally BodyPaint 3D is not compatible with Octane.

SSmolak wrote:Painting textures using BodyPaint doeasn't update in Octane LV even with Check Paint textures turned on. And yes, I'm using C4D Bitmap node. I reported this year ago... Every time there is need to restart LV to see changes.

paint Octane.png

Also painting on Octane materials doesn't work at all.

Changes in Bitmap node ( C4D Baked ) doesn't update in OGL view.

Switching painting to Bump channel after painting in Color channel, cause that Octane loosing changes that were done in Color channel.

Generally BodyPaint 3D is not compatible with Octane.

Update detection is not available.

aoktar wrote: Update detection is not available.

In other words, C4D's API doesn't provide third party developers with notification when the app has changed the content of a texture, so Octane doesn't know that there is anything that needs updating.

I'm guessing that C4D doesn't even change the source file right away, instead directly editing the data stored in the texture cache for the sake of interactivity, then writing the changes to disk once the active edit concludes. If this is the case, then Octane couldn't even monitor the source files for changed modification time stamps.

That's all just speculation on my part, but seems a reasonable internal pipeline.

frankmci wrote:That's all just speculation on my part, but seems a reasonable internal pipeline.

I wonder if Redshift support it. But there is another issue - there is no way to painting on Octane materials directly in viewport.

SSmolak wrote:

frankmci wrote:That's all just speculation on my part, but seems a reasonable internal pipeline.

I wonder if Redshift support it. But there is another issue - there is no way to painting on Octane materials directly in viewport.

Now that Redshift is under the Maxon umbrella, I wouldn't be surprised if they gave that engine special access beyond the public API, but that's purely speculation. I haven't actually tried it.

I suspect that painting on Octane materials is the same issue as real time viewing of painted C4D materials. There's a whole toolbox in C4D for accomplishing Bodypaint functionality. If C4D doesn't provide the hooks to access them, though, then OTOY would have to build their own implementation, which really isn't their core market. Many other tools already do that, and do it very well.

I am curious what the situation is with all the other Octane hosting 3D programs. Maybe there are some that give greater access to the native tool set than C4D does. But at this point in my 3D career, it's unlikely I'll switch again.

SSmolak wrote:

frankmci wrote:That's all just speculation on my part, but seems a reasonable internal pipeline.

I wonder if Redshift support it. But there is another issue - there is no way to painting on Octane materials directly in viewport.

It's same issue, you notified that recently. But I tried to do it years before, no any mechanism to tell us ıt's painted or accept it for painting. 3rd part shader are very limited on several areas. Still NO any example or support to improve these for viewport.

Standard Material issue - all parameters except color doesn't update in LiveViewer constantly on all channels - it update only if mouse button is released.

SSmolak wrote:Standard Material issue - all parameters except color doesn't update in LiveViewer constantly on all channels - it update only if mouse button is released.

std.jpg

It works well here, please check your setup again

aoktar wrote:It works well here, please check your setup again

Very strange. After restart sliders works fine Something was blocked them before...


Does it necessarily to automatically switching to 2x2 subsampling when there is some time of interface freeze for example during loading new HDR ? I have set Perf time to 1000ms but when large image is loaded it still change subsampling method.

I am not sure if this is a common Issue or it is new.
Working with Cryptomattes and DoF.

I am Painting a country in a color on the map and get these ugly edges.

It´s set to Material Node Name.
Info Channels are 1024.