Octane X for Houdini / how to export to standalone

[samjproctor]

Hello everyone. I am running Big Sur, and can launch Octane X PR7 Standalone. However the Houdini plugin still doesn’t work (I believe we were last told it was an issue on Apple’s side). If I relaunch Houdini it crashes on startup. I have to comment out the plugin directory in Houdini.env to launch as expected.

So this currently doesn’t work. Has anyone got advice on how to export scenes into octane standalone? I looked at exporting using alembic, however this only seems to give me one large mesh with one material when in octane. I looked at exporting .obj and can do this, however it would take forever to do this for each individual item. Does anyone have tips or tricks to do this quickly whilst the plugin is not working?

[juanjgon]

I'm afraid that without the plugin, exporting .abc or .obj files is the only way to import objects into Standalone.

Thanks,
-Juanjo

[samjproctor]

Okay, thank you. I shall wait for the next update. I believe with PR7 the plugin causes Houdini to crash on launch. hopefully PR8 will fix this. I have no doubt this will be worth the wait

[spectacle]

Houdini Indie 18.5.408 Works fine for me in Big Sur PR7. It's not the latest Houdini version but you can download it from sidefx.com

[samjproctor]

Wait what!? You have the octane X PR7 Houdini plugin working on big sur with Houdini 18.5.408? Big Sur 11.2? I was told that this was an issue the developers were trying to sort with apple.

I have Big Sur 11.2, octane X PR7 and Houdini 18.5.408 indie. I initially get presented with the permissions dialog when I first copy the plugin folder and edit houdini.env. The first time I allow it, Houdini starts but clicking any of the octane icons doesn’t register what to do with them (it’s like the permissions haven’t properly set). After this when I restart Houdini I just get a crash on launch. (I see the splash screen for Houdini and then it quits). I have to comment out the octane folder in Houdini.env in order to launch Houdini.

[spectacle]

Thats strange. Have you tried reinstalling everything? I'm using your exact setup. I'm on MacOS 11.2. I haven't tried with 11.2.2 or whatever it is now. I've used it with Built 5700 XT on an iMac, as well as external 5700 XT on MBP.

my ENV path is
HOUDINI_PATH = "/Applications/Houdini/Octane_OctaneX_PR7_Houdini_18.5.408_OSX;&"

Maybe your formatting is wrong?

[samjproctor]

Thanks for confirming this. I was using the same folder as the Houdini.env file, but now tried in the application Houdini folder as you have. I experience exactly the same thing. Can I ask how you deal with the permission when you first install this?

So when you copy the plugin folder to the correct location, and then append the Houdini.env file, when I first run I have two files which require permissions (apple displays a 'these files need updating' warning). Did this happen for you?
I can click cancel on these warnings, and Houdini continues to load, and I can see the octane shelf but I cannot do anything with it. If I then restart Houdini crashes upon launch and I have to comment out the Houdini path to successfully launch.
Maybe I just have to wait for PR8 but it is unusual I get nowhere and others seem to be successful.

[samjproctor]

The other thing I notice, is your folder doesn't have vr at the end of it. Whether I download the Houdini Studio plugin or Houdini Prime plugin they both have the same folder for Houdini 18.5.408 with the 'vr' ending.

HOUDINI_PATH = "/Applications/Houdini/Octane_OctaneX_PR7_Houdini_18.5.408_OSX_vr;&"

Is this a different plugin somehow?

[spectacle]

Yeah I don't see the "vr" version when I redownload the plugin. I'm downloading the Enterprise Houdini PR7 plugin.

I don't really remember what it asked when I copied over the plugin. Is it just doing the usual annoying MacOS security thing where you click ok and then have to go to System Preferences > Security & Privacy and click allow?

I also have my Mac with SIP disabled for other nerdy reasons. That MIGHT be why, but I doubt it. SIP is secure boot mode which can be disabled.

[samjproctor]

That is interesting. I have the studio subscription, so do not have access to the enterprise download. I wonder if there is something fundamentally different in these which is preventing me from loading.

Yes it is exactly what you described, with having to go to security & privacy and allowing the file. I may try disabling SIP just to see if that helps. I have nothing to lose at this point.