OctaneRender 2018.1 for Houdini Production build 2018.1.0.7 Tweet

[ptunstall]

I get this same warning in my console as well, appears in 4 as well but it doesn't seem to affect anything.

In other news, this latest build WORKS GREAT on my linux nodes after install 418.43(LINUX FEB 22nd)!!!! Thanks so much for all the amazingness Jaunjo!!!

[seriawp]

Houdini 17.5 plugin already realese for Octane 4.02 ?

[juanjgon]

Houdini 17.5 plugin already realese for Octane 4.02 ?

Not yet, we'll add an H17.5 plugin build for Octane 4.02 next week.

Thanks,
-Juanjo

[Fake Pilot]

I am also getting errors, even though I can start IPR and get a render without any watermarks.
The errors appear with or without the HOUDINI_DSO_ERROR = 2 though, so it is a bit annoying.

*** OCTANE API MSG: Tried to access pin via an invalid index 1
*** OCTANE API MSG: Tried to access null node pin
*** OCTANE API MSG: Can't connect node 'Object layer' (NT_OBJECTLAYER, 00000001A8AB96E0) to static pin 'unknown' (P_UNKNOWN, type PT_UNKNOWN) of node '' (NT_UNKNOWN, 00007FFE0D4B4F00)
*** OCTANE API MSG: ORC user subscription status could not be retrieved: The server returned a client-side error with HTTP code: 401
*** OCTANE API MSG: ORC subscription status cannot be found

My .env file looks like this:

Code: Select all

HOUDINI_DSO_ERROR = 2

# MOPS IS MOGRAPH FOR HOUDINI
MOPS = "C:/Users/fakep/Documents/MOPS-0.1.37"
HOUDINI_PATH = "C:/Users/fakep/Documents/Octane_2018.1.0.7_Houdini_17.5.173_Win64;$MOPS;&"
PATH = "C:/Users/fakep/Documents/Octane_2018.1.0.7_Houdini_17.5.173_Win64/bin;$PATH"

I upgraded to Enterprise this morning, it's working in Standalone and Cinema 4D.

[juanjgon]

Hi,

You can always disable the Windows Houdini console window if you add the HOUDINI_DISABLE_CONSOLE environment variable to the houdini.env file:

Code: Select all

HOUDINI_DISABLE_CONSOLE = 1


Hope it helps while we fix the problems with the Octane API messages.

Thanks,
-Juanjo

[snakeboxmedia]

I'm not sure if this is the correct place to ask, but for some reason in houdini 17.5 with the latest build 2018.1.0.7 octane says my account isn't activated anymore? when try to reset it using license manager, I can relogin, but houdini crashes to desktop after a min of just sitting there after I try to login, restart houdini and repeat... now my houdini subscription is active and obviously worked fine with houdini 17, just wondering if 17.5 has prompted anyone else to re-activate your octane account?

Thanks

EDIT: Oh wait, am I being a complete moron? I just noticed the SERVER MAINTENANCE post for the 19th.... which is today..... hmmmm ill go away for a bit....

EDIT2: Soooo maybe something is wrong, the maintenance is still 12 hours it seems.... hmm?

[juanjgon]

I'm not sure if this is the correct place to ask, but for some reason in houdini 17.5 with the latest build 2018.1.0.7 octane says my account isn't activated anymore? when try to reset it using license manager, I can relogin, but houdini crashes to desktop after a min of just sitting there after I try to login, restart houdini and repeat... now my houdini subscription is active and obviously worked fine with houdini 17, just wondering if 17.5 has prompted anyone else to re-activate your octane account?

Here I don't have any problem with H17.5 and the licensing. The license should be activated automatically when you launch an Octane rendering (from the IPR, for example). If you have problems, I wonder if you have installed the right plugin version for your license (Entreprise or Studio) ...

Thanks,
-Juanjo

[snakeboxmedia]

I'm not sure if this is the correct place to ask, but for some reason in houdini 17.5 with the latest build 2018.1.0.7 octane says my account isn't activated anymore? when try to reset it using license manager, I can relogin, but houdini crashes to desktop after a min of just sitting there after I try to login, restart houdini and repeat... now my houdini subscription is active and obviously worked fine with houdini 17, just wondering if 17.5 has prompted anyone else to re-activate your octane account?

Here I don't have any problem with H17.5 and the licensing. The license should be activated automatically when you launch an Octane rendering (from the IPR, for example). If you have problems, I wonder if you have installed the right plugin version for your license (Entreprise or Studio) ...

Thanks,
-Juanjo

I'm installing this Octane_2018.1.0.7_Houdini_Win64_vr which is the studio subscription, it is the same version I have installed for 4.01.1.1, 4.02.0.0 and 2018.1.0.6 for instance, I just started H17 and there the license still works for 2018.1.0.6

it just says it can't find my license, but something is certainly not correct. I think it thinks im trying to activate the all access standalone, which im not obviously.. my env path etc is copied from H17 and just renamed to match the new version so I don't fully understand how it would load something wrong, but maybe?

I mean I must be doing something wrong I will try and install it again fresh.

EDIT1: yes I can see when I cross reference the License name it is referring to in the error box, it's to the all access subscription, which I don't have, as I have a studio houdini subscription, but none of the previous builds has done this?

EDIT2: I just tried loading the 2018.1.0.7 version into my H17 which worked perfectly fine with .6 before, and I get the same error, so there is something in the latest build that isn't accepting my license type I'm guessing?

[juanjgon]

Do you know if the final Standalone 2018.1 Studio subscription works fine on your system? I wonder if there is a problem with the plugin Octane core libs or something like that ...
viewtopic.php?t=70809

Thanks,
-Juanjo

[snakeboxmedia]

Do you know if the final Standalone 2018.1 Studio subscription works fine on your system? I wonder if there is a problem with the plugin Octane core libs or something like that ...
viewtopic.php?t=70809

Thanks,
-Juanjo

Ive never used the stand alone so not sure, but I will try!

edit1: Nope! getting the exact same error the first time I try to start octane standlone 2018. Same license prompt saying I dont have all-access subscription.

but like I said, it has only happened since the very latest build, so yeah maybe something is a little off?