Octane Solaris plugin 2021.1.0.4 - 12-02-21 [OBSOLETE]

Sub forum for plugin releases
BK
OctaneRender Team
Posts: 1461
Joined: Mon Oct 31, 2016 7:54 pm

Ferdinand13 wrote:Hi BK,

Thanks for the suggestion. I followed your advice step by step. Octane has been activated for the plugin, but the same issue persists within Solaris, i.e. I click on Octane to activate it as the viewport renderer and then nothing happens, while the option to use Octane disappears from the dropdown menu. Have a look at the screen recording below:
Octane_SolarisIssue.mp4
I wouldn't even say that Octane "crashes" because the normal Octane IPR still works flawlessly, even after the viewport render option has disappeared.

Any idea what's going wrong?
Hi Ferdinand13,

Thank you for the video.

Would you please let us know the Houdini version? Please use the non-python and see if it works.
Also, the .env path is the same as our main plugin, for example,

Code: Select all

PATH = "PATH_TO_OctaneSolaris\bin;$PATH"
HOUDINI_PATH = "PATH_TO_OctaneSolaris;&"

cheers
Kind Regards

bk3d
User avatar
Ferdinand13
Licensed Customer
Posts: 154
Joined: Sun Apr 03, 2016 4:21 pm
Location: United Kingdom

Hi BK,

Sure. The Houdini version is 18.5.696, which is the built that the most recent version of Octane Solaris Studio was created for, right?

In terms of the paths in the .env file, I'm using Houdini packages to load Octane (and all my other render plugins). The Octane.json file that I've created reads as follows:

Code: Select all

{
	"env": [ 
	{ "HOUDINI_PATH": ["C:/Program Files/OTOY/OctaneSolarisStudio_2021.1.0.4_Houdini_18.5.696_Win64"] },
	{ "PATH": ["C:/Program Files/OTOY/OctaneSolarisStudio_2021.1.0.4_Houdini_18.5.696_Win64/bin"] }
	]
}
Custom PC, Intel Core i7-6800K, 48GB RAM, 3x MSI GeForce RTX 2080 Super Seahawk EK, Windows 10
Razer Blade Pro 17, Intel Core i7-10875H, 32GB RAM, 1x NVIDIA GeForce RTX 3080, 1x EVGA GeForce GTX 1080 Ti Hybrid (eGPU), Windows 10
BK
OctaneRender Team
Posts: 1461
Joined: Mon Oct 31, 2016 7:54 pm

Ferdinand13 wrote:Hi BK,

Sure. The Houdini version is 18.5.696, which is the built that the most recent version of Octane Solaris Studio was created for, right?

In terms of the paths in the .env file, I'm using Houdini packages to load Octane (and all my other render plugins). The Octane.json file that I've created reads as follows:

Code: Select all

{
	"env": [ 
	{ "HOUDINI_PATH": ["C:/Program Files/OTOY/OctaneSolarisStudio_2021.1.0.4_Houdini_18.5.696_Win64"] },
	{ "PATH": ["C:/Program Files/OTOY/OctaneSolarisStudio_2021.1.0.4_Houdini_18.5.696_Win64/bin"] }
	]
}

Hi Ferdinand13,
Thank you so much for this.
Would you please try to install via .env directly while we check if our plugin supports package installation with our devs?

cheers
Kind Regards

bk3d
User avatar
Ferdinand13
Licensed Customer
Posts: 154
Joined: Sun Apr 03, 2016 4:21 pm
Location: United Kingdom

Hi BK, thanks for the suggestion. I now removed the Octane.json from the packages folder and added the path variables to Houdini's .env file as you see below.

Code: Select all

HOUDINI_PATH = "C:/Program Files/OTOY/OctaneSolarisStudio_2021.1.0.4_Houdini_18.5.696_Win64;&"

PATH = "C:/Program Files/OTOY/OctaneSolarisStudio_2021.1.0.4_Houdini_18.5.696_Win64/bin;$PATH"
Unfortunately the same error still persists.

