Forum rules
Before posting a bug report, please check the following: 1. That the issue has not already been disclosed 2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone) Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it. A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.) B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.) C. RAM Capacity (i.e. 6 GB) D. Nvidia driver version (i.e. 7.50, 7.5.22) E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.) F. OctaneRender plugin version (i.e. v2.25 - 2.21) G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
There is an issue with Cryptomatte/CryptoObjectNode pass. It works fine when rendering mode is set to Update scene. When you set it to Full scene reload, the name of the objects (their id or however you call it) changes in every frame so its pretty much unusable for animation. Attached is a preview rendered from AE.
This problem can be related to the multi-thread scene extraction feature. Unfortunately, if the scene is extracted from multiple threads the order of the objects among the frames is not guaranteed, so all the cryptomatte IDs can change. Can you please try to disable this feature in the Octane ROP node to check if it helps?
Hmm, the other problem can be that your scene doesn't have a constant number of objects or instances along the sequence, something that can also break the cryptomatte IDs.
Thanks, -Juanjo
Last edited by juanjgon on Tue Nov 05, 2019 5:54 pm, edited 1 time in total.
Ok. So i tested it with just a simple rotating box. The same thing is happening as with a more complicated scene. Unfortunately i cannot test it in standalone cause 1) i don't really know how to assign different object ids (importing alembic and creating object pins either doesn't work or i'm just stupid) and 2) using it is giving me headaches.
Probably you are going to need to used the instanceID buffer even while working with conventional objects due to the internal plugin architecture. The instanceID should be constant among the frames while rendering in full scene reload mode if you have the multi-thread scene extraction option disabled.