The bug is that octane is ignoring the fact that the Pyro Output object is not at 0, 0, 0. Once the Pyro Output object is reset, the live view works again.
gf 4090
octane 2025.2.0 b1.5
c4d 2025.2.1
Pyro sim output offsets break renders
Moderators: ChrisHekman, aoktar
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
Open the attached project and play through to frame 10. Note that there are 3 emissions coming out of the cube. If you render to the live view, these emissions will all be in the wrong location.
The bug is that octane is ignoring the fact that the Pyro Output object is not at 0, 0, 0. Once the Pyro Output object is reset, the live view works again.
win 11
gf 4090
octane 2025.2.0 b1.5
c4d 2025.2.1
The bug is that octane is ignoring the fact that the Pyro Output object is not at 0, 0, 0. Once the Pyro Output object is reset, the live view works again.
win 11
gf 4090
octane 2025.2.0 b1.5
c4d 2025.2.1
Hi,
sorry, but why you need to move the Pyro Output object?
ciao,
Beppe
sorry, but why you need to move the Pyro Output object?
ciao,
Beppe
I don't.
But I have.
And now it doesn't work.
I spent 2 hours trying to work out why my sims were all rendering in the wrong place, but screw it, lets not fix bugs, lets make all the other c4d octane users waste their day working around basic octane shortcoming too.
But I have.
And now it doesn't work.
I spent 2 hours trying to work out why my sims were all rendering in the wrong place, but screw it, lets not fix bugs, lets make all the other c4d octane users waste their day working around basic octane shortcoming too.
So if you set back the Pyro output to the origin, everything is ok, correct?
ciao,
Beppe
ciao,
Beppe
