Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won


LaidlawFX last won the day on April 16

LaidlawFX had the most liked content!

Community Reputation

155 Excellent

1 Follower

About LaidlawFX

  • Rank
    Houdini Master
  • Birthday 02/23/1985

Contact Methods

  • Website URL

Personal Information

  • Name
  • Location
    Toronto, ON
  • Interests
    Getting away from the computer
  1. Render Farms

    Get in touch with your SideFX representative/support they can help you
  2. Random Voronoi Fracturing

    You will have to contact Orbolt support if you are having issues. The assets are free on Orbolt, but they are black boxed as their primary draw back. The methods everyone has mentioned in this thread are all used in the setup, so this is more just a visual example case. All the ways to modified voronoi as in this examples to build an HDA like this are on the forum. It is only on Orbolt if you do not want to pay the, Iron Price, if you understand the game of thrones parlance.
  3. Random Voronoi Fracturing

    This would be an example use of what everyone has been saying. There are many files on the forum for all these patterns if you look around. https://www.orbolt.com/asset/LaidlawFX::voronoifracture::1.0
  4. Hello Tanya, Welcome to the forum. Sounds like you dove in pretty deep. While making your lightning system is great for a lot of productions and learning. Have you tried to use the Lightning preset on the L-system sop? A bit old school but it should have most of the functionality you seek, with plenty of seeds. If you place down a geometry node at object level, and then drop a Lsystem sop, you can then hit the gear icon an pick from the presets lightning or any other of the branching patterns. Then you can play with the Generations tab to control the growth. The Lightning preset has Random Seed set to $F which means you can scrub the timeline to quickly test different cases. Otherwise you can break that channel and use the ladder bracket to quickly change up seeds so you can animate the generation over time. I'll let others go into some of the other methods you can use like in vexpressions, too. There a few other post out there too you can look into on the forum, especially in regards to different growth systems. Have fun and enjoy the journey.
  5. Houdini 17 Wishlist

    You can post these on the tools thread.
  6. can we get normalized curvature of a volume?

    Feel free to send in an RFE to SideFX. Your request will get lost in the forums here. https://www.sidefx.com/bugs/submit/ I think you may be looking to work with SDF Volumes? Otherwise perhaps just asking for a stock HDA that fits/normalizes for you. http://www.sidefx.com/docs/houdini/nodes/dop/volume.html -Ben
  7. GDC Vault paid membership?

    There are a lot of good talks in the vault. The most notable talks are generally made public. As for the price point I can not say if it is worth for an individual. For a company I would say yes, especially if it is a shared account. If you are into more game engine side it would certainly be worth it, as you not only get this years content but all previous years content. There is still a lot of work people have done in the past that other companies have still not caught up with yet. Also make sure it's applicable to what you are looking for, a lot of the speaker are technical and not great speakers so it's not like TED videos where the speaker comes first and then the content, so some can be quite boring. Plus there are hundreds of videos a years with the majority that might not be worth it, but there may be a dozen each year that really set the industry forward that are worth it the price alone. Kind of a round about answer. But yes if you have some one else pay for it.
  8. Houdini 17 Wishlist

    The previous preset of .idx used to be ascii before they made if binary to optimize performance, however, this reduce the amount of control you can have with the system. Source and revision control are impossible in a binary format. You can longer edit by hand in each preset which is really needed for production control. Additionally you want to be able to have per project control of presets, which I can not at the moment recall if the previous ascii .idx could handle i.e. for each HOUDINI_PATH variable you have be able to add each new preset to the list for studio and project control. The previous system of having all the presets in one file, I'm not personally a fan of as I would like each preset to be it's on file. The old presets have their own custom format, which was not intuitive, so documentation and a standard jason or xml format would be helpful. For those not used to hand editing presets, which I'm guessing is nearly everyone in the last five years or more, perhaps a UI from within Houdini. This UI could also help all the new people. Also allowing for some more complex preset controls, like node name, color and shape that are now maintained by different systems. This may include also other on name change, ondeleted, on input change actions. Which it would be nice to perhaps have a way to subscribe a bit to the presets, and maintain more of an active link, so that you know that this node is actively prescribed to that preset so when the studio updates the node preferences they can update. While perhaps dangerous in some ways, in the course of a large production, in order to say change a whole sequence of .hip files or Houdini Engine .hda options for a level team. A studio could change the options on demand instead of tryign to change the defaults on the node which may not be at issue for the other half the studio. For instance, all volumetric redering mantra nodes need to have a better tweak, or you need to autocorrect all the settings because some juniors keep messing with the settings and you want to lock down or hide the parameters. Something I am not a total fan of but perhaps needed in the world of Orbolt where people are selling assets, is to be able to add these presets to the .hda. In production this would generally be more a piece of shit decision, but in the world of smaller teams this may be helpful to store all related items of an asset together, especially now that we can store asset in their uncompressed version. The current work around for this system is to make your own python preset system. Which is a bit on the companies burdensome side. This also means you now have multiple preset systems to maintain. The old Gear Menu setup, the newer wrangle drop down menu setups, and then your own studio one. Additionally this brings to light that unlike the L-System preset, now with wrangles people expect presets to live in multiple places. A lot of newer people not even being aware there is a preset menu in the gear menu. One of these should be eliminated in preference of the other. So that means to take all of one system and put it into the other including making it more production friendly. Which in reality means going to all the wrangle nodes and putting those options in the gear menu, to make one homogeneous system. Additionally fixing all the under the hood reason why those options were not included in the gear menu solution. While in theory it is OK to have two different preset options in two different places, when accounting for studio options it really makes three. At the end of the day this really just highlights the issue at hand that the original system needs to be upgraded.
  9. Houdini 17 Wishlist

    Update node preset system for this decade... well maybe for next decade, too, as this one is almost over.
  10. Houdini asset not updating

    If you need just drop your assets into your $HOME/houdini##.#/otls directory inorder to test a directory that is by default searched via Houdini. As for the Embedded asset, this happens when Houdini is restarted and it can no longer find the path on disk to the original HDA, this will by default leave a shell HDA in your session. If you do not have the HDA already saved in your scene then you will not be able to find it either. This is because the $HOUDINI_PATH, $HOUDINI_OTLSCAN_PATH, or your $HOME path i.e. & does not have your .hda/.otl in those directories. So in H16.0 and earlier you can re-source these in the Operator Type Manager Window, in H16.5+ it is now called the Asset Manager i.e. Windows > Asset Manager, in the Operators Tab there is the listing for Operator Type Libraries > Current HIP File, and if you open that and see EMBEDDED that HDA has lost it's connection to on disk. You can manually add the HDA back in that session, or close the program and fix the environment variables that define those paths on load. Once loaded with the correct path and if they still don't work you can go to Configuration tab in the Asset Manager, change the Asset Bar: to Display Menu of all Defintions, and then above your parameter pane, you get a drop down bar you can relink your asset from Embedded to the correct HDA. I leave this bar on in production so you can easily switch version of HDAs. Hope that helps.
  11. Quad Sphere ?

    Nurbs sphere...?
  12. Terrain .hda Unreal to Houdini

    Cool glad to hear it works now.
  13. First Post!! \o/

    So true.
  14. Terrain .hda Unreal to Houdini

    That is so weird... If the pipe were working correctly the hda node should just get created in the Houdini session, which to your point it clearly does not. The only thing I think I could suggest is to open Unreal first, i.e. have Houdini closed. Switch the Session Type to Named process, so the value is hapi, as opposed to TCP as that specific port may be used by something else in your system, you could test this by trying another port number too if you wanted. Toggle the start of the automatic server... And then open Houdini, turn on the Houdini Debugger go to Named Pipes and then press start. Muscle memory as best as I can repeat it. I think you may be starting the debugger prior to when unreal would be available to be listened too. Another thing to check is, is your HDA available in your houdini session already? Like can you see it available in the tab menu in the objects or the sops context? I don't think this would be the case, but it could just not have it in it's otl search paths i.e. in your $HOME, $HOUDINI_PATH $HOUDINI_OTL_SCAN_PATH ?sp? Otherwise I would ping support at sidefx.com and give them your system info and all the above with your issue. It's possibly a bug, or in all case I'm missing something. It's one of those things at this point for me I would need to sit down at the desk and let my muscle memory do the work. I type more keys than I think about most times.
  15. Terrain .hda Unreal to Houdini

    I believe the Houdini Engine Debugger is what your after. Once the Houdini Engine Debugger has been started on the correct port, any changes you do in Unreal should real-time reflect in Houdini. For an example say you have a simple .hda that is a grid with a mountain sop to maker a rudimentary terrain. As you adjust the .hda in Unreal changing say the amplitude of the noise, it would reflect those changes like a ghost was editing it in Houdini. Encase the issues is otherwise, there is also the bake option on the HDA in Unreal. Maybe you are just looking for that? Where once you change the settings on the HDA is makes the copy of the content preserved in unreal. Unfortunately by default the Houdini Engine will not save preferences for session to session. The only work around would be to make your own preset system in python for the .hda to save your parameter settings you have changed and then load them again in your next session.