itriix
itriix
About Me
Connect
LOCATION
Not Specified
WEBSITE
Houdini Skills
Availability
Not Specified
Recent Forum Posts
Help is still broken! April 8, 2017, 10:56 a.m.
Yep, still not working properly using daily build 16.0.570. bug id #79188.
Old vs. New Point SOP March 22, 2017, 6:59 p.m.
Will do.
Yeah - a context-sensitive expression list sounds pretty good too.
Probably something flawed with my logic here but my thoughts were to just have an additional “Attribute/Self Value” parameter field that could represent “self” sitting right under the Constant parameter text boxes.
In the VEXpression box - “self” could then just reference this “Attribute Value” just like “value” references the “Constant Value”. When you change the “Attribute” pull-down menu option, it updates the “pre-defined” values, like @P.x, @P.y, @P.z in the “Attribute/Self Value” parameter fields. Something like in the image below:
I guess this doesn't really solve the original issue with the Point SOP - because it looks like it would just re-introduce the same problems as before. Hmmm… Maybe 3 VEX snippet boxes instead of 3 parameter value boxes? Each pre-set to write to an individual attribute component under the hood?
As for Constant Value - yeah that one seems a bit tricky. Possibly have a toggle for it.
Yeah - a context-sensitive expression list sounds pretty good too.
Probably something flawed with my logic here but my thoughts were to just have an additional “Attribute/Self Value” parameter field that could represent “self” sitting right under the Constant parameter text boxes.
In the VEXpression box - “self” could then just reference this “Attribute Value” just like “value” references the “Constant Value”. When you change the “Attribute” pull-down menu option, it updates the “pre-defined” values, like @P.x, @P.y, @P.z in the “Attribute/Self Value” parameter fields. Something like in the image below:
I guess this doesn't really solve the original issue with the Point SOP - because it looks like it would just re-introduce the same problems as before. Hmmm… Maybe 3 VEX snippet boxes instead of 3 parameter value boxes? Each pre-set to write to an individual attribute component under the hood?
As for Constant Value - yeah that one seems a bit tricky. Possibly have a toggle for it.
Old vs. New Point SOP March 22, 2017, 1:22 p.m.
I'm all about the efficiency improvements and I understand measures needed to be taken to make that happen. For myself and many others, i'm sure it didn't take long to adapt to the new approaches, but my initial response was from the perspective of an educator, teaching students between undergrad to grad level - with widely varying experience in cg.
At the one end of the spectrum, the changes are welcomed, at the other end, a little more technical explanation is now needed to get them up and running. Not that it's a bad thing, it just requires approaching educational material from a different angle. In the end, it's for the benefit of all the Houdini artists.
So, I guess it's time to say goodbye to those we've lost - I surely hope the Point, Copy and Group SOP's got proper burials. It better have been epic! We had some amazing adventures! Out with the old, in with the new! I look forward to the better, brighter future of Houdini.
~ I still retain that the Attribute Expression SOP could use some work.
At the one end of the spectrum, the changes are welcomed, at the other end, a little more technical explanation is now needed to get them up and running. Not that it's a bad thing, it just requires approaching educational material from a different angle. In the end, it's for the benefit of all the Houdini artists.
So, I guess it's time to say goodbye to those we've lost - I surely hope the Point, Copy and Group SOP's got proper burials. It better have been epic! We had some amazing adventures! Out with the old, in with the new! I look forward to the better, brighter future of Houdini.
~ I still retain that the Attribute Expression SOP could use some work.