Cinema4D version 2022.1-XB3-(R4) (Experimental) 23.09.22 Tweet

[aoktar]

I'm very sorry but I found another interface issue caused by Octane plugin.

If Previews -> Materials preview is turned off it cause that Cinema's viewports not refresh - totally. They not refresh even polygons selections.

I thing that this option don't work :

OCT_OGL_OFF.jpg

Please see video

yes but clicking to active view will redraw the viewport. Also why do you disable all preview options? They are critical to have for the correct workflow.

[SSmolak]

I'm very sorry but I found another interface issue caused by Octane plugin.

If Previews -> Materials preview is turned off it cause that Cinema's viewports not refresh - totally. They not refresh even polygons selections.

I thing that this option don't work :

OCT_OGL_OFF.jpg

Please see video

yes but clicking to active view will redraw the viewport. Also why do you disable all preview options? They are critical to have for the correct workflow.

Because I found that disable them there is much faster respond with changing material parameters without delay.

EDIT : ok but there is workaround - just enable and disable this option and everything is ok - but only for some minutes.

[SSmolak]

Vertex map doesn't update in realtime even if "check paint textures" is turned on. It refresh only while changing this box :

[Meet]

Solo node not working when using Standard Surface Material

UPDATE EDIT - Restarted, works fine now.

[azumbrunnen]

It crashes super frequently. Similar to PR14 builds. When can we expect windows level reliability for octane on mac? speed isn't the major issue here, but reliability is a very big problem. Opening up the graph editor feels like flipping a coin, you never know if it will crash.

Tested both on my iMac Pro (PR14) and M1 Max (this build).

[aoktar]

It crashes super frequently. Similar to PR14 builds. When can we expect windows level reliability for octane on mac? speed isn't the major issue here, but reliability is a very big problem. Opening up the graph editor feels like flipping a coin, you never know if it will crash.

Tested both on my iMac Pro (PR14) and M1 Max (this build).

It's not tested much on my side for Macs. Mostly it's built from Windows codes, we should expect it should be solid as Windows. It should be a different problem if it's crashing. Share some detailed information for crashes, like bugreports and steps that causes this.

[azumbrunnen]

This is not meant to sound bad or something but how can you build a product without testing?

I'd love to help but I mean it crashes SO frequently that I wouldn't know where to start and it's been this unstable and unchanged since PR14. I thought it was gonna get better but it keeps crashing independently of the machine and C4D version.

A good way to try is to use noises or build any more advanced material. As long as you stay away from the node editor it is relatively stable. It's as soon as you start building materials that you will get a lot of crashes.

[aoktar]

This is not meant to sound bad or something but how can you build a product without testing?

I'd love to help but I mean it crashes SO frequently that I wouldn't know where to start and it's been this unstable and unchanged since PR14. I thought it was gonna get better but it keeps crashing independently of the machine and C4D version.

A good way to try is to use noises or build any more advanced material. As long as you stay away from the node editor it is relatively stable. It's as soon as you start building materials that you will get a lot of crashes.

This is still a development/test build and improves as feedback quality. Also there are a lot of users and stuff from team to test it! I'm not in love with Macs to use it for long hours, that's my way to develop the things. Do it in Windows and build in Osx, as I said there should be C4d+Mac related issues. Better to ping someone from support team.

[azumbrunnen]

I don't mean to be unconstructive. What's the best way to help? I'd love for the node editor and X to be as stable as its windows counterpart.

One thing I noticed is that I seem to be unable to use any vertex maps. Cinema crashes immediately when trying to save a scene with a material that uses a c4d vertex map to mix materials.

[SSmolak]

Cinema crashes immediately when trying to save a scene with a material that uses a c4d vertex map to mix materials.

But Mix Material is obsolete. You should use Composite or Layered Material instead. I think that Mix Material should be removed from materials group and move to the down of the list to the "Compatibilty Group".