Jump to content

BlackPariah

Members
  • Content count

    29
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

1 Neutral

About BlackPariah

  • Rank
    Peon

Personal Information

  • Name
    Jack D.
  • Location
    Canada
  1. Hello! I can't wrap my head around this one. I applied some random colors on the primitives with the default @Cd attribute & set the roughness to 0.1 on the principled shader. The colors show up and everything seems to work fine. BUT, just as a test, I tried to bind a custom roughness attribute with the same exact roughness values (0.1 on all primitives, just like it's set on the shader) and when I plug it in, the colors don't come through... I get a black & white render instead. I am lost as to why the shader/renderer is behaving this way... logically the outcome should be identical & I have no idea why the colors disappear. custom_shader_attribute.hipnc
  2. Hello! I can't figure out why the bind vop inside the material network will not grab a primitive float attribute from the geometry. I just made a simple float primitive attribute with some random values & want to use it as a roughness parameter on the principledshader material. *EDIT* Oops! Nevermind! it's working! By some luck I named the attribute "rough" which is the actual default attribute name for the shader's roughness... so it was reading the attribute directly without needing a bind vop.
  3. New PC only for Houdini

    It looks like Renderman will support raytracing acceleration with the Nvidia RTX cards! Probably other renderers might follow... So for rendering I think it would be worth waiting for RTX... and AMD gpu's are outclassed in this department. Speeding up Pyro & other sims that run on OpenCL is the only situation that might make AMD gpus somewhat useful... But I cannot recomment them just for that limited usefulness so please disregard my first reply.
  4. Channel parameter from a variable

    Yes that did it! Thank Atom!
  5. Channel parameter from a variable

    That's a bummer :| I was planning on using the output to drive parameters on other nodes (copy/paste relative reference etc..) I don't know anything about python... just learning vex is daunting enough for a non-programmer lol. But it's good to know that the functionality is missing at the moment. Does SESI have any plans to add it? Something like: ochf("parametername", myvariable); to output a float channel would be nice :s
  6. Hello! I'm trying to create a channel parameter but with the exception that I want it's input or it's value to be driven by a variable & not a user input/slider. Am I even going about it the right way? I just want to get my variable (it's just a float) out of the vex wrangle and on to the UI at the bottom. So basically the opposite of pumping a value into a wrangle. Is this even doable? Channel_Parameter_from_variable.hipnc
  7. New PC only for Houdini

    Here is a quick build I put together just to get a ballpark figure... https://ca.pcpartpicker.com/list/QqPmmq
  8. New PC only for Houdini

    1600$ and up for 128GB DDR4 quad channel matched kits... assuming your mobo has 8 DIMM slots. Pretty much all ATX TR4 socket boards come with 8 slots. ( 8 x 16GB modules). https://www.newegg.ca/Product/ProductList.aspx?Submit=ENE&N=100007610 600563496 601190328&IsNodeId=1&bop=And&PageSize=36&order=BESTMATCH And around half that for 64GB kit (4 x 16GB modules). https://www.newegg.ca/Product/ProductList.aspx?Submit=ENE&N=100007610 601190328 600336949&IsNodeId=1&bop=And&PageSize=36&order=BESTMATCH
  9. Polyexpand failing in a for loop

    I'm getting the same error copying an expanded line to a bunch of points. The only difference is my polyexpand node is outside the loop... I think the node might have a problem with data coming out of a for each loop in general.
  10. Orient attribute

    Awesome! Looks like exactly the problem I'm having! Thanks Jasper
  11. New PC only for Houdini

    2950X is the 2nd revision of 1950X... almost the same but 2950X is slightly more power efficient & is a bit faster (you might get better overclocks with it, if you plant to OC) Clock for clock they are the same but stock 1950X turbos to 4ghz while 2950X goes 4.4ghz. NVME SSD drives are almost all M.2 slot types running on the PCI-E bus. For Example this drive is quite fast & not too expensive (up to 3.2 gibabytes/second read performance, PCI-E 3.0 spec at x4) --> Samsung 500GB 960 EVO NVMe M.2 Internal SSD. For graphics, I would also consider AMD's latest GPUs since their OpenCL performance is significantly better than Nvidia's for a given pricepoint. For Example: RX Vega 56 has a 32 bit float performance of 10.5 gigaflops. Vega 64 at 12.7 gflops. Compared to 1080Ti's at around 11.3 gflops. Also AMD's cards are significantly faster in 64 bit and 16 bit compute. As for Nvidia's RTX, I'm not sure how Houdini would take advantage of Nvidia's RTX since Mantra is a CPU renderer.
  12. Orient attribute

    Hello! I'm trying to create an @orient attribute on a simple circle (so the copies all point inwards towards the center of the circle) I laid down a polyframe & fed it's generated @N and @tangentu attributes into a quaternion VEX function but it's a no go. From what I gathered, I'm missing an "up" vector & a transform matrix & I'm not sure how to set this up with a wrangle... Orient_attribute.hipnc
  13. IF condition result makes no sense

    That did it lol. Not sure why I didn't have to use the "op:" in the For Each copy tutorial in the help... Same "point" function, didn't need "op:"... strange. The exact line in the exercise was: point("../foreach_begin1", 0, "divisions", 0) I think because it's a "point" expression & not a "point" vex function... ahhh, contexts contexts... Thanks again toad!
  14. IF condition result makes no sense

    I ran into another small problem :-| It's with the "point" function this time. I want to specify a specific node to grab the attribute from, rather than input 0, 1 etc... The help states that the geometry parameter can be a string... so I put a relative path but it's a no go. Point_function_geometry_parameter.hipnc
  15. IF condition result makes no sense

    I assumed I could just directly fetch it with the dot "." operator... good to know! And indeed it works now! Thanks toadstorm
×