I hope we can find a way to get this to work :)
Custom PC, Intel Core i7-6800K, 48GB RAM, 3x MSI GeForce RTX 2080 Super Seahawk EK, Windows 10
Razer Blade Pro 17, Intel Core i7-10875H, 32GB RAM, 1x NVIDIA GeForce RTX 3080, 1x EVGA GeForce GTX 1080 Ti Hybrid (eGPU), Windows 10
BK
OctaneRender Team
Posts: 1461
Joined: Mon Oct 31, 2016 7:54 pm

Ferdinand13 wrote:Hi BK, thanks for the suggestion. I now removed the Octane.json from the packages folder and added the path variables to Houdini's .env file as you see below.

Code: Select all

HOUDINI_PATH = "C:/Program Files/OTOY/OctaneSolarisStudio_2021.1.0.4_Houdini_18.5.696_Win64;&"

PATH = "C:/Program Files/OTOY/OctaneSolarisStudio_2021.1.0.4_Houdini_18.5.696_Win64/bin;$PATH"
Unfortunately the same error still persists.

I hope we can find a way to get this to work :)
Hi Ferdinand13,

Thank you for the test.
It seems the path is using the forward slash.
Would you please try changing them with backward slash(\) and see if it works?

cheers
Kind Regards

bk3d
User avatar
Ferdinand13
Licensed Customer
Posts: 154
Joined: Sun Apr 03, 2016 4:21 pm
Location: United Kingdom

Hi BK,

I tried the Octane Solaris plugin on my custom PC now and it loads as expected there, no matter whether I'm using forward or backward slashes in the file path, so that doesn't seem to be the problem. I'll have to look deeper into this, as it doesn't make sense this won't run on the Razer laptop, since everything else is the same installation-wise.

Just a little issue I picked up while playing around with Octane in Solaris: You can quickly swap between Redshift, Karma and Houdini GL, without having to worry about pausing the render process. You just switch and the new renderer starts doing its job. However, with Octane it caused Houdini to crash, if I switched to another renderer without pausing Octane first. On top of that, after having used a different renderer, upon switching back to Octane, the viewport remains empty, even though it looks like it started rendering. You have to click "Restart Render" in the dropdown menu for the viewport to refresh and show the scene again.

Just a small issue, but maybe you can look into this for the next release :)
Custom PC, Intel Core i7-6800K, 48GB RAM, 3x MSI GeForce RTX 2080 Super Seahawk EK, Windows 10
Razer Blade Pro 17, Intel Core i7-10875H, 32GB RAM, 1x NVIDIA GeForce RTX 3080, 1x EVGA GeForce GTX 1080 Ti Hybrid (eGPU), Windows 10
BK
OctaneRender Team
Posts: 1461
Joined: Mon Oct 31, 2016 7:54 pm

Ferdinand13 wrote:Hi BK,

I tried the Octane Solaris plugin on my custom PC now and it loads as expected there, no matter whether I'm using forward or backward slashes in the file path, so that doesn't seem to be the problem. I'll have to look deeper into this, as it doesn't make sense this won't run on the Razer laptop, since everything else is the same installation-wise.

Just a little issue I picked up while playing around with Octane in Solaris: You can quickly swap between Redshift, Karma and Houdini GL, without having to worry about pausing the render process. You just switch and the new renderer starts doing its job. However, with Octane it caused Houdini to crash, if I switched to another renderer without pausing Octane first. On top of that, after having used a different renderer, upon switching back to Octane, the viewport remains empty, even though it looks like it started rendering. You have to click "Restart Render" in the dropdown menu for the viewport to refresh and show the scene again.

Just a small issue, but maybe you can look into this for the next release :)
Hi Ferdinand13,

Thank you so much for the feedback.
Our dev has found a bug that causes this crash and will get it fixed for the next release!

cheers
Kind Regards

bk3d
Post Reply

Return to “Releases”