VRScene issue with Motion Blur

Looks like I accidently found a bug related to Motion blur and with VRScenes. I managed to recreate the problem in a simple scene.

If I load a .vrscene cache file (saved from Houdini) and try to render using Motion Blur, using a Vray Physical Camera , an un-flipped version of my character get duplicated in the scene. For now we are rendering with velocity and making MB on comp but would be nice have this look into it. We are all using Vray 7.4 stable versions.

Would it be possible to provide a simple scene where this one is replicated? Thanks.

Edit. We received the materials and will check them. Thanks.

Following up on #507322 with two simple repros, no production assets. Everything is in one zip: https://drive.google.com/file/d/18FadQrn1CL9l5IHEzlXcBLTixXCVYpgf/view?usp=sharing

  1. synthetic_repro: script-generated vrscenes, a Max 2024 scene and a README.
  2. max_export (new): the same bug with vrscenes exported by V-Ray for 3ds Max itself, so it is not tied to our Houdini caches.

The duplicate only shows when all three are true:

  • the VRayScene loads a per-frame sequence ()
  • the files declare Y-up, so V-Ray converts them to Z-up (flip axis Auto or Flip)
  • camera motion blur is on

The extra copy is the geometry without the up-axis conversion. Max’s own export doesn’t show it only because Max writes Z-up. As soon as I declare the same Max export Y-up, it duplicates. It still duplicates when both shutter samples are inside each frame file, and it doesn’t happen when the node points at one resolved frame file without the token. With MB off, every variant renders identical.

One more thing we found, maybe not a bug but worth flagging: both the Max exporter and our Houdini cfx export give every mesh plugin a new content-hash name each frame. With one time sample per file, which is what our Houdini caches have, V-Ray can’t pair a mesh with itself in the next frame file, so we get no deformation blur at all. Max avoids it by writing two samples per file. Is there a way to get stable plugin names, or two samples per frame, out of the Houdini vrscene export?

Two questions:

  1. Is there an ETA on the fix?
  2. Until then, is baking the Y-up to Z-up rotation into the Node transforms and declaring the scene Z-up safe to use in production? That renders clean for us.

Tested on 3ds Max 2026, V-Ray 7.40.05 (build 33719).

Thanks!
Delcio

Hi Delciogames,

Thank you for sharing the details!

We are working on a fix for this issue (VMAX-15825).
We’ve made progress, but we don’t have an estimated timeframe for the fix.

You can try baking the transformation as a workaround if that works for your workflow.
Are you able to use a single .vrscene file with all the animations, without using the <frame04> tag?

Regarding the exporter, we will check with the Houdini team to get more information.

We will keep you posted.

Hi Martin,

Quick update, we have a workaround that is confirmed on Chaos Cloud.

Before rendering, we convert each per-frame vrscene:

  1. Bake the Y-up to Z-up rotation into the node transforms and declare the scene Z-up.
  2. Add the next frame as a second time sample, with the mesh relinked to one plugin.

With that, camera motion blur renders clean on the farm (no duplicate) and we get proper deformation blur. Tested on three production shots.

Still interested in a real fix for the <frame4> + Y-up + motion blur duplicate, and in a way to get stable mesh names (or two samples per frame) out of the Houdini vrscene export.

Thanks!
Delcio