Version 3.05.3 (13.01.2017)

[Liketheriver]

Hi Guys, Sorry I can;t seem to get the signature to update so it shows specs.

Win10, 4 x GTX1070 hybrids. Have tried combinations of priority, I tried one GPU at a time being low as I wasn't sure I was selecting the correct one. None of the combinations I tried made a difference.
I have a lot of Geo in these scenes, but as the whole scene sits in Octane memory that is why I am curious why there is so much lag when changing light brightness. I don't understand the mechanics of it, so I apologise if my assumptions are in error, but if the mesh emitter/area light is in memory, and I change the brightness, everything happens really slowly even on 4x 1070s. I certainly can NOT interactively drag the slider of a light brightness, I have to type a value, and hit enter, then touch another part of the UI as Octane seems to be one click/tap behind what I am doing. I am now in the habit of setting every value twice just so I can see the update. Sometimes when I update, say, the power of an HDRI in a heavy scene, this doesn't update for more than 2 clicks, so then I go and adjust an area light too bright because the HDRI change has not updated in the LV right away. It's very frustrating.
The simpler the scene, the less this happens. But it doesn't take a lot in the scene for this slowdown to start being a hindrance. I'd post a scene file but this is commercial work and I cannot. But pretty much all my scenes use cloners, can't do lot in C4D without these guys, so if this UI issue is a C4D thing it looks like I have no hopes of seeing a fix soon.

Can you kindly clarify please if I disable the object update, will I be better able to interactively adjust lights? As lights are mesh emitters (geo) I thought this would need to stay on? Or is it not classified as a geo change?

Thanks, and apologies again if I am asking the wrong thing or misunderstand how the engine works.

Hi!

how big is this hdri? sometimes with big files it get laggy, I notice something similar with 15000*7500px hdri, if you have enough Vram try to disable Out of core textures, so the files are keeped totally in vram, it helped me a little. for the cloners try to optimize, and use istances, note that octane can handle only 1 level of istance, for example, it cannot render an istance of an istance, so avoid to put istanced object inside other object you want to istance.

[zinogino]

This looks very interesting Ahmet,

The grouping is very welcome.

I can only think of a few minor improvements that would help me when using the NE.

• 1. Optimize (auto scale) for nodes would be helpful to quickly reduce the size of nodes based on their content:
  
  Here's that function in Xpresso:
  
  
  My god, yes please have this function.
• 2. Gradient previews, similar to how the C4D gradient node displays when you enable previews:
  
  
  Top is how Octane gradients preview, below is the C4D gradient
  
  
  Maybe something like this would be nice, and not having the square preview so it fits the shape of the node better too.
• 3. Undo for the NE in general, not just the main commands, I mean layout and connections.
• 4. Have the attributes/parameter pane collapsible with a single shortcut/button would be really helpful too:
  
  
• 5. Snapping to the grid, or maybe an Align to Grid command like in Xpresso:
  
  
• 6. Detatching node connections is tricky at the moment, you can only do it by click dragging the input end and releasing.
  Having an option like Alt+click or Shift+click to delete the connection would be cool. Houdini has a useful one which is shake to detach, that's one I miss in every other nodal interface when it's not there
• 7. Maybe rounded corners and a 1px grey border for unselected nodes, just as minor cosmetic improvements would help.

Let me know if you want me to clarify anything, those are just things that have occurred to me when using it.
Keep up the good work!

cheers,
brasc

[Oleg]

Hey, a tiny feature request for creating new materials within layers

[aoktar]

Hey, a tiny feature request for creating new materials within layers

Ok i'll see how possible.

[rwalker]

Sorry if this has come up before, but here's the problem: I just updated from Octane 3.03.3r1 (which has been stable and perfect for many weeks for me ) to 3.05.3 to see how it would work. I did a test render of a few frames from a recent project. There is a significant difference in brightness/gamma between renders done in the two versions. Am I missing something? Nothing changed in the project, the only change was updating OctaneRender and c4doctane plugin folder.

I am running C4D Studio R16.050, nVidia GTX780 + 780ti with latest drivers.

[aoktar]

Sorry if this has come up before, but here's the problem: I just updated from Octane 3.03.3r1 (which has been stable and perfect for many weeks for me ) to 3.05.3 to see how it would work. I did a test render of a few frames from a recent project. There is a significant difference in brightness/gamma between renders done in the two versions. Am I missing something? Nothing changed in the project, the only change was updating OctaneRender and c4doctane plugin folder.

I am running C4D Studio R16.050, nVidia GTX780 + 780ti with latest drivers.

Have you checked gi_mode in directlighting if you're on?

[rwalker]

Sorry if this has come up before, but here's the problem: I just updated from Octane 3.03.3r1 (which has been stable and perfect for many weeks for me ) to 3.05.3 to see how it would work. I did a test render of a few frames from a recent project. There is a significant difference in brightness/gamma between renders done in the two versions. Am I missing something? Nothing changed in the project, the only change was updating OctaneRender and c4doctane plugin folder.

I am running C4D Studio R16.050, nVidia GTX780 + 780ti with latest drivers.

Have you checked gi_mode in directlighting if you're on?

Well, this is using pathtracing.

[bepeg4d]

Hi rwalker,
maybe the "Surface brightness" option in emission nodes and Area lights?
ciao beppe

[miohn]

I also had to switch back from 3.05.3 to 3.05.1 because of that
massive difference in brightness when rendering a project made with 3.05.1.

Did not had to time to figure out what causes this!
Also rendering with PT.

regards
Mike

[rwalker]

Hi rwalker,
maybe the "Surface brightness" option in emission nodes and Area lights?
ciao beppe

The scene is lit only by Octane HDRI Environment. I am experimenting with color-correction in After Effects to try to match, thinking maybe it's just a gamma correction. But it's not that simple. Using levels, I can change gamma to 1.02, and output white to 29812 (from default 32768) I can get close but not perfect.

This is a problem if I need to update something due to client request and the new scene does not match the original in lighting.