"Prelaunch pb? 1" message on every houdini launch

   679   3   1
User Avatar
Member
55 posts
Joined: May 2017
Offline
Hello.

I'm getting this window message on every houdini launch.



This only happens with Houdini 20.5.332 and the latest 20.5.370.
I also have Houdini 20.5.278 installed, and it is not giving me the message.

I also tried to delete the houdini configuration folder but it keeps giving me that message.

I have another computer with Houdini 20.5.332, and there’s no message on Houdini startup. So I guess it’s something related to the installation on my main computer, but I have no idea what it could be...

Any possible solution to this?
Edited by Gagui - Sept. 29, 2024 13:56:19

Attachments:
screencapture.png (12.8 KB)

User Avatar
Member
185 posts
Joined: Feb. 2017
Offline
same here
User Avatar
Member
55 posts
Joined: May 2017
Offline
Apart from how annoying it is that this message appears in every Houdini session, I have confirmed that when I launch a render through Deadline, it is unable to start Houdini and keeps throwing errors. To be sure, I tested changing the version of Houdini that Deadline uses to render to 20.5.278, which doesn't show the message at startup, and with this version, Deadline has no problem rendering. So, this is more problematic than it initially seemed.
User Avatar
Member
1 posts
Joined: May 2020
Offline
Hey! I was also plagued by this startup warning, and it looks like it was related to my installation of BorisFx Sapphire OFX. I had installed a trial version to test out with copernicus, and after the trial expired, I removed my OFX_PLUGIN_PATH environment variable (I work in windows).

Turns out just doing this wasn't sufficient! The OFX plugin nodes and the "Prelaunch pb? 1" warning still kept appearing until I set my HOUDINI_DISABLE_OPENFX_DEFAULT_PATH to 1. Here's where I found all the info on these environment variables for more info: https://www.sidefx.com/docs/houdini/copernicus/openfx.html [www.sidefx.com] .

Now if you are still using these OFX nodes then disabling them probably isn't the solution, but maybe look at any OFX plugins you have installed to see if that's where the warning is coming from.
  • Quick Links