Hi,

It seems related to Bone/Skin, if you disable/re enable the Skin object it stops to blink, can you confirm?

ciao,
Beppe


Hey, thank you for checking! And yep, so it seems like deformers in general might be a factor? Disabling Skin stops the restarts, but adding e.g. a Displacer with a ...

I'm currently fighting one of these cases where the LV constantly restarts a rendering, making it frustrating (a bit of a dice roll) to preview render some scenes.

From what I can tell, this particular case seems to be related to the combination of Vertex Maps on skin deformed geometry? Noticed it ...

Hey, just to make sure it doesn't get lost I wanted to add my request regarding updated support for the Insydium plugin here as well.

The issue is basically this:
The new nxEmitter is not recognized by the Octane Object Tag, so particles can't easily be rendered as geometry like before.
The ...

Hey, just to make sure it doesn't get lost I wanted to add my request regarding updated support for the Insydium plugin here as well.

The issue is basically this:
The new nxEmitter is not recognized by the Octane Object Tag, so particles can't easily be rendered as geometry like before.
The same ...

Hey, I believe the download links still go to the 2026.5 version of the plugin, not yet the new Alpha?

Hey all! Last week, there was a new xParticles / Insydium public beta released - unfortunately the new nxEmitter doesn't seem to be recognized by the Octane Object Tag, so particles can't easily be rendered as geometry like before.

The same issue applies to the Instance Color and Instance Range ...

@Tim0042:
We have changed the way log works.
The specific message is a warning, nothing serious, but I'm with you that shouldn't be there, thanks for the report!
Aah, ok! Thx, that is very good to know - trying to optimize a scene and I wasn't sure if I need to worry about that message. But then ...

Hm, creating a Fog Volume (via the button) in an empty scene and then rendering brings up a message in the log: "The size of the volume array attributes does not match. They will be ignored."

This is not a message I remember from working with volumes in the past, though I could be wrong. What is ...

What about using two Output AOVs?
One with color correction for Live View preview, and the other without it for compositing in post.

You can use the same nodes connected to both Output AOVs, and add the color correction only on top of the first one.

ciao,
Beppe


That would work, true - though ...

Sorry, I cannot reproduce the issue.
Output AOVs are untonemapped, so you need to apply the same color conversion with layers, to obtain the same result you have in Main pass, and Live View color dropdown menu shouldn't have any effect on Output AOVs :roll:

Could you share an example scene that ...