schwungsau

don't worry, it will change soon

or simpler. in source node add group name under "just born group" after you use any node (for example popvop) and use the source group name.

XPS graphics died.... after dell service guy came and replaced the motherboard, it got worse it run's hot after 20 minutes and shut it self down -->just throw it out and switched to apple. never issues or blurscreen --> never lookded back... i heard lot time people burn's CPU/GPU if it let it runs all day long under full stress. thats i never buy machine with highestg GHz. good cooled or Xeon's . thats why willl pay extra money and save me time for fixing /replacing stuff all the time.

i think you better of with blender, there a is lot Archviz stuff going on with it. (poliigon.com /blenderguru for example). you have all the render engine you need (cycles, eveee, vray, indigo etc..) and best modeling tools in the industry for this kind of work.

i had bad experience with dell XPS laptop, that's why i switched to mac book. best part is the apple service, they will replace your mac book even if it is 5years old. a friend of mine try get replacements for surface because it burn the CPU, they was laughing at him in Microsoft store. but i know a guy, which he is using his Dell Precision Mobile Workstation for years.

go with this one : http://www.cgchannel.com/2019/05/review-boxx-apexx-t3-workstation/ its better then building yourself... if spend so much money, you don't want crashing machine because of some hardware glitches with each other....

a lots of ways.... simple and fast way at pointwrangle after the add note ithe code int prim_points[]; float umap; addattrib(0, "point", "umap", 0.0); prim_points = primpoints(0, @primnum); for ( int i = 0; i < len(prim_points); i++ ){ umap = float(i) / (len(prim_points) - 1); setattrib(0, "point", "curveu", prim_points[i], 0, umap, "set"); } then you can add a "color" node --> set it ramp from attribute with curveu as attr.

this is a much better explanation of L-systems : https://natureofcode.com/book/chapter-8-fractals/

xeon clocked at 2.2 ? your GPU's will wait long time to get data....

i think, you have to set your particle size (pscale / width) to small number like 0.001......

its that's easy. written stuff for GPU needs 2 things, a host program and a kernel. the host program is usually written mid/high level language like (C, python etc..) the host program handles data management, complies kernels etc... the host program detect hardware GPU and complies and send the kernels to the GPU and feed the kernels with Data. in Houdini the openCL wrangle is the host program. the openCL Kernels (code/snippets) can only handle the data from local GPU/Memory which it got send from the Host program (OpenCL wrangle node). current openCL wrangle Houdini does not support multi GPU's. you have write you own openCL wrangle node via houdini API to make it happen, but you have to dive deep into parallel processing and data management or the GPU's sit there waiting most of the time for Data to be moved around. If you rewrite nodes as openCL version, you need basic routines first. openCL is pretty low level. you need to write function like noise, PCopen, neighbours, ramp's etc... based on lastest test Houdini does not take full advantage of shared memory nor does it use multi GPU's. Pyro or Vellum uses only little part of the GPU. I could get self written Kernels to use 100% of the GPU for simpler Operation. I know only handful software packages, which run entirely Simulation's on GPU's. I am not sure, but I think only Cuda can take advantage of NVlink right now.

i using classic Julia Fractal to drive my spline : cool spline (Mantra) and black-and-white

go through first 3 chapters here: http://www.scratchapixel.com/lessons/mathematics-physics-for-computer-graphics/geometry/points-vectors-and-normals it good explansion about vector's, Normal's etc...

thanks for sharing !

look nice !