Houdini Ocean Toolkit for Maya

khnli · 2015-11-19 09:31:03 UTC

its working in 2015 and not in 2016

acidream · 2015-12-29 11:11:00 UTC

I’m not able to get the MR shader for linux working in 2016, I’m getting a “call to undeclared function “hotOcean””, same for the vector displace.

I’ve had that happen before when I tried to use the 2015 shader in 2016 as a test. Are you sure the 2016 version is the one in the archive?

acidream · 2015-12-29 13:40:51 UTC

I’ve got it compiled for linux 2016 myself, phew. I’ve never been able to make it work before.

colt · 2015-12-30 11:53:59 UTC

Strange. Works for me here. Which MR version are you running?
I used a Maya 2016 with mental ray: version 3.13.1.2, Jan 21 2015, revision 236291
on a Centos 6.0.

Maybe some Distro related troubles. If you are bored you could run “ldd hotOcean.so” for me to see if something is not matching/found.
But congratulations for compiling it yourself. It’s too often the only viable solution on Linux. There are just too many flavours of it out there.

Cheers,
Nico

colt · 2016-02-27 05:34:16 UTC

I finally found some time to do the vray shader. So as a late christmas gift a vray shader for Windows is now included in the package. I tested it with Vray 3.10.01 in Maya 2016 on Windows.

A little vray test with 2 stacked shaders and one shaders jMinus for some fakefoam:

//youtu.be/PRN_M3ra4sk

I also added an OSX compile for the deformer made by Oliver Markowski to the package.

Cheers, Nico

bazuka · 2016-02-27 05:40:14 UTC

U r the man

great work my friend, send my regards to Oliver

dEnbom · 2016-03-14 11:45:18 UTC

Dayum Nico, what a treat. Another late xmas-present, first v-ray 3.3 and now finally a hot-shader, big thanks for this contribution.

I tested and it works sweeeet! Only thing I missed until I checked your examples was to connect the texture directly to the SG, haven’t seen that before, when I connected out col to a displacement-node’s vector slot it didn’t work. Maybe it’s just me but that might be something to clarify… Other than that all good here. Really good

:keenly:

colt · 2016-03-15 02:19:27 UTC

Good point about the displacement connection. I will update the readme file.

Did you test it with vray 3.3? I’m not sure if I need to recompile it for the update. We haven’t switched at work yet so I couldn’t test it.

Nico

dEnbom · 2016-03-15 04:42:22 UTC

Yup I’m on 3.3, works a charm!

colt · 2016-05-11 13:19:00 UTC

Added Windows/Maya 2016Ext2 for the deformer and MR shader. No Linux, if somebody desperately needs it let me know.
How time flies…

dEnbom · 2016-05-11 13:36:04 UTC

I think I speak for everyone here Nico when I say thanks so much for these updates and staying on top of things.

Uniel · 2016-05-23 02:18:46 UTC

Hey Nico,

Thanks for this plugin! I’m having trouble with the VRay Shader, using VRay 3.3 in Maya 2016sp5. It shows up fine in the 2D Textures list, but when I add it in Hypershade i get these errors:

shadingNode -asTexture VRayHotOcean;
// Result: VRayHotOcean2 //
shadingNode -asUtility place2dTexture;
// Result: place2dTexture2 //
connectAttr place2dTexture2.outUV VRayHotOcean2.uv;
// Result: Connected place2dTexture2.outUV to VRayHotOcean2.uvCoord. //
connectAttr place2dTexture2.outUvFilterSize VRayHotOcean2.uvFilterSize;
// Result: Connected place2dTexture2.outUvFilterSize to VRayHotOcean2.uvFilterSize. //
// Error: ERROR: Could not create plugin TexHotOcean ! //
// Error: ERROR: Could not create plugin TexHotOcean ! //
// Error: ERROR: Could not create plugin TexHotOcean ! //
// Error: ERROR: Could not create plugin TexHotOcean ! //
// Error: ERROR: Could not create plugin TexHotOcean ! //
// Warning: Unsupported texture VRayHotOcean //
// Error: ERROR: Could not create plugin TexHotOcean ! //
// Warning: Unsupported texture VRayHotOcean //

