PyroFx, OpenCL ON ->clBuildProgram (-11) Error.

   8036   5   0
User Avatar
Member
20 posts
Joined: Dec. 2011
Offline
Hello i'm new to Houdini and may ask some dumb questions so be gentle)
Just installed 12 (free) and tried to test new pyroFx, but when i turned on OpenCl checkbox in pyrosolver got this in console:

OpenCL Exception: Error in processing command line: Don't understand command line argument “Effects”!clBuildProgram (-11)

I have 580gtx 3gb, latest drivers (295.73). Should i install something else? afaik opencl is included in nvidia drivers package.

Thanks in advance.
User Avatar
Staff
2493 posts
Joined: Sept. 2007
Offline
Hi ho! Since you're new here, you probably didn't see this sticky note at the top of the thread on how to log bugs, so here you go!
http://www.sidefx.com/index.php?option=com_forum&Itemid=172&page=viewtopic&t=15702 [sidefx.com]
Chris McSpurren
Senior Quality Assurance Specialist
SideFX
User Avatar
Member
20 posts
Joined: Dec. 2011
Offline
ok.thanks. I just didn't think it's a bug.
User Avatar
Staff
2493 posts
Joined: Sept. 2007
Offline
No worries! Thanks!
Chris McSpurren
Senior Quality Assurance Specialist
SideFX
User Avatar
Staff
6219 posts
Joined: July 2005
Online
From Houdini's textport (Alt-Shift-T) type
echo $HFS
This likely gives a path with spaces in it. Windows is supposed to have contracted this path into a ~ path without spaces, but it's been known to fail on some systems.

Can you please try re-installing Houdini into a path with no spaces to see if it fixes it?

If this is the problem, we can add a “” guard to the offending command line argument.
User Avatar
Staff
6219 posts
Joined: July 2005
Online
First, note that we try very hard to make sure $HFS doesn't have spaces. If you
echo $HFS
from inside hbatch and get a path with spaces, the Windows short path name conversion has failed. As far as we can tell, this is likely caused by the registry entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation
If that is 1, new directories won't get a shortpath made, so Houdini will have to use a path with spaces. Which isn't the end of the world because we *also* try to support paths with spaces everywhere.

For example, we now apply “” around the paths when we send it to the OCL compiler if the path has spaces. This should properly protect the path.

Unfortunately, some google work reveals that several OCL implementations ignore the “” when parsing the path, so will still fail to compile.

If this happens to you, you can either re-enable the short file path name creation for the installation of Houdini, or probably simpler, just install Houdini into a path without spaces. Note that the Program Files directory likely already has a short name, so you can install into c:\Program Files\, so long as the succeeding directories don't have spaces.
  • Quick Links