Hey guys,

I'm testing the new Houdini 14.0.379, and when I load any otl in Maya all of the parameters are zeroed, and there is no connection between the parameters and the Engine.

Anyone else is experiencing a similar behavior?

Thanks
Alex



The last version I was using was 14.0.335, Maya 2014, Linux.

Hm, that's strange. The parameters seem to be working fine for me. Are there any errors being outputted to the script editor, or to the shell?

Could you try this test asset? It's just be a simple sphere SOP with parameters promoted.

This is really strange Andrew!!

All the new otls work fine but the old one's don't.
What's even more interesting is if I add parameters to the old otl, the new parameters work fine while the old ones don't.

Any ideas?

Thanks
Alex

I just created an asset from 14.0.335, and loaded it into Maya with 14.0.379, and the asset works fine. This is strange.

If you create a simple asset with 14.0.335, and load it into Maya with 14.0.379, can you reproduce the same problem?

No I can't! No idea what's going on. A bunch of my old otls are not working. :?

I attached an example.

I can reproduce the problem. The problem seems to happen with parameters that are within a folder. My current guess is that I broke something related to folders while implementing ramps. ops:

Thanks Andrew!!
Glad it's not just me. I was going crazy here, thinking it's something to do with our toolset or Houdini installation.

I managed to fix the problem. The fix should be in tomorrow's build (14.0.382).
Sorry about that! ops:

Awesome! Thanks a million Andrew!!

Hey Andrew,

Regular parameters work now, however, now the ramps come in blank and are not affecting the engine.

in version 379 the ramps were actually the only parameters which worked I think. Now it's the other way around.


Let me know if you need another example otl or anything else I can help with.


Thanks a lot
Alex

I made a fix (again) yesterday for these parameter problems. The fix should be in today's build (14.0.386). Please give it a try.

Hey Andrew,

Thanks a lot for your hard work! We are already using v386 and ramps are working.

One issue we are experiencing is every time you add a new point to the ramp it reloads all the attributes. It is very annoying especially with us overriding the Engine template file and collapsing all tabs by default.
Is there anything you or we can do to prevent it from reloading every time?


Alex

We are also experiencing quite a few freezes and crashes which I can't really point at what is triggering them.

Few artists experience freezes when messing around with the ramps parameters.

Another issue we have been experiencing is Maya crashes when we rebuild the Engine asset if we introduce new parameters in the otl.

Also, loading/saving presets crashes Maya often.

As I said, it's hard for me to point exactly at what is triggering all of the above but it's quite unstable overall. I'll do my best to come up with actual example files which demonstrate the issues.

Any thoughts to what can be causing this?


Thanks a lot!

i have tested the houdini engine some time ago(end of last year) and there i found out that some plugins in combination with houdini engine makes maya instabel and it will crash. but i don't know if it's still today that case… maybe you can test if you disable some 3rd parties plugins.

just as a hint

Afeigin
One issue we are experiencing is every time you add a new point to the ramp it reloads all the attributes. It is very annoying especially with us overriding the Engine template file and collapsing all tabs by default.
Is there anything you or we can do to prevent it from reloading every time?

One way to get around it might be pop up the bigger ramp widget (by clicking the “>” button) and do the editing there. This might be tricky to fix. I need to look into this some more.

Afeigin
Another issue we have been experiencing is Maya crashes when we rebuild the Engine asset if we introduce new parameters in the otl.

I made a fix on Friday for this crash. The fix should be in 14.0.390 or later.

I still couldn't reproduce the other freezes and crashes though. What were the artists doing right before the freeze/crash? Were they adding a point? Removing a point? Moving an existing point? If possible, it might be useful to get a stack trace of the freeze/crash too.

The freezes happen when artists move the points and adjust values. Not adding or removing points.
It seems to happen less often now. I'll try to get more information if it keeps happening.

We'll try the new version some time this week. It takes a while for us to install new software and integrate it into the pipeline even for testing.

Thanks a lot Andrew! Overall things are improving a lot