The glow effects in the octane render settings should look identical to the glow effects in the camera tag right? I cant get these to match.
Octane settings glow:
Same settings on camera:
project attached
octane 2023.1.2
c4d 2024.2.0
win 11
post effect glow different from camera glow
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.
- Attachments
-
- cam vs post.zip
- (98.77 MiB) Downloaded 49 times
Hi boxfx,
thanks for the report, we are looking into it.
Please use the Camera Post Effect for now.
ciao,
Beppe
thanks for the report, we are looking into it.
Please use the Camera Post Effect for now.
ciao,
Beppe
Scale with film makes no difference, though on a side note this setting seems to be missing from the camera glow version UI.elsksa wrote:Does the dissimilarity occur when deselecting "Scale with film" and without and any FX from the Lens Effects section?
Is the "color management" consistent and properly set?
Color management is 100% defaults
Ok, please remove the installed c4doctane version and upgrade to 2023.1.2-R2 stable:
https://render.otoy.com/customerdownloa ... R2_win.rar
Then correct the General Post Effects values, and you should have almost the same result.
There is still an issue with Spread Start value, and will be fixed in next update.
ciao,
Beppe
https://render.otoy.com/customerdownloa ... R2_win.rar
Then correct the General Post Effects values, and you should have almost the same result.
There is still an issue with Spread Start value, and will be fixed in next update.
ciao,
Beppe