The plugin will be re-written as soon as the Bifrost 2.5 becomes the default standard installation done by Maya installer.

https://knowledge.autodesk.com/support/maya/learn-explore/caas/CloudHelp/cloudhelp/2023/ENU/Maya-WhatsNewPR/files/GUID-1A978C1B-76AB-4324-B786-EBE06AB8B3D8-htm.html
Bifrost 2 ...

we can not apply Octane materials to Maya fluid since they are volumes.

Hi Bikram,
Maya fluids are not only volumes, they are also surfaces (level sets) :
maya_2022-01-05_10-08-21.png

Indeed this is the exact same thing as Octane Volume_SDF node :
VolumeSDF_fig2_SEv2018-1.png

In the plugin ...

I've attached a city with Mash, but when we render with octane it disappear.
You need to assign Octane materials before attaching the instanced objects to the Mash instancer else Octane doesn't render anything...
However you can easily "repair" the instancer by detaching, assig again octane ...

Terryvfx wrote:Regarding the third question ACES2065-1 = ACEScg, different name same color space.

no it's not.

Am I on the right track there....?

I guess several workflow are possible as usual in Maya,
but personally I prefer to export alembic with the Maya builtin Alembic cache exporter (menus> cache > alembic cache>export selection to alembic) as it is faster, more powerful and reliable than the ORBX ...

But when something is inside the proxy.... the imported mesh is invisible to the Maya view port...

Right the ORBXproxy node only have an annoying box locator representation,
My wokflow is to use alembic geometry in the Orbx proxy node while also linking the same alembic file in a Maya GPUcache ...

Many nice improvements and fixes for the Octane DB in this version, this is quite efficient and pleasant to use now,
and thank you very much for the option to import as orbx materials

for rendering shots and large scene i find the maya workflow quite strange and not so reliable.
Right, depending on the context (interactive / batch render/ exporters/frame cache or not ) and also depending on the object type, the chosen "animator data" type can give different results...
lack of ...

Fixed a bug: crash when DB-importing some nodes having compound plugs.[/list]

No more crash but still some unsupported recent materials failing silently ...
layerMatBitmap.orbx
stripesB.orbx


Repeating myself, but an option to import from localDB as ORBXmaterials would solve these issues ...

I saw an update to the plugin go out, did that fix the issue?
Yes, crash is fixed and some errors are gone but still some issues :
For example Layered Materials and Toon Materials are still not supported ...

Also preparing materials for Maya in Standalone is still way too tedious
as you need to ...