Page 2 of 8
Re: OctaneRender 2020 for Rhino (TEST and STABLE)
Posted:
Tue Jan 28, 2020 2:17 amby trogers
Hi Paul,
Quick update, I installed 2019.1.4.115 and it worked flawlessly for saving out a layered EXR from the IPR. I'm happy to send you any technical info you think you'd need to source the issue with 2020.
Best / Travis
Re: OctaneRender 2020 for Rhino (TEST and STABLE)
Posted:
Tue Jan 28, 2020 2:52 amby face_off
Thanks for getting back and sorry for the delay in my reply. I get the error dialog when attempting to save a layered EXR from the corresponding icon at the top of the Octane IPR window in any of the format options (32, 16, ACES, tonemapped or not). It gives me a file explorer window that I can type the file name into, but after hitting save it presents the error. I just tried deleting the plugin from Rhino and I updated to the latest .117 version of the plugin but that didn't solve it for me. Do you have any ideas as to how to either reset things or how I could provide you with any technical info? I'm also running the latest studio drivers for my Nvidia 2080Ti (Studio 441.66).
Hi - can you please provide a sample scene where this happens?
Thanks
Paul
Re: OctaneRender 2020 for Rhino (TEST and STABLE)
Posted:
Tue Jan 28, 2020 10:59 pmby trogers
Hi Paul,
Please find a scene attached. It seems to happen even if I create a very simple single cube scene. Let me know what you find. I can create a screen capture video for you as well if need be. This was using the .117 version, but again .116 was giving me the same results.
Best / Travis
Re: OctaneRender 2020 for Rhino (TEST and STABLE)
Posted:
Wed Jan 29, 2020 2:48 amby face_off
Please find a scene attached. It seems to happen even if I create a very simple single cube scene. Let me know what you find. I can create a screen capture video for you as well if need be. This was using the .117 version, but again .116 was giving me the same results.
Thanks for providing the scene Travis. That allowed me to reproduce the error, which is fixed in the next release.
Paul
Re: OctaneRender 2020 for Rhino (TEST and STABLE)
Posted:
Wed Jan 29, 2020 2:59 amby face_off
I have updated the installers at the top of this thread with:
2020.1.0.118
- Fixed bug where saving to multi-layer EXR files was not working
Thanks
Paul
Re: OctaneRender 2020 for Rhino (TEST and STABLE)
Posted:
Fri Jan 31, 2020 9:40 pmby trogers
Thanks so much Paul, I just installed 118 and can confirm that it's working as expected on my end. I appreciate the quick turn around on the new version!
Best / Travis
Re: OctaneRender 2020 for Rhino (TEST and STABLE)
Posted:
Wed Mar 11, 2020 4:11 amby stonearch.isaacs
Hi Simon,
See the CUDA 999 message attached. I have a standalone license, latest Version 3 plugins for Rhino 6, latest Rhino 6 service release, latest NVIDIA driver for my Geforce GTX 1080. I've been using the software with no issues for 5 years and I can usually resolve problems by either reverting to previous versions or updating the software / drivers. Thoughts?
Cheers, Dave
Re: OctaneRender 2020 for Rhino (TEST and STABLE)
Posted:
Wed Mar 11, 2020 10:12 amby face_off
stonearch.isaacs wrote:Hi Simon,
See the CUDA 999 message attached. I have a standalone license, latest Version 3 plugins for Rhino 6, latest Rhino 6 service release, latest NVIDIA driver for my Geforce GTX 1080. I've been using the software with no issues for 5 years and I can usually resolve problems by either reverting to previous versions or updating the software / drivers. Thoughts?
Cheers, Dave
Hi Dave. Please see point 7) in the Solution to Common Problems at the very top of this thread.
Thanks
Paul
Re: OctaneRender 2020 for Rhino (TEST and STABLE)
Posted:
Fri Mar 20, 2020 12:41 amby roy_orengo
hello,
i'm trying to install the 2020 realease _118 but i receive this error: "This build is not supported anymore. Please update to a newer version."
Thanks,
Roy
Re: OctaneRender 2020 for Rhino (TEST and STABLE)
Posted:
Fri Mar 20, 2020 11:30 amby face_off
i'm trying to install the 2020 realease _118 but i receive this error: "This build is not supported anymore. Please update to a newer version."
I will post a new build in the next 24hrs to resolve this.
Paul
