Brian R Hanke

I suppose I could, but it's essentially 1) Load Houdini Solaris 2) Enable MoonRay 3) Doesn't work. :P I haven't heard of a single person getting Open MoonRay working in...

Here's another clue. I tried rendering a simple scene to MPlay with MoonRay. (The scene works in Karma/MPlay.) Got this in the console: "[TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for 'TF_DEBUG_REGISTRY'....

1. Launch Houdini 19.5.534 from the console in CentOS 7. 2. Load attached scene and click Render to MPlay in rendersettings1. 3. Check console for above errors. [moonray_error.zip](https://github.com/dreamworksanimation/openmoonray/files/11057416/moonray_error.zip)

@solomon-s2020 For me the solution was to build MoonRay using the Houdini USD libraries. A standard MoonRay build using the official build guide won't work in Houdini.

@knightcrawler25 Aha, there is indeed a problem there: ``` -- Looking for a CUDA compiler -- Looking for a CUDA compiler - NOTFOUND -- No CUDA support ``` I've followed...

Great, it's working now! Thanks a lot for the help. :)

I might be able to help with this! I'm knowledgeable about OCIO and I'm interested in making it more accessible and user friendly. I get by in C++ and Python...

I already patched that config to work with Gaffer 1.4. Here's the old one that showcases the issue: ``` ocio_profile_version: 2.1 environment: {} search_path: "" strictparsing: true luma: [0.2126, 0.7152,...

Anything that makes it easier to install MoonRay on different distros would be very welcome!

@nyue I don't know what that is, so I'm not sure I did get past! I just followed the Windows build guide. I already have a VM set up with...