• ourouk
  • Wanting the recipes
  • Email
  • Posts 178
  • Reputation 1
  • Member Since
  • Last Active
Email
All Posts Topics Started Likes
SOuP 2017-02-27
Thanks Peter !
Another awesome update :)
0 0
SOuP 2017-01-29
Thanks Peter !

About KdTree, I read about it online ( and on the forum ), it is related to "nearest neighbour" right ? like the pcfilter/pcopen in Houdini ?

thx
0 0
Nonlinear Regression
Thanks ! will check that asap.
0 0
[MAYA BUG] - New value in remap_array at file opening
Yeah I understand...

My guess would be that Maya has already so much spooky error messages that one more should not be a problem :p

Btw it's neither a satisfying solution...
0 0
[MAYA BUG] - New value in remap_array at file opening
Hello,

That problem is not related to SOuP as I saw it in standard Maya nodes ( fluidshape especially ). But I just see that in the new remap array ( SOuP 17/01/25 ).

I have a new "value" (white) which is appearing at the position 0...

Any idea where the problem comes from ? or how to workaround it ?

thx




0 0
Nonlinear Regression
Very interesting MOAB !
Could u send higer rez screenshot please ?
Having hard time actually to decode your network/attributes/connectionss :)
0 0
SOuP 2017-01-25
Yes !
Thanks Peter
0 0
Ramp parameters ?
MOAB wrote: In my setup I remapped the weight values with the BE_Ramp.
What I did is I created a point node to assign weight values for each vertices depending on the rows & columns of the mesh... each vertices on a row will have the same weight values. The first row vertices will have a value of 0 while the last row vertices will have 1.0. For that I used the modulo operator. Then I remapped the weight values with the BE_Ramp and I used those remapped values with the peak node to push vertices along their normals.


Wow very nice ! thanks for the information, will try that too.
0 0
Ramp parameters ?
pshipkov wrote: Just spent a moment to add a ramp lookup to the remapArray node. Will be in the next update.
Let me know if you need it and i can try to provide you with a one off build.


I don't "need" it as I managed to remap my attribute.
But thanks for the ramp lookup, I'll use it as soon as the next update is out.
0 0
Point node : auto evaluate on $NODE.attr changes
Yes thanks,

I was not doing that this way. 
It sounds better.
thanks
0 0
Ramp parameters ?
I saw about BE_Ramp but didn't know about using it with "standard" attributes ( not related to any vdb )
I am working on something close to a tornado too ;)

Thanks, will check that.

EDIT : don't seems to work as I am remaping a radiusPP attribute ( from a point node )...

point1 > BE_ramp > displayComponents ( DisplayComponents only display the [1] value of the ramp )
0 0
Point node : auto evaluate on $NODE.attr changes
Hi,

Is it be possible for the point node to reevaluate when an attr used in the expression changes ?
I actually have to clic on apply or to change frame, to get it reevaluated.

I have something like : $R = $RADIUS*$NODE.radMult

thx
0 0
Ramp parameters ?
Hello everybody,

Is there a way to remap an attribute from a point node with a ramp ?

Something like in Houdini VOP :  attribute > fit > ramp parameter ( spline or RGB ) > attribute

thx
0 0
SOuP 2017-01-15
roshanfx1 wrote: Hi..Rendering the fluid exported VDB mesh is rendering fine but its voxelated..Maya 2017 Arnold


Hi, I think it's BE_openVDB related and not SouP, btw did u set the density layer to "density" in the BE_VDBArnoldRender ?
0 0
count post selected

Add a Website Forum to your website.