Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 05/28/2026 in Posts

  1. Hi Here is my approach to this effect: chain.mp4 magnetos_stick_02.hip
    2 points
  2. Particles and Anticipation. Have Fun . proc09.h
    1 point
  3. Try to adjust closer to worldscale, based on this collision padding and amount of bullet substeps. Check constraints, seems something messed up here. Also, PY position initially is under the ground what doesn't help.
    1 point
  4. Simple way to define magnetic side initially, more fun is to find out side on fly by availability, distance etc. magnet_chain_v01.hipnc
    1 point
  5. there were a few issues. 1) there was no velocity attribute before the rasterize_velocity node 2) pumps are affecting volume velocity so they need to be plugged in the volume velocity input of the Flip solver. 3) the FLIP object doesn't have a pump field by default in H18, you can create one and resize it. FluidPump_V02.hipnc
    1 point
  6. I have a similar desire. My workaround for now has been to to create a label parameter for each parameter I want control over. Perhaps it will soothe your needs too until there's a better solution. For a left-justified label above the float(most easily accomplished) I would do the following: make a string: Strmylabel# -- you can add some kind of default expression to read in whatever you need or let the user adjust this -- if you are setting it yourself then make this parm invisible make a label: mylabel# -- turn off 'Main Label', turn on 'Horizontally Join to Next Parameter', and turn on all 16 labels -- In 'Label 1' put "<additional common words such as 'controls for: ' >`chs('Str' + substr($CH,0,strlen($CH) - 1 ))`<additional common words such as 'controls' or >" (you need '-1' because once you have more than Label 1 turned on the labels get additional #s added to the end so you don't want to get that number also) make a seperator: <doesn't matter> -- this will just help fill in rightspace so your label stays left-justified make a float: myfloat# -- turn off 'Main Label', setup however you want If the string parm is set to "hello3" and Label 1 has "Controls for: `chs('Str' + substr($CH,0,strlen($CH) - 1 ))` Objects" in Label 1 would yield the label: Controls for: hello3 Objects For right-justified labels that look like the normal label in-line with your float you can remove the seperater and move the Label expression to 'Label 16' replacing '-1' with '-2' since 16 is 2 digits long instead of 1 digit long. This method will force everything to the far right of the parameter interface You can do other similar things with attributes being read in using something like the following in the Label: `detailsmap(0,'myAttribute', opdigits( substr($CH,0,strlen($CH) )) )`
    1 point
  7. Solved by Peter Sanitra @ Redshift Render community facebook group. Uploading the updated hip file. So: 1. you have to compute the velocity of points before the boolean, then use a atribute transfer to transfer the velocity from that preboolean to the new boolean geo. 2. go to redshift per object parameters (OBJ level) - Settings - Render and activate Deformation Blur From Velocity Attribute , so you force redshift to compute the motion from your velocity atribute from points. Done! I hope my full morning investigation will be usefull for you guys! Keep growing! mberror_solved.hiplc
    1 point
×
×
  • Create New...