OTOY Forums

Not sure what these mean, but they have the word Octane in them.
They pop up in the Houdini Dialog Window.

WARNING: OPUI_DialogPRM2: Symbol "open.val" value stepped on.

WARNING: OPUI_DialogPRM2: Symbol "open.val" value stepped on.

WARNING: OPUI_DialogPRM2: Symbol "open.val" value stepped on.

WARNING: OPUI_DialogPRM2: Symbol "open.val" value stepped on.

Qt Warn: External WM_DESTROY received for QWidgetWindow(0x205c294f760, name="RE_WindowWindow") , parent: QWindow(0x0) , transient parent: QWindow(0x0)
Qt Warn: External WM_DESTROY received for QWidgetWindow(0x205c294da80, name="RE_WindowWindow") , parent: QWindow(0x0) , transient parent: QWindow(0x0)
Qt Warn: External WM_DESTROY received for QWidgetWindow(0x205c294dfc0, name="RE_WindowWindow") , parent: QWindow(0x0) , transient parent: QWindow(0x0)
Qt Warn: External WM_DESTROY received for QWidgetWindow(0x205c294ece0, name="RE_WindowWindow") , parent: QWindow(0x0) , transient parent: QWindow(0x0)
Qt Warn: External WM_DESTROY received for QWidgetWindow(0x205c1bbca00, name="RE_WindowWindow") , parent: QWindow(0x0) , transient parent: QWindow(0x0)
Qt Warn: External WM_DESTROY received for QWidgetWindow(0x205918bd480, name="RE_WindowWindow") , parent: QWindow(0x0) , transient parent: QWindow(0x0)
Qt Warn: External WM_DESTROY received for QWidgetWindow(0x205c286ef20, name="RE_WindowWindow") , parent: QWindow(0x0) , transient parent: QWindow(0x0)
Qt Warn: External WM_DESTROY received for QWidgetWindow(0x205918bcd00, name="RE_WindowWindow") , parent: QWindow(0x0) , transient parent: QWindow(0x0)
Qt Warn: External WM_DESTROY received for QWidgetWindow(0x205c8912140, name="RE_WindowWindow") , parent: QWindow(0x0) , transient parent: QWindow(0x0)
Qt Warn: External WM_DESTROY received for QWidgetWindow(0x2058f6a3340, name="RE_WindowWindow") , parent: QWindow(0x0) , transient parent: QWindow(0x0)
Qt Warn: External WM_DESTROY received for QWidgetWindow(0x205c89120e0, name="RE_WindowWindow") , parent: QWindow(0x0) , transient parent: QWindow(0x0)
Qt Warn: External WM_DESTROY received for QWidgetWindow(0x2058f6a3880, name="RE_WindowWindow") , parent: QWindow(0x0) , transient parent: QWindow(0x0)
Qt Warn: External WM_DESTROY received for QWidgetWindow(0x205a183e080, name="RE_WindowWindow") , parent: QWindow(0x0) , transient parent: QWindow(0x0)
Qt Warn: External WM_DESTROY received for QWidgetWindow(0x205a183eb60, name="RE_WindowWindow") , parent: QWindow(0x0) , transient parent: QWindow(0x0)
Qt Warn: External WM_DESTROY received for QWidgetWindow(0x205a183dd80, name="RE_WindowWindow") , parent: QWindow(0x0) , transient parent: QWindow(0x0)
Qt Warn: External WM_DESTROY received for QWidgetWindow(0x20599bbb940, name="RE_WindowWindow") , parent: QWindow(0x0) , transient parent: QWindow(0x0)
Qt Warn: External WM_DESTROY received for QWidgetWindow(0x205a959f640, name="RE_WindowWindow") , parent: QWindow(0x0) , transient parent: QWindow(0x0)
Qt Warn: External WM_DESTROY received for QWidgetWindow(0x205a959d480, name="RE_WindowWindow") , parent: QWindow(0x0) , transient parent: QWindow(0x0)
Qt Warn: External WM_DESTROY received for QWidgetWindow(0x205a943ffa0, name="RE_WindowWindow") , parent: QWindow(0x0) , transient parent: QWindow(0x0)
Qt Warn: External WM_DESTROY received for QWidgetWindow(0x205a9771360, name="RE_WindowWindow") , parent: QWindow(0x0) , transient parent: QWindow(0x0)
WARNING: OPUI_DialogPRM2: Symbol "open.val" value stepped on.

WARNING: OPUI_DialogPRM2: Symbol "open.val" value stepped on.

