Jump to content
[[Template core/front/profile/profileHeader is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

AntoineSfx last won the day on March 2 2021

AntoineSfx had the most liked content!

Community Reputation

42 Excellent

About AntoineSfx

  • Rank
    Illusionist

Personal Information

  • Name
    Antoine L
  • Location
    France
  1. There is an even faster path than reply #1 Just add a Convert SOP after your 123456 polygon, with Bezier Curve Order 4, and check: interpolate through Hulls; this last option will add the points I was talking about earlier; then drop a Curve SOP after that and adjust the handles in Edit mode.
  2. Any polygon can be interpreted as a Bezier curve. All you need to do is add two points for each linear segment so that Curve SOP can interpret them as the handles. Two additional points per segment means that it must be interpreted as a Bezier Order 4 curve down the road; this is the order most program use because it's the most intuitive for us humans. If you want to go full procedural, split the polygon with convertline / facet (unique points), in a for loop over the primitives do a resample Max segments = 3, then put the segments together with a: polypath, connect end points. You can input this in Curve SOP, Bezier Curve Order 4 (the default) and you will have access to the Curve SOP tools to edit the curve interactively. You can also procedurally move the handle ( the points that were added at the Resample step) if you feel like it.
  3. I think I loaded someone else's file a while ago, and I've been having problems since - maybe it's something else, I really don't know. Basically I used to just type W in the viewport window, and it would toggle between a wired shading model and a smooth wired shading model. That's the only two modes I use on a regular basis. Now randomly I seem to be stuck in some mode, and typing W doesn't do anything. I'm sure it's following some logic, but I don't get it. Obviously I don't know how to change it back.
  4. I'm trying to have a sphere jump at some points in space when it's close to those points. I would like to have for one step of the dop, to have v + = dv_n , where dv_n is a point attribute on a curve that the sphere moves close to. I'm trying to emulate a player pressing a jump button once where the sphere is close to a given point The logic I'm using is this: in DOP, in Geometry VOP // The dv curve has points which have mostly dv=(0,0,0) except at some points where I want the sphere to jump the curve is connected to Geometry VOP input2 get the near point on the dv curve import dv_n attribute found on the curve at that point in space v += dv_n Doing only this, I get multiple d += dv_n depending on v. I'm trying to have an array which stores the points which have already been used so that I can ignore them for some time or forever. I'm not sure where the integer array should be stored though
  5. How to drive activation with SOP ?

    I'd love to see how to attribute transfer from a RBD Packed to a curve in a dop network. Then read data from that curve in order to drive Activation for example. I quite don't get the logic.
  6. How to drive activation with SOP ?

    you can't attribute transfer in DOP, and in SOP upstream from dopimport, it's a fixed object.
  7. How to drive activation with SOP ?

    Because I don't know when it needs to be active. I only know where it needs to be active, i.e as some information in SOP.
  8. Say I have a RBD Packet Object and a bunch of obstacles to jump over I have a velocity Impulse force that needs Activation set to 1 at various locations in space and maybe a direction , i.e a bit before the object reaches the obstacle. In DOP, how do I get those values from a SOP context ? I would like to set some points and vectors somewhere, and use those as an indication as to where and how much the object should jump
  9. How can I convert a point cloud to a surface?

    Using third party tools: Meshlab 2021.10 Import Mesh the point cloud as OBJ file 1/ Compute Normals for Point sets 2/ Surface Reconstruction: Screened poisson (those are the full names of the functions, you can type them in the upper right magnifying glass search field) I can't elaborate too much on the parameters, but you should be able to reconstruct the surface in some case, especially if the point cloud still looks like a surface, not your use case, as it will output a surface, but something that doesn't really look like the original rubber toy I think it works well for example, to rebuild the mid section of a character if the hole size is in the same ballpark as the average distance between the points; otherwise the rebuilt surface will not bridge the two parts together. Lots of parameters to play with though...
  10. Place a point on center of surface

    primuv can help I don't know the relationship between the P value computed by uvsample, and say, the P value the renderer is using when rendering the primitive, but you can try this Those are 2 for loops, iterating on primuv for values in [0;1] The input is is single non planar primitive, not a surface. Houdini is doing something do parametrize the surface (intrinsic UV), but I don't know what it's doing. You can skip all the loops and try this in detail wrangle: vector p = primuv(0,"P",0,set(0,1,0)); int center = addpoint(0,p); setpointgroup(0,"center",center,1,"set"); The set(u=0,v=1,w=0) reads like this: u= location on the perimeter (in 0;1) v=distance to the edge ( 0= on the perimeter; 1=center) w= not used in this case So set(0,1,0) defines a point that somewhere at the perimeter of the primitive, that is projected towards the center (v=1) It should give you some kind of center to the primitive. HTH
  11. For example, Topo Transfer can be quite expensive. I don't mind spending 15 minutes of CPU for the result, but changes upstream trigger a solve. Is there a way to make it save results somehow ? Lately I've been stashing the result, but it's a bit too manual for my taste.
  12. Free Pig Head Sculpt

    Maybe they could have offsprings ?
  13. It turns out, Topo Transfer' ing a high resolution sphere, with polar UV and the original texture assigned to it to help pick the features -- is doing the job just fine Just took 15 minutes at 1,600 % CPU usage on my trusty dual Xeon 32 cores workstation. Now the resulting surface obviously doesn't match the original person head, but that's the point of projecting it on a geometry with a known good topology for easy tweaking Also, a few problems exist on the back UV seam.
  14. Can you quote the source and the use case ? 400 lines of Python is a bit rough to start with.
  15. There is a high resolution free sample here https://www.3d.sk/photos/show/id/949587 What method can we use to generate the UV on testmodel head so that the texture fits the head ? It looks like it's a job for topo transfer but it's not exactly in the same attribute space. Ideally something like defining landmarks on two geometries and have topo transfer match the two topologies. Or maybe something like UVFlatten with a seam on the back of the head, and some constraints to make it look like the texture. I have not tried this method though Any thoughts ?
×