Export Animation to ORBX -> Turn off Replicator motionblur

[face_off]

Thanks - I can now load the scene, but still not able to replicate the issue you are having. This is what I get when I open the viewport.

Are you animating the position of the replicator transforms? If so, they I would suggest instead to not animate the replicator particles, and instead have a static grid and animate the material instead. Use an Octane RGB Image with a Planar (XYZ to UVW) projection and World space coordinate space. Then animate the RGB Image -> UV Transform -> Translation to move the LED's that are on.

I hope the helps a little.

Thanks

Paul

[Hesekiel2517]

Hi Paul,

can you check if the Text meshop has a font selected? I'm not animating the positions, but divide the particles and feed them into two replicators.

[Hesekiel2517]

I froze the mesh, should now work out of the box

[face_off]

I am really sorry, but I still get the same render as previously, so it is not working for me

Paul

[funk]

I am really sorry, but I still get the same render as previously, so it is not working for me

Paul

Did you try rendering out the animation?

[funk]

I tried rendering the animation and it stopped at around frame 91. Checking the log I see it ends up crashing Octane.

When checking the rendered frames, I noticed particles and text in wrong places (see attached frames 42, 43, 44, 84)

There seem to be some other issues going on. If I restart modo, load the file and try to render in MODO, the animation looks wrong (text not showing up, particles in wrong places etc).

I need to scrub the timeline a few times and press f8 to render until it eventually looks correct.

[Hesekiel2517]

Hi Paul,
any news on this? FYI i tried to export the two replicators separately and combine them in standalone. The same error happens there too. Maybe that helps to find the reason behind this.

All the best!

[face_off]

Funk was able to identify the problem I was having in that I didn't have the font installed. After that I was able to get an Octane crash, which was reported to OTOY. At a guess, I would say that because there are some frames that don't appear to have any red cubes, it is going to either trip the plugin or Octane up - as there will be a replicator with 0 instances at that point, but we will need to wait to see what the Octane fix brings.

Paul

[Hesekiel2517]

Hi Paul, thank you for looking into this! I'm not sure if i understand your explanation correctly, because the problem is that octane turns the wrong cubes to red and only a reload of the scene fixes it.

[face_off]

Hi Paul, thank you for looking into this! I'm not sure if i understand your explanation correctly, because the problem is that octane turns the wrong cubes to red and only a reload of the scene fixes it.

My understanding is that OTOY have resolved an issue in the next release of Octane which is likely to resolve your issue. I don't have access to this release yet, so cannot confirm the fix at this stage.

Thanks

Paul