*** OCTANE API MSG: Tried to access null node
*** OCTANE API MSG: Tried to access null node pin
*** OCTANE API MSG: Tried to access null node
*** OCTANE API MSG: Tried to access null node pin
*** OCTANE API MSG: Tried to access null node pin
*** OCTANE API MSG: Tried to access null node pin
*** OCTANE API MSG: Tried to access null node
*** OCTANE API MSG: Tried to access null node pin
*** OCTANE API MSG: Tried to access null node
*** OCTANE API MSG: Tried to access null node pin
*** OCTANE API MSG: Tried to access null node
*** OCTANE API MSG: Tried to access null node pin
*** OCTANE API MSG: Tried to access null node
*** OCTANE API MSG: Tried to access null node pin
*** OCTANE API MSG: Tried to access null node
*** OCTANE API MSG: Tried to access null node pin
*** OCTANE API MSG: Tried to access null node
*** OCTANE API MSG: Tried to access null node pin
*** OCTANE API MSG: Tried to access null node
*** OCTANE API MSG: Tried to access null node pin
*** OCTANE API MSG: Tried to access null node
*** OCTANE API MSG: Tried to access null node pin
*** OCTANE API MSG: Tried to access null node
*** OCTANE API MSG: Tried to access null node pin
*** OCTANE API MSG: Tried to access null node
*** OCTANE API MSG: Tried to access null node pin
*** OCTANE API MSG: Tried to access null node
*** OCTANE API MSG: Tried to access null node pin
*** OCTANE API MSG: Tried to access null node
*** OCTANE API MSG: Tried to access null node pin

I'm not sure about the origin of the PRM and Qt related messages, they seem something related to Houdini, but the *** OCTANE API MSG: Tried to access null node message usually means that in the scene there is an object that at the end didn't have any valid geometry (polygon for example) available for rendering.

Usually, the null node messages are not a problem for the rendering (in Houdini 16 they can be launch while working with bones, for example), but if you have a scene to reproduce these issues, send it to me to test it here.

Thanks,
-Juanjo

juanjgon wrote:I'm not sure about the origin of the PRM and Qt related messages, they seem something related to Houdini, but the *** OCTANE API MSG: Tried to access null node message usually means that in the scene there is an object that at the end didn't have any valid geometry (polygon for example) available for rendering.

Usually, the null node messages are not a problem for the rendering (in Houdini 16 they can be launch while working with bones, for example), but if you have a scene to reproduce these issues, send it to me to test it here.

Thanks,
-Juanjo

I just found this, I just got this error. rendered a sequence last night, no problems all good. shut down computer, started again today and now I can't open the file I get the long list of errors mentioned here, and houdini crashes at the end of it. Is my work just lost or was there a solution and work around to cover from this?

I am using the the latest octane 4 build for H17.5

Hi,

Sorry, for that. So do you say that the scene is corrupted? In this case, I'm not sure if recover it is going to be possible, I hope you have a backup of it. About the source of this problem, I'm not sure at all. A long time ago the plugin had a bug related to something like that (a problem that happened when the multi-thread scene extraction feature was enabled), but it had been fixed and I had never seen this problem until these days ... I wonder if the problem could be related to something broken in Houdini 17.5 or something like that.

Only one question. Are you using materials from LiveDB? What I've found is that some materials in this database have weird names with space characters and international strings that are not good for Houdini. Perhaps the problem could be related to these liveDB materials, but I'm not sure at all.

Of course, if you can reproduce this problem and you can send me the scene, It could help a lot to try to find the origin of the problem.

Thanks,
-Juanjo

Thank you for the reply!

No I am not using LiveDB, but the idea that something could have changed in H17.5 isn't impossible for sure. I obviously haven't seen this issue before either until now, so H17 never did this.

My scene was really simple, but I guess I will try to remember to keep auto save on (not sure why it's off by default in houdini), and see how things go. A little scary though.

Yes, this is something that we must investigate. Corrupting the scene file is something critical that must be fixed for sure, but I need to know how to reproduce the problem ... if you can reproduce it again and you can send the scene, this could help to try to reproduce the problem here, find how it is possible and fix the problem.

Thanks,
-Juanjo

Hi,

After a long time trying to reproduce and find the source of this issue, we've updated the 4.04.0.2 and 2018.1.2.1 plugin builds, adding new code to try to fix these rare problems related to the scene corruptions reported by some users.

Hope it helps to fix this weird issue,
-Juanjo