Jump to content

haggi

Members
  • Content count

    237
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won

    2

haggi last won the day on November 17 2016

haggi had the most liked content!

Community Reputation

28 Excellent

About haggi

  • Rank
    Initiate

Contact Methods

  • Website URL
    http://www.renderwiki.com

Personal Information

  • Name
    haggi

Recent Profile Visitors

4,336 profile views
  1. Hi, maybe anyone knows an easy solution for this. I usually use the sleep mode for my machine if I do not use it for some time. Unfortunately it goes to sleep mode even if a hbatch process is running on all cores. I now turned the sleep mode off, but does anyone know a simple solution for this problem? For Windows7 I once used a standalone tool where you can select a process and it keeps Windows awake as long as this process is running. Is this still necessary? Or are there any Windows10 built in options? I even do not understand why it goes to sleep at all if it is working.
  2. Alembic export 3 floats vs vector

    Okay, I found it in the Houdini plugin in the alembic repository.
  3. Hi, I export particles from my particle sim from Houdini as an Alembic file. Some attributes have three floats instead of vector or color, e.g. pprevious, targetv, all the attributes which are 3flt and have no further description. If I now try to read these attributes in my Maya plugin, I can see that they are defined as float arrays instead of vector arrays. Usually in alembic a vector or color is exported as a float array (one for each point) attribute with extent 3, in the mentioned cases the attribute is exported as float array with extent 1: vector attribute like position or color: float extent 3 attribute len = 1 3 floats attribute like pprevious, targetv: float extent 1 attribute len = 3 This makes it complicated to read these attributes correctly. Of course I could convert all of these attributes to vector before export, but this seems not to be the correct way, I'd prefer to find a way to read these attributes correctly. Does anyone has an idea how I could find out the correct type from alembic API?
  4. From the Alembic 1.7.1 source code: I'm not sure if Autodesk itself uses the same original sources, but it seems so. So I fear there you will have no luck reading an animated sequence. We solved the problem (with Maya 2015) by building our own abc reader plugin which can be connected to a particle instancer what work quite well.
  5. Export Points to maya 2017

    Or you could ask the creator of http://redpawfx.github.io/partio if he is able to provide a version for Maya2017. He has a particle emitter in his toolset.
  6. Control Where Points Scatter

    Placing only one point in an volume does not guarantee that only one chunk is created. I'd use a boolean instead. First you bool the desiered chunk and then you fracture the rest.
  7. Per point distance VEX

    If you only want to know the distance of the same point id in input 1 you can keep the point wrangle type and the advantages of parallel execution: f@dist = length(@P - point(1, "P", @ptnum)); Of course this only works if the input 1 has the same number of points as the first input.
  8. Render to pointcloud?

    Ahhh... great. Thanks a lot.
  9. Hi, I'm searching for a way to create a pointcloud from rendered geometry. More or less it was possible with prman where I was able to save point positions with rendered color information during rendering (or in a pre render pass). Same procedure worked in more ore less in mentalray. Can I do it in mantra as well? The result should be a camera independent point clouds with rgb and position data.
  10. Happy 10th Birthday Od[force]

    Happy birthday. It is incredible how helpful the community here is. Thank you.
  11. You create a surface vdb which creates necessary data on the surface only by definition. But to simplify the process you could use a fluidSource sop which seems to fill the interior.
  12. Hi, during the work with my maya alembic reader, I discovered a problem with alembic files written by houdini. Obviously Houdini exports an additional point geometry together with my mesh. If I load the alembic in Maya, I get a mesh shape and a particle shape. In houdini I can see two packed objects in the alembic sop. This only happens in certain situations. e.g. if I create a box and deform it, only one packed object is created in the alebic export. Only if I export my flip mesh an additional packed point geometry is exported and I get a warning in the exporter: "Renaming node to /geo1/file3_1 to resolve collision". Does anyone know what's going on here? It seems not to be a new phenomenon, it happens the same way with H16.
  13. But it is helpful to keep in mind that 10 nodes in a vop can sometimes be replaced by one line of code. I just followed a Jeff Wagner flip fluid webinar where he combines some vop operators in a dop node and even if it is not very complicated, the network grows fast and most of the time you are moving the viewport to check where all the connections go. So with two lines of code I was able to do the same thing what results in a very much better overview and less nodes.
  14. Particles from Houdini to Maya

    Okay, did you really try it? In the source code you can see: data["bhclassic"]=readBGEO; What means, bhclassic should be handled as bgeo. But maybe the code on github is newer than the plugins.
  15. Particles from Houdini to Maya

    There is no need to rename it as begeo, partio should be able to read bhclassic directly.
×