Any ideas what’s going wrong?
Thanks!

andreinfante · 2016-06-23 11:24:39 UTC

Hello, yes… great plugin! We used it in a project and worked perfectly!

I am having the same issue as Uniel:

// Error: ERROR: Could not create plugin TexHotOcean ! //

colt · 2016-06-24 03:14:40 UTC

This is usually the case when Vray can’t find the .dll from the shader, because the environment variable is not set up correctly.
Check by using

getenv "VRAY_FOR_MAYA2016_PLUGINS_x64"

as mel code. It should point to the folder with the dll.

You could also try copying the .dll into vrays bin folder.

If that does not work either take a look at vrays output when the plugin is loaded. It should print something like this:

[2016/Jun/22|11:44:54] V-Ray: V-Ray core version is 3.25.01
[2016/Jun/22|11:44:54] V-Ray: Loading plugins from “C:/Program Files/Autodesk/Maya2016/vray/vrayplugins/vray_.dll"
[2016/Jun/22|11:44:57] V-Ray: 74 plugin(s) loaded successfully
[B][2016/Jun/22|11:44:57] V-Ray: Loading plugins from "C:/Users/administrator/Documents/maya/2016/modules/Houdini_Ocean_Toolkit/vray/vrayplugins/vray_.dll” [/B]
[2016/Jun/22|11:44:57] V-Ray: 1 plugin(s) loaded successfully

If it finds the .dll but has a problem loading it, there will be an error message there.

Cheers,
Nico

andreinfante · 2016-06-24 10:22:50 UTC

Hello Nico, thank you very much for your response.

That did it!! I actually copied both files (txt and dll) into various directories until it loaded correctly your vray example scene.

Thanks!! =)

André.

dEnbom · 2016-11-11 13:16:55 UTC

Hej Nico,

Just wanted to check if there’s any chance of a 2017 build anytime soon?

Cheers /D

colt · 2016-11-13 11:07:23 UTC

Hi David,

with the new BOSS system in Maya 2017 I was thinking that HOT is rather outdated now and not needed anymore.
And it feels kind of that way since you are only the second person asking for a Maya 2017 version, even though 2017 is available for some time now. Usually people start mailing me as soon as a new Maya is released.

So, did you look at BOSS? Is it a valid successor? I only played with it, nothing serious. But it does look quite promising.

Cheers,
Nico

dEnbom · 2016-11-30 04:57:21 UTC

Hey Nico,

Well partly I agree, but partly I disagree. One of the major perks of boss is that it can combine spectral waves with collisions, and also easily influense a bifrost sim, but that we can do with hot too.

The thing is though, that I don’t see them as competitors. I see boss as something I use when I know I’m going to sim, and then I get simulated liquid for foam etc. But when I use HOT it’s more of a procedural approach that doesn’t have time for sim, and it also has capabilities that boss doesn’t have like access to vertex colors, presets etc. So for me it’s two different things.

If you find that the interest is so low I completely understand that you don’t want to spend more time release more versions especially since maya updates so often these days, just wanted to give my two cents. All in all thanks for the effort!

colt · 2016-12-06 13:46:32 UTC

Allright … I made a Maya 2017 compile for windows. The fun thing is that although I created and maintain this thing for 7 Years now, I personally never used it in any production. So I can’t really judge how it competes with other tools, i.e. Boss.

The new compile feels kind of slow, but I don’t have older Mayas on my new machine so I couldn’t compare it.
I even managed to get it to work partially with the parallel mode, as long as you don’t use the vertex colors. It still is slower than DG mode, because it somehow evaluates twice per frame.
But all in all I think the code needs an overhaul for all the api changes, which I lack the time and dedication to do. On the other hand I find it amazing that it still works after all these Maya versions. Autodesk really keeps some things backwards compatible.

If somebody desperately needs a linux version let me know. Since nobody wanted one for 2016 Ext2 I didn’t do one for 2017.

Cheers,
Nico

MartinGPP · 2016-12-09 15:00:53 UTC

very cool to see this implemented!