5. This is my conclusion as well, the issue can be masked by low enough step volume % however, counter intuitavely to this, I found that in some sitations higher also worked depending on the fog look you are going for.

Hopefully a developer can confirm if this is just a core limition relating to ...

Let me be clear this is NOT an issue with the medium you attach to a daylight system. That medium is very different to an actual voxelised mesh volume, vdb or the likes.

That should be clear already based on the files I am presenting and the problem.

To re-summarise:

- Using a Mesh volume or any ...

This has nothing to do with scene scale.... 'Out of scale' based on what exactly?

You could have any size object that uses a texture with opacity.

Your comments make no sense and does not hint at a real solution based on what I am presenting

EDIT: And to prove it, here is a more 'appropriately ...

It's easily reproducible - I just did an orbx export file, which shows it in standalone.

The 3dsmax scene above shows it more easily as you can easily control the voxel size of the mesh volume.

The bitmap map is not the cause, just swap it for any procedural texture and it's the same issue.

I ...

If you use the Std Medium Volume in compatibility mode, it is a lot harder to replicate this problem.

So the issue has to be tied to the fact that the ray march is no longer tied to an absolute length and rather a % based on voxel size.

If I change my voxel values, volume step %, density and ...

Hello guys,
There is an issue when using a fog volume and there are assets that use opacity maps, such as leaves

I have tried loads of different settings, even found this super old post from 2015 which was solved apparently.
https://render.otoy.com/forum/viewtopic.php?t=49455

Attaching a scene ...

Can someone explain why this is happening? Adding displacement breaks the albedo texture? Switching back to compatibility mode and it's fine

https://drive.google.com/file/d/116kH2TWradgtFH-ZAmFD-omVB7iQBuz7/view?usp=sharing

Thanks

As Octane uses the current viewport camera for rendering (in production mode and Octane viewport mode), you can get the camera like that:
cam = viewport.getCamera()



Thanks neonZorglub, I was already using viewport.getCamera() to get camera XY position but for some reason in my ...

Hello neonZorglub
How would I get the current render camera in production renders?

rendGetCamera() always returns undefined even when a proper camera is in use. I need something that works across frames

Thanks

I would just use Max 2024 unless you have a really good reason to use 2025 or 2026, the new features are barely worthy of a full upgrade. I used 2025 for 2 months but just impacted workflow too much - Max 2024 works flawlessly with Octane