Issue with Animated orbx to ORC
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.
This issue, however, is not resolved in the same manner, and points back to the original issue that I have been having regarding visible boolean operators when rendering in Standalone. As C4DtoOctane is the only way to create an animated orbx package, I am posting here as a bug. As the above pictures show, we see that one frame has a large cylindrical wedge on the left side of frame, while the other does not. When rendering in Cinema, this image renders correctly all of the time. On occasion I will see this object in Live View, but it disappears upon refresh. In Standalone, when rendering the Animated orbx package, the boolean operators are visible in the first frame, but disappear in subsequent frames. Note that I am showing you two different frames about 3 or 4 frames apart, so there are differences due to that.
However, on ORC, using the exact same animated orbx package, the operators are always visible, which differs notably from the results with Standalone. I am using 3.08 Octane and R19 Cinema. I prefer to keep these booleans live rather than bake them in for a variety of reasons (as they animate for effect). Hopefully we can figure out a quick fix.
CaseLabs Mercury S8 / ASUS Z10PE-D8 WS / Crucial 64GB 2133 DDR4 / 2 XEON E5-2687W v3 3.1 GHz / EVGA 1600 P2 / 2 EVGA RTX 2080Ti FTW3 Hybrid/ Cinema 4D
Is it fast? Oh, yeah!
Is it fast? Oh, yeah!
And it appears that the subD operator is also not working properly in the ORC version, as noted in the red object to center top of frame. It is smooth (correct) on the local Standalone version, but not on the ORC version.
CaseLabs Mercury S8 / ASUS Z10PE-D8 WS / Crucial 64GB 2133 DDR4 / 2 XEON E5-2687W v3 3.1 GHz / EVGA 1600 P2 / 2 EVGA RTX 2080Ti FTW3 Hybrid/ Cinema 4D
Is it fast? Oh, yeah!
Is it fast? Oh, yeah!
Do you mean it's correct in standalone but not in ORC? Did you tried to convert boolean objects to meshes?
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Yes, it is correct in Standalone, but after the first frame. It is never correct in ORC, even though both were rendered from the same orbx file.
As I am animating these booleans for a reveal effect, it is difficult for me to convert them to meshes. I am also animating the source cylinder using the slice command, which adds to the complexity of converting them (and it renders correct in with C4DtoOctane anyway, so it should render correct in both Standalone and ORC.)
As I am animating these booleans for a reveal effect, it is difficult for me to convert them to meshes. I am also animating the source cylinder using the slice command, which adds to the complexity of converting them (and it renders correct in with C4DtoOctane anyway, so it should render correct in both Standalone and ORC.)
CaseLabs Mercury S8 / ASUS Z10PE-D8 WS / Crucial 64GB 2133 DDR4 / 2 XEON E5-2687W v3 3.1 GHz / EVGA 1600 P2 / 2 EVGA RTX 2080Ti FTW3 Hybrid/ Cinema 4D
Is it fast? Oh, yeah!
Is it fast? Oh, yeah!
ORC is not about plugin side. So this issue is more related to ORC section.jayroth wrote:Yes, it is correct in Standalone, but after the first frame. It is never correct in ORC, even though both were rendered from the same orbx file.
As I am animating these booleans for a reveal effect, it is difficult for me to convert them to meshes. I am also animating the source cylinder using the slice command, which adds to the complexity of converting them (and it renders correct in with C4DtoOctane anyway, so it should render correct in both Standalone and ORC.)
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Perhaps, but ORC is being driven by the file that is written from the plug in, so it is relevant here.
As I wrote, in Standalone, the issue occurs on the first frame, but disappears in subsequent frames. That indicates that the issue is present in the orbx file; As I noted in one of my posts in the Cinema forum, when I choose the Edit in Standalone option, the issue does NOT present at all, however, choosing the Export Animated Package to Orbx, it DOES present -- it just goes away after the first frame. Perhaps there is some sort of latency thing happening. I am happy to PM you the orbx file to review if you like. Perhaps that can shed some light...
As I wrote, in Standalone, the issue occurs on the first frame, but disappears in subsequent frames. That indicates that the issue is present in the orbx file; As I noted in one of my posts in the Cinema forum, when I choose the Edit in Standalone option, the issue does NOT present at all, however, choosing the Export Animated Package to Orbx, it DOES present -- it just goes away after the first frame. Perhaps there is some sort of latency thing happening. I am happy to PM you the orbx file to review if you like. Perhaps that can shed some light...
CaseLabs Mercury S8 / ASUS Z10PE-D8 WS / Crucial 64GB 2133 DDR4 / 2 XEON E5-2687W v3 3.1 GHz / EVGA 1600 P2 / 2 EVGA RTX 2080Ti FTW3 Hybrid/ Cinema 4D
Is it fast? Oh, yeah!
Is it fast? Oh, yeah!
Only thing is related with plugin is inconsistency of boolean objects. Rest is a compatibility issue on ORC version and standalone. Because you should expect same results between standalone vs. ORC. It's based standalone not plugin. Please send a scene to me.jayroth wrote:Perhaps, but ORC is being driven by the file that is written from the plug in, so it is relevant here.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Will do. Its a big one, so I will try and simplify it for you.
CaseLabs Mercury S8 / ASUS Z10PE-D8 WS / Crucial 64GB 2133 DDR4 / 2 XEON E5-2687W v3 3.1 GHz / EVGA 1600 P2 / 2 EVGA RTX 2080Ti FTW3 Hybrid/ Cinema 4D
Is it fast? Oh, yeah!
Is it fast? Oh, yeah!
While ORC can run 3.08 test releases jobs (mostly for our testing), it's best to work with the latest stable version (3.07) for any production work, until 3.08 is finalized. I am not sure if that is the issue here, but it may be worth trying 3.07 just in case that reduces variables.