Paul, the 2023.1.3.200 release notes are wrong about the octane.exportFrame useOldExporter option ("octane.exportFrame" doesn't exist).

The actual command is

I replied on slack, but posting it here too:

The new output AOVs don't go through the imager anymore. You have to rebuild your effects with the newly available nodes. While they aren't exactly the same, you can get something pretty close once you learn how. It's also WAY more flexible. eg. you can ...

As far as I know, motion blur won't work if the particle count is different in each frame.
IMPORTANT: motion blur on Replicators only works if there are the same number of Point Source transforms each frame

The alternative instructions only seem to allow you to see the replicas (without motion ...

I also found a way to make it work in modo, although I'm not sure if it's correct

Add a modo motion vector render output (add layer > render outputs > basic > motion vector) and restart the render.
This seems to help the render cache produce correct motion vectors (?)
It also exports the ORBX ...

UPDATE: There is more to this. I restarted modo, loaded the scene and went straight to an export. This second ORBX is NOT showing motionblur (on the middle mesh) in standalone.

If I DISABLE "use modo render cache", then export, it works though. So I may have changed settings, or there is some ...

Motion blur is not working in Standalone on an exported ORBX from this scene either, so something is amiss. I am away for the Christmas break, so will need to look at this next week.

Paul

Standalone 2023.1.1 is showing motion blur here. Here's a screenshot and the ORBX.
NOTE: I'm using modo 16 ...

@funk - as to your Fusion setup:
When reading in the image with the OCIO node and transforming it to sRGB that means that you then also have sRGB as your working color space - meaning that Fusion will apply all it's operations on data in that color space, which I think is not ideal. If you do that ...

I need to add a note here about saving PNGs with Octane. I only noticed this while testing the 2 different ways you can use ACES in Octane.

If you are using an ACES OCIO config with imager > OCIO view = "ACES: sRGB", you need to select color space = "Output - sRGB" when saving to PNG.
Selecting ...

I don't use Nuke, but tested this in fusion and it looks correct with a simple textured area light.

In this fusion comparison, I'm using no view LUT.
Left = modo viewport, Octane plugin 2023.1.1.196 (using imager > ACES tone mapping)
Right, Top left = EXR16 (saved as ACEScg). Piped through an OCIO ...

As a long time user you probably already know this.

You need to delete your modo config (or move it somewhere else), then start modo to generate a new one.

On windows it's in C:\Users\USERNAME\AppData\Roaming\Luxology

This is just the way modo works. You are probably missing layout changes in the ...