Aller au contenu

popol

Members
  • Content Count

    813
  • Inscription

  • Dernière visite

  • Days Won

    67

Reputation Activity

  1. Like
    popol got a reaction from TChadail in Avenir des forums   
    Aller hop on verra bien ce que ça donne
    https://discord.gg/BMQTMCcvuQ
     
  2. Thanks
    popol reacted to Nicolas Caplat in Avenir des forums   
    Salut tout le monde,
    Après avoir reçu un email de @Troadegrafix, je me suis dit qu'il était certainement plus judicieux de répondre directement ici. On va essayer de couvrir tous les sujets:
    - @kilkil3d "pourquoi migrer ?" -> j'ai tendance à penser que, quitte à continuer, autant le faire sur de nouvelles bases. A tort ou à raison, je ne trouve pas ça très sain de continuer à utiliser des forums qui portent le nom d'un absent (qui, au passage, continue à payer l'hébergement). Donc, pour résumer, si ce type de forums francophones doit perdurer sans Matt, autant le faire à 100%.
    - "pimper" ce site -> je ne vois pas trop ce que ça implique, mais si ça vous amuse, why not. Pour info, je dispose d'un accès admin, donc pleins pouvoirs sur le site. Je peux tout à fait laisser ces infos à quelqu'un si besoin. En revanche, certaines choses nécessitent des informations que seul Matt détient (compte Invision Community pour update, accès FTP ...) ... d'où ma suggestion de repartir sur un autre site, pour lequel 2 ou 3 personnes maxi auraient les infos permettant une administration complète du site.
    - pour la migration des données actuelles des forums -> aucune idée de la faisabilité de la chose, c'est peut-être juste un fantasme. A moins d'utiliser la même techno (Invision), mais est-ce réellement pertinent ?
    J'espère avoir répondu à l'essentiel de vos questions. Si nécessaire, je reste joignable par email, SMS, téléphone et LinkedIn.
    Portez-vous bien !
    ++
     
  3. Like
    popol got a reaction from archimi in Avenir des forums   
    J'ajoute des sections forums sur discord histoire d'être moins perdu https://discord.gg/BMQTMCcvuQ

  4. Like
    popol got a reaction from Yanosh HRDY in Avenir des forums   
    J'ajoute des sections forums sur discord histoire d'être moins perdu https://discord.gg/BMQTMCcvuQ

  5. Like
    popol got a reaction from Troadegrafix in Avenir des forums   
    J'ajoute des sections forums sur discord histoire d'être moins perdu https://discord.gg/BMQTMCcvuQ

  6. Like
    popol got a reaction from XYZ in Avenir des forums   
    Aller hop on verra bien ce que ça donne
    https://discord.gg/BMQTMCcvuQ
     
  7. Like
    popol reacted to manoro in Avenir des forums   
    idem!
     
  8. Like
    popol reacted to Yanosh HRDY in Avenir des forums   
    inscrit!!
  9. Like
    popol got a reaction from Yanosh HRDY in Avenir des forums   
    Aller hop on verra bien ce que ça donne
    https://discord.gg/BMQTMCcvuQ
     
  10. Like
    popol got a reaction from Yanosh HRDY in Avenir des forums   
    triste mais pas étonnant  en tout cas merci pour tout et bonne continuation  a toi ! 
    on va pouvoir aller te spammer sur linkedin XD
  11. Haha
    popol got a reaction from Nicolas Caplat in Avenir des forums   
    triste mais pas étonnant  en tout cas merci pour tout et bonne continuation  a toi ! 
    on va pouvoir aller te spammer sur linkedin XD
  12. Sad
    popol reacted to Nicolas Caplat in Avenir des forums   
    Salut tout le monde,
    Bon, je ne vais pas y aller par quatre chemins: après plusieurs années à porter à bouts de bras ce forum, je jette l'éponge.
    D'une part, je ne souhaite plus y consacrer autant de temps que par le passé, et d'autre part, mon quotidien professionnel n'a à présent plus grand chose à voir avec les préoccupations de l'archviz, m'éloignant ainsi encore plus de ce forum. L'absence de Matt sur son propre forum compte aussi un peu, quelque part ... bref, peu importe.
    Pour celles et ceux qui souhaitent rester en contact avec moi, le canal à privilégier est mon LinkedIn, le seul réseau social sur lequel vous me trouverez. Mon site web restera actif pour le moment, et sera peut-être amené à évoluer, qui sait.
    Enfin, si quelqu'un est intéressé pour mettre sur pieds une plateforme d'échange pour la communauté arvchiz francophone, sachez que j'avais déposé il y a quelque temps un nom de domaine artiste-archviz.org, que je possède encore jusqu'au 27/01/2024, et que je cèderai volontiers, gratuitement évidemment.
    J'ai pris un grand plaisir à fréquenter ce forum, à aider quand je le pouvais, à plaisanter dès que c'était possible (pardon à ceux qui m'ont trouvé lourdingue, et pour ceux qui ne pigent pas le second degré ... pas mon problème). Prenez soin de vous et de ceux qui comptent pour vous et kiffez
    A bientôt !
     

  13. Thanks
    popol got a reaction from Nicolas Caplat in Export nuage de points ?   
    Tu as sequoia de thinkbox qui est vraiment bon, https://aws.amazon.com/fr/blogs/media/aws-thinkbox-products-now-available-free-of-charge/
  14. Like
    popol got a reaction from TChadail in Export nuage de points ?   
    Tu as sequoia de thinkbox qui est vraiment bon, https://aws.amazon.com/fr/blogs/media/aws-thinkbox-products-now-available-free-of-charge/
  15. Confused
    popol got a reaction from kilkil3d in URSAFF ou MDA - fiscalité   
    ouai triple ouf, comme bande de br****** la CIPAV on fait pas mieux. 
    Première cotisation première erreur,  débité de 13000€ :| ,3 mois pour rectifier le tir...
  16. Like
    popol got a reaction from TChadail in œuvres d'art modernes?   
    Check les sites des musées, beaucoup ont des scans 3d format .stl (et autres) d'oeuvres d'art, tu as du modern qui traine également mais plus rare.
     
    https://www.musee-rodin.fr/recherche/fonds-patrimoniaux-et-documentaires-du-musee/fonds-historiques-et-archives-institutionnelles/archives-institutionnelles/fichiers-3d
    https://www.bmimages.com/3d-scans.asp
     
     
  17. Like
    popol got a reaction from Nicolas Caplat in œuvres d'art modernes?   
    Check les sites des musées, beaucoup ont des scans 3d format .stl (et autres) d'oeuvres d'art, tu as du modern qui traine également mais plus rare.
     
    https://www.musee-rodin.fr/recherche/fonds-patrimoniaux-et-documentaires-du-musee/fonds-historiques-et-archives-institutionnelles/archives-institutionnelles/fichiers-3d
    https://www.bmimages.com/3d-scans.asp
     
     
  18. Like
    popol reacted to Nicolas Caplat in 3ds Max 2023, Maya 2023   
    Long story short: on a développé notre pipeline sur 3dsmax 2022, notamment le gros Maxscript que j'ai du mettre au point (merci @SugaR d'ailleurs), et il n'était pas question de changer quelque chose qui fonctionne en cours de route. La release de notre produit est prévue pour mars prochain, on verra ensuite si on update vers 3dsmax 2023 et la dernière version de DataSmith, ce qui impliquera entre autres des ajustements dans mon code.
  19. Confused
    popol reacted to magnet_00 in Je n'arrive pas a trouver ce "material standard"   
    Bonjour Je narrive pas a trouver ces fenêtres et les mettre dans cette disposition 
    pourriez vous m'aider svp merci 

  20. Thanks
    popol got a reaction from Nicolas Caplat in Vol d'images ...   
    J'ai republié ça, faut pas hésiter a exposer ce genre de truc
  21. Sad
    popol reacted to Nicolas Caplat in Vol d'images ...   
    Hello,
    Partagez, faites tourner, commentez, please: https://www.linkedin.com/feed/update/urn:li:activity:6985932987582304256?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A6985932987582304256%2C7006917539322605568%29
    Même si ce n'est plus mon gagne-pain aujourd'hui, je pense à celles et ceux à qui ça peut arriver !
    Merci
     
  22. Like
    popol got a reaction from SugaR in VEX Wrangle Cheat Sheet   
    Global Variables
    A list of variables available in wrangles. The type indicator isn't necessary, but included as a reminder.
     sidefx

    Available in all SOP wrangles
    f@Frame     //The current floating frame number, equivalent to the $FF Hscript variable
    f@Time      //The current time in seconds, equivalent to the $T Hscript variable
    i@SimFrame  //The integer simulation timestep number ($SF), only present in DOP contexts.
    f@SimTime   //The simulation time in seconds ($ST), only present in DOP contexts.
    f@TimeInc   //The timestep currently being used for simulation or playback.
    Available in Attribute Wrangle (point, vertex, primitive and detail)
    v@P         //The position of the current element.
    i@ptnum     //The point number attached to the currently processed element.
    i@vtxnum    //The linear number of the currently processed vertex.
    i@primnum   //The primitive number attached to the currently processed element.
    i@elemnum   //The index number of the currently processed element.
    i@numpt     //The total number of points in the geometry.
    i@numvtx    //The number of vertices in the primitive of the currently processed element.
    i@numprim   //The total number of primitives in the geometry.
    i@numelem   //The total number of elements being processed.
    Available in Volume Wrangle
    v@P                     //The position of the current voxel.
    f@density               //The value of the density field at the current voxel location.
    v@center                //The center of the current volume.
    v@dPdx, v@dPdy, v@dPdz  //These vectors store the change in P that occurs in the x, y, and z voxel indices.
    i@ix, i@iy, i@iz        //Voxel indices. For dense volumes (non-VDB) these range from 0 to resolution-1.
    i@resx, i@resy, i@resz  //The resolution of the current volume.
     
    Common Geometry Attributes
    Houdini knows to cast these to the appropriate data type.

    Int
    @id         // A unique number that remains the same throughout a simulation.
    // Float
    @pscale     // Particle radius size.  Uniform scale.  Set display particles as 'Discs' to visualize.
    @width      // Thickness of curves.  Enable 'Shade Open Curves In Viewport' on the object node to visualize.
    @Alpha      // Alpha transparency override.  The viewport uses this to set the alpha of OpenGL geometry.
    @Pw         // Spline weight.
    Vector3
    @P          // Point position.  Used this to lay out points in 3D space.
    @Cd         // Diffuse color override.  The viewport uses this to color OpenGL geometry.
    @N          // Surface or curve normal.  Houdini will compute the normal if this attribute does not exist.
    @scale      // Vector scale.  Allows directional scaling or stretching (in one direction).
    @rest       // Used by procedural patterns and textures to stick on deforming and animated surfaces.
    @up         // Up vector.  The up direction for local space, typically (0, 1, 0).
    @uv         // UV texture coordinates for this point/vertex.
    @v          // Point velocity.  The direction and speed of movement in units per second.
    Vector4
    @orient     // The local orientation of the point (represented as a quaternion).
    @rot        // Additional rotation to be applied after orient, N, and up attributes.
    String
    @name       // A unique name identifying which primitives belong to which piece.  Also used to label volumes.
    @instance   // Path of an object node to be instanced at render time.
     
    Specifying VEX Data Types
    The following characters are used to cast to the corresponding data type.

    float       f@name    // Floating point scalar values.
    vector2     u@name    // Two floating point values. Could be used to store 2D positions.
    vector3     v@name    // Three floating point values. Usually positions, directions, normals, UVW or colors.
    vector4     p@name    // Four floating point values. Usually rotation quaternions, or color and alpha (RGBA).
    int         i@name    // Integer values (VEX uses 32 bit integers).
    matrix2     2@name    // Four floating point values representing a 2D rotation matrix.
    matrix3     3@name    // Nine floating point values representing a 3D rotation matrix or 2D transform matrix.
    matrix      4@name    // Sixteen floating point values representing a 3D transform matrix.
    string      s@name    // A string of characters.
     
    Channel Shortcut Syntax
    This is used to hint at the data type of auto generated wrangle parameters.

    ch('flt1');             // Float
    chf('flt2');            // Float
    chi('int');             // Integer
    chv('vecparm');         // Vector 3
    chp('quat');            // Vector 4 / Quaternion
    ch3('m3');              // 3x3 Matrix
    ch4('m4');              // 4x4 Matrix
    chs('str');             // String
    chramp('r', x);         // Spline Ramp
    vector(chramp('c', x)); // RGB Ramp 
     
    DOP Particle Attributes 
    Particle systems are driven by attributes, here are some of the attributes used.

    f@age       // Time in seconds since the particle was born.
    f@life      // Time in seconds the particle is allowed to live. When f@age>f@life, i@dead will be set to 1.
    f@nage      // Normalized age, f@age divided by f@life.  Implicit attribute, you cannot write to this.
    i@dead      // Whether a particle is living (0) or dead (1).  A dead particle is deleted in the Reaping stage.
    i@id        // A unique id for the particle that remains the same throughout a single simulation.
    i@stopped   // Whether a particle is moving (0) or stopped (1).
    i@stuck     // Whether a particle is free (0) or stuck (1).
    i@sliding   // Whether a particle is free (0) or sliding along a surface (1).
    f@cling     // Force applied to sliding particles inwards (according to the collision's surface normal).
    s@pospath   // The path to the object that the particle is colliding with.
    i@posprim   // Which collision primitive in the path geometry whose position we wish to refer to.
    v@posuv     // Parametric uv on the collision primitive.
    i@hittotal  // The cumulative total of all hits for the particle (only incremented once per timestep).
    i@has_pprevious // This is set to 1 if v@pprevious contains valid values.
    v@pprevious // Stores the position of the particle on the previous frame.  Used for collision detection.
    i@hitnum    // The number of times the particle collided in the last POP Collision Detect.
    s@hitpath   // The path to the object that was hit. A path to a file on disk or an op: path.
    i@hitprim   // The primitive hit. Could be -1 if it the collision detector couldn’t figure out which prim.
    v@hituv     // The parametric UV space on the primitive.
    v@hitpos    // Where the hit actually occurred.  Useful if the colliding object was moving.
    v@hitnml    // The normal of the surface at the time of the collision.
    v@hitv      // The velocity of the surface at the time of the collision.
    f@hittime   // When the collision occurred, that could be within a frame.
    f@hitimpulse// Records how much of an impulse was needed for the collision resolution.  varies with timestep.
    f@bounce    // When particles bounce off another object, this controls how much energy they keep.
    f@bounceforward // Controls how much energy they keep in the tangential direction.
    f@friction  // When particles bounce, they are slowed down proportional to how hard they hit.
    s@collisionignore   // Objects that match this pattern will not be collided.
    f@force     // Forces on the particle for this frame.
    f@mass      // Inertia of the particle.
    v@spinshape // This is multiplied by f@pscale to determine the shape of the particle for rotational inertia.
    f@drag      // How much the particle is effected by any wind effects.
    f@dragexp   // Ranges from 1 to 2, default is set on the solver.  Used for both angular and linear drag.
    v@dragshape // How much the particle is dragged in each of its local axes.
    v@dragcenter// If specified, drag forces will also generate torques on the particle.
    v@targetv   // The local wind speed. Thought of as the goal, or target, velocity for the particle.
    f@airresist // How important it is to match the wind speed.  Thickness of the air.
    f@speedmin  // Minimum speed, in units per second, that a particle can move.
    f@speedmax  // Maximum speed, in units per second, that a particle can move.
    p@orient    // Orientation of the particle.  Used for figuring out 'local' forces.
    v@w         // Angular speed of the particle.  A vector giving the rotation axis.
    v@torque    // The equivalent of force for spins. No inertial tensor (the equivalent of mass) is supported.
    v@targetw   // The goal spin direction and speed for this particle.
    f@spinresist// How important it is to match the targetw.
    f@spinmin   // Minimum speed in radians per second that a particle can spin.
    f@spinmax   // Maximum speed in radians per second that a particle can spin.
    </syntaxhighlight>
    DOP Grains Attributes
    Particles under control of POP Grains have the 'ispbd' attribute set to 1. This causes them to bypass movement update in the POP Solver, as the actual motion update is done by the POP Grains node.

    i@ispbd     // A value of 1 causes the particle to behave as grains.
    f@pscale    // Used to determine the radius of each particle.
    f@repulsionweight   // How much the particle collision forces are weighted.
    f@repulsionstiffness// How strongly particles are kept apart.  Higher values result in less bouncy repulsion.
    f@attractionweight  // How much the particles will naturally stick together when close.
    f@attractionstiffness   // How strongly nearby particles stick to each other.
    v@targetP   // Particles are constrained to this location.
    f@targetweight      // The weight of the v@targetP constraints.
    f@targetstiffness   // The stiffness with which particles are fixed to their v@targetP attribute.
    f@restlength// Particles connected by polylines will be forced to maintain this distance (prim attribute).
    f@constraintweight  // Scale, on a per-particle basis of the constraint force.
    f@constraintstiffness   // This controls the stiffness on a per-particle basis.
    f@strain    // This primitive attribute records how much the constraint is stretched.
    f@strength  // If f@strain exceeds this primitive attribute, the constraint will be removed.
     
    DOP Packed RBD Attributes
    The Bullet Solver uses several point attributes to store the properties of each piece of a packed object.
    i@active    // Specifies whether the object is able to react to other objects.
    i@animated  // Specifies whether the transform should be updated from its SOP geometry at each timestep.
    i@deforming // Specifies whether the collision shape should be rebuilt from its SOP geometry each timestep.
    f@bounce    // The elasticity of the object.
    i@bullet_add_impact // Impacts that occur during the sim will be recorded in the Impacts or Feedback data.
    i@bullet_ignore     // Specifies whether the object should be completely ignored by the Bullet solver.
    f@bullet_angular_sleep_threshold// The sleeping threshold for the object’s angular velocity.
    f@bullet_linear_sleep_threshold // The sleeping threshold for the object’s linear velocity.
    i@bullet_want_deactivate// Disables simulation of a non-moving object until the object moves again. 
    i@computecom// Specifies whether the center of mass should be computed from the collision shape.
    i@computemass   // Specifies whether the mass should be computed from the collision shape and density.
    f@creationtime  // Stores the simulation time at which the object was created.
    i@dead  // Specifies whether the object should be deleted during the next solve.
    f@density   // The mass of an object is its volume times its density.
    f@friction  // The coefficient of friction of the object.
    f@inertialtensorstiffness   // Rotational stiffness.  A scale factor applied to the inertial tensor. 
    i@inheritvelocity   // v and w point attributes from the SOP geometry will override the initial velocity.
    f@mass  // The mass of the object.
    s@name  // A unique name for the object. Used by Constraint Networks.
    p@orient// The orientation of the object.
    v@P     // The current position of the object’s center of mass.
    v@pivot // The pivot that the orientation applies to. If i@computecom is non-zero, this is auto-computed.
    v@v     // Linear velocity of the object.
    v@w     // Angular velocity of the object, in radians per second.
    i@bullet_adjust_geometry    // Shrinks the collision geometry.
    i@bullet_autofit    // Use the bounds of the object for Box, Capsule, Cylinder, Sphere, or Plane.
    f@bullet_collision_margin   // Padding distance between collision shapes.
    s@bullet_georep     // Can be convexhull, concave, box, capsule, cylinder, compound, sphere, or plane.
    i@bullet_groupconnected     // Create convex hull per set of connected primitives.
    f@bullet_length     // The length of the Capsule or Cylinder collision shape in the Y direction.
    v@bullet_primR  // Orientation of the Box, Capsule, Cylinder, or Plane collision shape.
    v@bullet_primS  // Size of the Box collision shape.
    v@bullet_primT  // Position of the Box, Sphere, Capsule, Cylinder, or Plane collision shape.
    f@bullet_radius // Radius of the Sphere, Capsule, or Cylinder collision shape.
    f@bullet_shrink_amount  // Specifies the amount of resizing done by Shrink Collision Geometry.
    s@activationignore  // Won't be activated by collisions with any objects that match this pattern.
    s@collisiongroup    // Specifies the name of a collision group that this object belongs to.
    s@collisionignore   // The object will not collide against any objects that match this pattern.
    f@min_activation_impulse// Minimum impulse that will cause the object to switch from inactive to active.
    f@speedmin  // Minimum speed, in units per second, that a particle can move.
    f@speedmax  // Maximum speed, in units per second, that a particle can move.
    f@spinmin   // Minimum speed in radians per second that a particle can spin.
    f@spinmax   // Maximum speed in radians per second that a particle can spin.
    f@accelmax  // Limits the change in the object’s speed that is caused by enforcing constraints.
    f@angaccelmax   // Limits the change in the object’s angular speed that is caused by enforcing constraints.
    f@airresist // Specifies how important it is to match the target velocity (v@targetv).
    f@drag      // How much the the v@targetv and f@airresist attributes effect the object.
    f@dragexp   // Ranges from 1 to 2, default is set on the solver.  Used for both angular and linear drag.
    v@force     // Specifies a force that will be applied to the center of mass of the object.
    f@spinresist// Specifies how important it is to match the target angular velocity (v@targetw).
    v@targetv   // Target velocity for the object. Used in combination with the f@airresist attribute.
    v@targetw   // Target angular velocity for the object. Used in combination with the f@spinresist attribute.
    v@torque    // Specifies a torque that will be applied to the object.
    i@bullet_autofit_valid  // Stores whether the solver has already computed collision shape attributes.
    i@bullet_sleeping       // Tracks whether the object has been put to sleep by the solver.
    f@deactivation_time     // Amount of time the speed has been below the Linear Threshold or Angular Threshold.
    i@found_overlap         // Used by the solver to determine whether it has performed the overlap test.
    i@id                    // A unique identifier for the object.
    i@nextid                // Stores the i@id the solver will assign to the next new object.
     
    DOP RBD Constraint Attributes
    Attributes on the geometry to customize each constraint behavior and type. If a primitive attribute with the same name as a constraint property (such as damping) is present, the attribute value will be multiplied with the value from the constraint sub-data.
    s@constraint_name    // Specifies a piece of relationship data by name, such as 'Glue' or 'Spring'.
    s@constraint_type    // Specifies whether the constraint affects 'position', 'rotation' or 'all' degrees of freedom.
    f@restlength         // Specifies the desired length of the constraint to enforce.
    f@width              // Width of each edge.
    f@density            // Density of each point.
    p@orient             // Initial orientation of each point. Value stored as a quaternion.
    v@v                  // Initial velocity of each point.
    v@w                  // Initial angular velocity of each point measured in radians per second.
    f@friction           // Friction of each point.
    f@klinear            // Defines how strongly the wire resists stretching.
    f@damplinear         // Defines how strongly the wire resists oscillation due to stretching forces.
    f@kangular           // Defines how strongly the wire resists bending.
    f@dampangular        // Defines how strongly the wire resists oscillation due to bending forces.
    f@targetstiffness    // Defines how strongly the wire resists deforming from the animated position.
    f@targetdamping      // Defines how strongly the wire resists oscillation due to stretch forces.
    f@normaldrag         // The component of drag in the directions normal to the wire.
    f@tangentdrag        // The component of drag in the direction tangent to the wire.
    i@nocollide          // Collision detection for the edge is disabled (Only used if Collision Handling is SDF).
    v@restP              // Rest position of each point.
    p@restorient         // Rest orientation of each point.
    i@gluetoanimation    // Causes a point’s position and orientation to be constrained to the input geometry.
    i@pintoanimation     // Causes a point’s position to be constrained to the input geometry.
    v@animationP         // Target position of each point.
    p@animationorient    // Target orientation of each point.
    v@animationv         // Target velocity of each point.
    v@animationw         // Target angular velocity of each point.
    i@independentcollisionallowed   // Toggle external collisions (Only non-SDF Geometric Collision).
    i@independentcollisionresolved  // Unresolved external collisions (Only non-SDF Geometric Collision).
    i@codependentcollisionallowed   // Toggle soft body collisions (Only non-SDF Geometric Collision).
    i@codependentcollisionresolved  // Unresolved toggle soft body collisions (Only non-SDF Geometric Collision).
    i@selfcollisionallowed          // Toggle self collisions (Only non-SDF Geometric Collision).
    i@selfcollisionresolved         // Unresolved toggle self collisions (Only non-SDF Geometric Collision).
     
    DOP FLIP Attributes
    The FLIP Solver contains an embedded POP Solver, so all of POP Attributes listed above apply.
    f@pscale        // Particle scale
    v@v             // Particle velocity
    f@viscosity     // The "thickness" of a fluid.
    f@density       // The mass per unit volume.
    f@temperature   // The temperature of the fluid.
    f@vorticity     // Measures the amount of circulation in the fluid.
    f@divergence    // Positive values cause particles to spread out, negative cause them to clump together.
    v@rest          // Used to track the position of the fluid over time.
    v@rest2         // Used for blending dual rest attributes, avoids stretching. 
    f@droplet       // Identifies particles that separate from the main body of fluid.
    f@underresolved // Particles that haven't fully resolved on the grid.
    i@ballistic     // Specifies particles which will be ignored by the fluid solve.
    v@Lx            // Angular momentum X axis
    v@Ly            // Angular momentum Y axis
    v@Lz            // Angular momentum Z axis
     
    DOP Vellum Point Attributes
    Vellum geometry is also considered particles, so all of POP Attributes listed above apply.
    i@isgrain           // A value of 1 causes the particle to behave as grains, 0 behaves as cloth.
    f@attractionweight  // How much the particles will naturally stick together when close, zero disables clumping.
    f@friction          // How much to scale the static friction.
    f@dynamicfriction   // How much to scale the dynamic friction.
    f@inertia           // Resistance of a particle to rotational constraints. If zero, the particle won't rotate.
    v@v                 // Point velocity.
    p@w                 // (Hair or Wire) angular velocity.
    p@orient            // (Hair or Wire) orientations.
    i@stopped           // Used to pin points (0=free, 1=no motion, 2=no rotation, 3=no rotate or move).
    i@pintoanimation    // If 1, the pinned points' position will be updated to match the target point.
    i@gluetoanimation   // If 1, both the position and orientation will be updated
    s@target_path       // target path for any pins (when the Target parameter is set in Vellum Source)
    i@target_pt         // target point number for any pins (when the Target parameter is set in Vellum Source)
    f@targetweight      // Affect the strength of the pinned points using a 0..1 weighting value.
    i@weld              // Weld this point to a point number.  If there is an @id attribute, then to a point id.
    i@branchweld        // built by hair constraints when it is forced to split points for hair simulation.
    i@collisionweld     // generated on demand to provide a single weld to the detangle algorithm.
    f@breakthreshold    // The threshold for breaking welds and branch welds
    s@breaktype         // 'stretchstress', 'bendstress', 'stretchdistance', 'stretchratio', or 'bendangle'.
    // Collisions
    f@pscale            // Used to determine the thickness of cloth or radius of each particle.
    f@overlap_self      // Stores how much of the original pscale is overlapped.
    f@overlap_external  // Stores how much of the original pscale is overlapped.
    i@layer             // Indicates belonging to different layers of cloth. Higher numbers refer to higher layers.
    i@disableself       // A value of 0 means this point will use self collisions.
    i@disableexternal   // A value of 0 means this point will use external collisions.
    s@collisionignore   // Stores a pattern for the objects and collision groups to not collide with.
    s@collisiongroup    // Gives the collision group that this point belongs to.
    // Internal worker variables (Kept to avoid removing/adding attributes every frame)
    v@pprevious         // For 1st order integration, the previous frames position (beginning of timestep).
    v@plast             // For 2nd order integration, the position from two frames earlier.
    v@vprevious         // For 1st order integration, the previous frames velocity (beginning of timestep).
    v@vlast             // For 2nd order integration, the velocity from two frames earlier.
    p@orientprevious    // For 1st order integration, the previous frames orientation (beginning of timestep).
    p@orientlast        // For 2nd order integration, the orientation from two frames earlier.
    p@wprevious         // For 1st order integration, the previous frames angular velocity (beginning of timestep).
    p@wlast             // For 2nd order integration, the angular velocity from two frames earlier.
    f@dP                // Constraint displacements.  Likely of last iteration.
    f@dPw               // Constraint weights.  Likely of last iteration.
    s@patchname         // Identifies each generated patch in a simulation so it can be updated/replaced.
    // When a point is part of a Pressure constraint, these attrs hold values computed during constraint update.
    v@pressuregradient  // a vector pointing outwards along the direction of greatest volume gain.
    i[]@volumepts       // contains array of the points needed to compute the volume attribute.
    i@volume            // compare against the Pressure constraint’s restlength value.
     
    DOP Vellum Constraint Attributes
    There are many types of constraints, so the meaning of these variables is often dependent on the constraint type. They usually live on the primitive.
    s@type // Type of the constraint.
    s@type = 'distance' // Each edge in the display geometry is turned into a distance constraint maintaining that edge length.
    s@type = 'stitch' // Stitch points within the same geometry together using distance constraints. The points do not need to actually be connected by geometry. This is useful for keeping jackets closed or preventing pockets from flapping
    s@type = 'branchstitch' // 
    s@type = 'ptprim' // 
    s@type = 'bend' // Each pair of triangles (or implied triangles if input is quads or higher) creates a constraint maintaining the initial dihedral angle between the triangles.
    s@type = 'trianglebend' // Each pair of triangles (or implied triangles if input is quads or higher) creates a constraint maintaining the initial dihedral angle between the triangles.
        angle
        tetvolume
        pressure // Each piece, as determined by the Define Pieces parameter, stores its original volume and a many-point constraint is built to maintain it. The enforcement is global, so squishing one place will expand another, like a balloon.
        attach, pin
        attachnormal
        pinorient
        bendtwist
        stretchshear
        tetfiber
        triarap
        tetarap*
    f@stiffness // The stiffness of the constraint, which controls how strongly the constraint pulls.
    f@restlength
    f@restlengthorig
    f@dampingratio // Damping reduces jitter by bleeding energy when evaluating the constraint. Too much damping can prevent the constraint from being satisfied. Values less than 1 must be used.
    f@stress // Estimate of work done by the constraint (updated by Vellum solver).
    s@constraint_tag // The name of the node which created the constraint
     
    KineFX Attributes 
    A KineFX hierarchy or skeleton is represented by a collection of points connected by polygon lines. The parent-child relationship between joints in a hierarchy is determined by vertex order.
    s@name             // joint name attribute
    3@transform        // World space 3×3 transform of the point (rotation, scale, and shear).
    4@localtransform   // The transform of the point relative to its parent.
    i@scaleinheritance // Determines how a point inherits the local scale from its parent.
    </syntaxhighlight>
    Viewport Display Attributes
    Override the viewport display mode <ref>''[https://www.sidefx.com/docs/houdini/model/attributes.html#attributes sidefx.com/docs/houdini/model/attributes.html]''</ref>

    i@gl_wireframe     // Detail attribute, force wireframe (1) or shaded (-1)
    i@gl_lit           // Detail attribute, draw with lighting (1) or no lighting (0)
    i@gl_showallpoints // Detail attribute, draw points even if connected to geometry
    f@vm_cuspangle     // Detail attribute, angle in degrees for generating cusped normals
    i@gl_spherepoints  // Detail attribute, (1) causes unconnected points to be drawn as spheres
    i@gl_xray          // Detail attribute, (1) geometry will visible even when it is hidden behind other geometry
    v@Cd               // Color Diffuse
    f@Alpha            // Surface opacity
    v@N                // Surface Normal for lighting
    f@width            // Curve width
    f@pscale           // If no pscale exists the viewport defaults to 1.0, while Mantra defaults to 0.1
    s@spritepath
    s@shop_materialpath
    i@group__3d_hidden_primitives  // Add primitives to this group to hide them from the 3D viewport
    f@intrinsic:volumevisualdensity // Primitive intrinsic attribute controlling the opacity of volumes.
    f@volvis_shadowscale // Detail attribute controlling the shadow strength for volumes.
     
    Copying and Instancing Attributes
    When copying or instancing, Houdini looks for these point attributes to transform each copy/instance. 
    https://www.sidefx.com/docs/houdini/copy/instanceattrs sidefx.com/docs/houdini/copy/instanceattrs.html

    p@orient                    // Orientation of the copy.
    f@pscale                    // Uniform scale.
    v@scale                     // Non-uniform scale.
    v@N                         // Normal (+Z axis of the copy, if no p@orient).
    v@up                        // Up vector of the copy (+Y axis of the copy, if no p@orient).
    v@v                         // Velocity of the copy (motion blur), used as +Z axis if no p@orient or v@N.
    p@rot                       // Additional rotation (applied after the orientation attributes above).
    v@P                         // Translation of the copy.
    v@trans                     // Translation of the copy, in addition to v@P.
    v@pivot                     // Local pivot point for the copy.
    3@transform or 4@transform  // Transform matrix overriding everything except v@P, v@pivot, and v@trans.
    s@shop_materialpath         // The instanced object uses this material.
    s@material_override         // A serialized Python dictionary mapping material parameter names to values.
    s@instance
    s@instancefile              // File path indicating what geometry to instance.
    s@instancepath              // Geometry to instance. This is either a path to a file on disk or an op: path.
    </syntaxhighlight>
    Accessing Other Inputs 
    This syntax is used to refer to nodes wired into the inputs of the wrangle, or other nodes in the network. 
     'opinput:X' is the most legible and always works (the first input is input 0).
    point('opinput:0', 'P', i@ptnum)
    point('opinput:1', 'P', i@ptnum)
    point('opinput:2', 'P', i@ptnum)
    point('opinput:3', 'P', i@ptnum)
    The integer input number (the first input is 0).  Some functions don't support this but it's easy to type.
    point(0, 'P', i@ptnum)
    point(1, 'P', i@ptnum)
    point(2, 'P', i@ptnum)
    point(3, 'P', i@ptnum)
    @OpInputX works as well, but be careful as it isn't 0 based, instead it starts at 1 which is confusing
    point(@OpInput1, 'P', i@ptnum)
    point(@OpInput2, 'P', i@ptnum)
    point(@OpInput3, 'P', i@ptnum)
    point(@OpInput4, 'P', i@ptnum)
    v@opinputX_* reads an attribute from the same element on the numbered input (first input is input 0).
    v@opinput0_P
    v@opinput1_P
    v@opinput2_P
    v@opinput3_P
    Absolute and relative paths to other nodes look like this.
    point('op:/obj/geo1/OUT', 'P', i@ptnum)
    point('op:../../OUT', 'P', i@ptnum)
     
    For Loop Metadata
    Detail attributes, You can get this information with a [https://www.sidefx.com/docs/houdini/model/looping#metadata “Fetch metadata” Block Begin node].
    i@numiterations      // The expected total number of iterations
    i@iteration          // The current iteration number, always starting at 0 and increasing by 1 each loop.
    f@value              // In piece-wise loops, this is the current value of the attribute
    i@ivalue             // In simple repetition, this is an integer version of value.
     

    Mantra Shader
    Mantra shader global variables.  See a [https://www.sidefx.com/docs/houdini/model/primitive_spaces.html detailed explanation of implicit parametric UVs]
    v@Cf      // Surface Color.
    v@Of      // Surface Opacity.
    f@Af      // Surface Alpha.
    v@P       // Surface Position (camera space).
    f@Pz      // Surface Depth.
    v@I       // Direction from Eye (camera) to Surface.
    v@dPds    // Directions or Derivatives of surface implicit s coordinate.
    v@dPdt    // Directions or Derivatives of surface implicit t coordinate.
    v@N       // Surface Normal.
    v@Ng      // Surface Geometric Normal.
    v@Eye     // Position of Eye (camera).
    f@s       // implicit parametric s coordinate (u).
    f@t       // implicit parametric t coordinate (v).
    f@Time    // Shading Time.
    f@dPdz    // Change in Position with depth.
    i@SID     // Sample Identifier. A sample id to be used with the nextsample() VEX function to generate consistent random samples that don’t change when re-rendering or between frames.

     
  23. Haha
    popol reacted to Nicolas Caplat in VEX Wrangle Cheat Sheet   
  24. Like
    popol got a reaction from Nicolas Caplat in AWS Thinkbox products now available free of charge   
    ouai pareil, mais je vais tester ca des que j'ai un moment . les produits développé par thinkbox son quand même excellent, ce serait dommage de pas en profiter.
  25. Like
    popol got a reaction from Nicolas Caplat in AWS Thinkbox products now available free of charge   
    Today we are excited to announce that AWS Thinkbox products (Deadline, Draft, Krakatoa, Frost, XMesh, Sequoia, and Stoke) are now available at no cost. Thinkbox tools simplify rendering, VFX, and simulation workflows, and are in use by top studios around the world.
    https://aws.amazon.com/ru/blogs/media/aws-thinkbox-products-now-available-free-of-charge/
×
×
  • Créer...