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.]]

eloop last won the day on October 29 2012

eloop had the most liked content!

Community Reputation

8 Neutral

About eloop

  • Rank
  • Birthday 06/17/1964

Personal Information

  • Name
    Drew Whitehouse
  • Location
  • Interests
    Crossfit, surfing, kite surfing and all things CG.

Recent Profile Visitors

8,483 profile views
  1. Houdini 19 Wishlist

    Your intuition about the good reasons is correct. From what I understand VEX implements what's called a "single instruction multiple data" (SIMD) processing model, meaning it's possible to parallelise for fast implementation on processors that support it, think Intel MMX, SSE, etc and GPUs. Introducing modifiable globals would limit vex code to execute serially and in strict order.
  2. Render Farms

    A new entry to the above list. An open source renderfarm manager donated by Sony to the Academy Software Foundation. https://github.com/AcademySoftwareFoundation/OpenCue No Houdini support at the moment.
  3. Houdini 17 Sneak Peak

    Transcribed from the end of H17 launch video ... "LOPS (Project Solaris) Major new architecture, busy developing in R&D. Architecture that goes straight to the heart of lighting and rendering. And in one big swoop, takes Houdini's proceduralism, combines it with GPU accelerated workflows across the board. Dedicated artist workflows, and it weaves all that into a live and native USD core. But that is a story for another day." Can't wait! :-)
  4. Render Farms

    Many thanks for that great summary Szymon, it was just what I was looking for. We actually are a supercomputer facility, so have lots of task scheduler experience, PBS Pro in our case. But for my groups work (sci-viz) we're currently using hqueue on a chunk of cloud machinery. Being a educational and research institution we have the luxury of great hardware resources, but poor software budgets. Hqueue has been ok for small renders, but has truly woeful performance once you attempt jobs that have a large number of frames, eg I've just rendered a sequence with ~45,000. To view the job I'm seeing 80Mb xmlrcp downloads into the browser, each taking about 30s, with the hqueue process flat pegged at 100% for a lot of the time. Plus the browser re-loads that 80Mb every few seconds, proper server side pagination would go a long way to making it more efficient. I'm also currently trying to delete that finished job which has pegged the hqueue server for the last half an hour. I'm guessing it's a wildly inefficient implementation, where you could reasonably expect a good SQL statement should be able to do that in the blink of an eye. Question for hqueue users, has anyone gone over from sqlite to mySQL and seen a big difference in performance? I'm thinking it woudn't make that much difference, since the main bottleneck seems to be in the hqueue web server API implementation. Now the question is do I start implementing my own half baked pipeline using something like SLURM. Wish HQueue could get some SideFX luvvin!
  5. HOT for Houdini 13

    Thanks Javier, much appreciated :-)
  6. HOT for Houdini 13

    I have no plan to support H13 now that Houdini has equivalent/better ocean surface tools included. It may simply be a case of recompiling. -Drew
  7. HOT OceanTool to H12.5 OceanTool

    Most likely not, the new ocean tool is a completely new implementation. -Drew
  8. HOT for h12.5

    Hi guys, I have no plans to maintain the HOT from this time on. SideFX have done a great job of making the HOT redundant. Now I don't have to recompile/port every time I want to make an ocean surface. This makes me happy :-) -Drew
  9. Hi people, I just fixed a problem with vop_displace.hip in the examples directory that was suffering from houdini version bitrot. For some reason the wave height paramater had been reset to zero. I also added an new example 'equivalent_geos.hip' that shows how you go about getting matching oceans via SOP, VOPSOP and VEX shader, something that I've been asked on more than one occasion. https://github.com/eloop/hot -Drew
  10. Ocean Eval Displacement in SHOPs

    Hi Julian, Look at the new example "equivalent_geos.hip" that I just uploaded to the github repository. https://github.com/eloop/hot -Drew
  11. PS - not sure how you implement a VEX COP Generator where you can set the size of the image directly. Is it possible ?
  12. You'll need to compile the latest version from gitub, turned out there was a small bug in VEX_Ocean.C's implementation of ocean_eval_ij. Then have a look at the vex code implemented in the COP operator in the .otl file included here. It's just the skeleton of an implementation of an asset to generate the various ocean exports as images. hotimages.zip
  13. HOT Ocean Eval vop

    Make sure you have the VEXdso file installed properly.
  14. Hello Imre, Chris's version should be faster, as he's added multi-threading. I peeked at his update to get my SOP_Ocean working again for H12's new geometry library (thanks Chris), but didn't bring in the multithreading. The lastest version of the HOT is now hosted on github and only has support for building on osx/linux with a simple script "compile.sh". You'll need to do the equivalent things to build on windows, although the third party tools are included pre-compiled. I don't have much time to spend on the HOT anymore, so I don't plan to bring Chris's multithreading into the distribution any time soon. If I did I'd be trying to do it in a way that didn't make Ocean.h application specific, and that could take quite a bit of fiddling. I think one of the reasons the HOT has been so widely ported to other platforms is that I kept the math part of the code as clean as possible and completely independent from the application integration. That's also why you can't get the VEX code to multithread. Keep in mind that one way to work with the code is to output the displacement and other quantities as image maps using the VEX function in a COP network. Then you just use the images in shaders and can take advantage of filtering for anti-aliasing, pass the maps between Maya and Houdini as OpenEXRs as well as save memory for the large layered displacements you typically use to hide tiling. https://github.com/eloop/hot BTW Nicholas Yue has commit access to the github repo and is probably available for consultation if you needed more support. Good luck, Drew
  15. HOT on github / H12

    I don't see this (on OSX), do you see the same thing with the vopsop_foamparts.hip example ? -Drew