Hi there!
I'm struggling with backward compatibility when opening older Octane files.
As a solution, could we have the option to 'pin' specific Octane versions to different Rhino installations?
For instance, using an older build for Rhino 7 and the latest one for Rhino 8.
Adding a simple toggle in the latest installer to choose the target Rhino version would make managing these legacy projects much easier.
This way we could install an older version of Octane and then on top of that install the newest version just for Rhino 8 and keep the old version with 7 Rhino.
Andy
Wish: Separate Octane Versions for different Rhino Versions
Moderator: face_off
Architectural Rendering Services
1 x 4090 GTX, 1 x 3090 GTX
http://www.v-cube.de
1 x 4090 GTX, 1 x 3090 GTX
http://www.v-cube.de
Hi Andy
I understand the challenges you have around this. Firstly, the plugin only stores the pin values that are present in the installed version of the Octane plugin. So if a pin gets removed between Octane 2025 and Octane 2026, then saving the .RHI with the 2026 version of the plugin means the value of the pin that was removed is not saved in the .RHI file. This makes having a system where a .RHI file can be opened on multiple Octane versions of the plugin and render the same problematic. Some of the other plugins get around this by saving the native Octane format OCS file XML to the .RHI file, but at this stage it is not viable to implement such a system in the Rhino plugin.
The other challenge is how Rhino loads plugins. My understanding is that a plug will automatically load in Rhino8 if it is installed for Rhino7. I may be wrong, but my interpretation of this is that it is not possible to have separate versions of the plugin for Rhino7 and Rhino8. Having said that, you can potentially manually do this by a) installing the version of the plugin with the older version of Octane, copying the plugin from from it's install folder into a different folder, then install the latest version of the plugin, then update Regedit for the Rhino7 version of the plugin to point to the copied location. Then in theory you have a different version of the plugin loading for Rhino7 compared with Rhino8. I haven't tried this, but it seems like it would work. I can provide more details if you need (like the registry keys you would need to update). I suspect when you install a new version of the plugin, you will need to reset the Rhino7 plugin location in regedit again, as it will more likely have been overwritten by the install process.
Thanks
Paul
I understand the challenges you have around this. Firstly, the plugin only stores the pin values that are present in the installed version of the Octane plugin. So if a pin gets removed between Octane 2025 and Octane 2026, then saving the .RHI with the 2026 version of the plugin means the value of the pin that was removed is not saved in the .RHI file. This makes having a system where a .RHI file can be opened on multiple Octane versions of the plugin and render the same problematic. Some of the other plugins get around this by saving the native Octane format OCS file XML to the .RHI file, but at this stage it is not viable to implement such a system in the Rhino plugin.
The other challenge is how Rhino loads plugins. My understanding is that a plug will automatically load in Rhino8 if it is installed for Rhino7. I may be wrong, but my interpretation of this is that it is not possible to have separate versions of the plugin for Rhino7 and Rhino8. Having said that, you can potentially manually do this by a) installing the version of the plugin with the older version of Octane, copying the plugin from from it's install folder into a different folder, then install the latest version of the plugin, then update Regedit for the Rhino7 version of the plugin to point to the copied location. Then in theory you have a different version of the plugin loading for Rhino7 compared with Rhino8. I haven't tried this, but it seems like it would work. I can provide more details if you need (like the registry keys you would need to update). I suspect when you install a new version of the plugin, you will need to reset the Rhino7 plugin location in regedit again, as it will more likely have been overwritten by the install process.
Thanks
Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question