Jump to content

ninjismo

Members
  • Content count

    3
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ninjismo

  • Rank
    Peon

Personal Information

  • Name
    Arun S
  1. Hey, I'm having some trouble generating .ass files for volumes in Houdini so they can be lit by lighters in Maya using Arnold. I'm using Houdini FX 14.0.201.13 with HtoA 1.3.1 (which the website says is the correct version of HtoA for my version of Houdini). The steps that I used to get Arnold to work with Houdini is that I manually installed the plugin and had my houdini.env point to the plugin location, and the console seems to have all the arnold plugins loaded at startup. I created a shelf tool pyroFX explosion, converted it to VDB using "density" and "heat" as the groups. I then called those fields back using an Arnold Volume node at scene level, with the grids as density and heat. It displays the volume in the viewport, and renders out the scene if I put down some arnold lights and render it with an Arnold ROP in Houdini itself. In the Archive tab of the Arnold ROP, I set the location to where I want to have the .ass files dumped and uncheck "export lights" and "export cameras". When I hit the render button I get this message in the console - 00:00:00 1127MB WARNING | [htoa.session] generating shaders... 00:00:00 1127MB WARNING | [htoa.session] shader generation done. HtoA ends up generating a .ass file that is only 2KB in size, always. When I take a simple sphere and apply a shader to it and dump out the .ass file, it works, but not with volumes. Anyone knows why this isn't working for me?
  2. Well the answer is probably never in a production environment for the final sim. To get a fair understanding of how the sim will look before I start churning out high-res versions of it, I always use the graphics card OpenCL version first even with its limitations of RAM because of the number of iterations I can see in a given amount of time, considering how small my production deadlines are. I have done this on 3 productions so far. It is very helpful for me in personal projects as well. And now with graphics cards coming out with 8GB and 16GB of RAM, it will be interesting to see how they perform on the OpenCL test. The main thing here is to check the speed, hence the name of this thread.
  3. Hello! I haven't seen a resource that benchmarks the calculation speed of graphics cards in Houdini so I thought I'd post this. I hope that people can participate and post their scores using their gaming/workstation graphics cards so other people can get a rough idea of the performance of each graphics card in Houdini before they decide to buy/upgrade anything. This should only take a few minutes - 1. Start Houdini 2. Use the following units under your Hip File Options - Unit Length - 1 Unit Mass - 1 3. Frame Range 1-240 @ 24fps 4. Add a sphere at origin 5. Goto the Pyro FX shelf tool and select Explosion. Select the sphere. 6. Disable Cache Simulation in your DOP and use the following settings - Pyro Container Settings Division size - 0.075 Size - 7.5, 10, 7.5 Center - 0, 4, 0 Resize Container Settings Padding 0.3 Subtract Threshold 0.2 9. Select the Pyrosolver. In the Advanced tab, turn on OpenCL 10. Save the file and restart your computer 11. Use a stopwatch or http://www.online-stopwatch.com/ to keep track of the time 12. Open the file, start the sim and the stopwatch timer 13. Record the time after 240 frames. 14. Run the same sim again but with OpenCL disabled 15. Post the exact times with your PC Specs, Houdini version and OS in the following format (using my results as an example) - Houdini Version - 14.0.201.13 OS - Windows 7 Ultimate x64 GFX - Zotac 770GTX Amp! Edition (2GB) / Driver - 347.09 Time - 1:37.222 CPU - Intel i7 3770K @ stock Time - 2:09.503 Other - ASRock z77 Pro3 Motherboard, 32 GB Corsair Vengeance RAM Thank you! PS - I've attached a hip file with the above settings using Houdini 14 that you can run right away. Thanks for the suggestion, Skybar. OpenCL_TestFile.hipnc
×