Jump to content

Search the Community

Showing results for tags 'assets'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Lounge/General chat
    • Education
    • Jobs
  • Houdini
    • General Houdini Questions
    • Effects
    • Modeling
    • Animation & Rigging
    • Lighting & Rendering
    • Compositing
    • Games
    • Tools (HDA's etc.)
  • Coders Corner
    • HDK : Houdini Development Kit
    • Scripting
    • Shaders
  • Art and Challenges
    • Finished Work
    • Work in Progress
    • VFX Challenge
    • Effects Challenge Archive
  • Systems and Other Applications
    • Other 3d Packages
    • Operating Systems
    • Hardware
    • Pipeline
  • od|force
    • Feedback, Suggestions, Bugs

Found 6 results

  1. Hey everyone! I recently finished up a tutorial on creating game ready procedural rocks assets for UE4 Hopefully you can learn a thing or two on my process and feel free to let me know if you have any suggestions, critique, or questions about anything you see! Video preview Free Demo version: https://gum.co/rocksue4demo Full version: https://gum.co/rocksue4 Includes: 8 Video Chapters Project file (.hip) Hi/lowres meshes+maps Tools: Houdini 16.5+, Unreal Engine 4 Introduction: Chapter_1_Base_Shape 26 min Chapter_2_VDB_Setup 4 min Chapter_3_Detailing 12 min Chapter_4_Texturing 21 min Chapter_5_Remesh 10 min Chapter_6_LOD's 9 min Chapter_7_Save_File 15 min Chapter_8_Bake 4 min Difficulty : Intermediate-Advanced Format: Recorded video chapters
  2. Wireshape is currently selecting participants for its Private Beta Program. Created for provide a high quality web stock of 3D scanned models for extreme closeups, Wireshape arrived to become a fast and accurate solution for customers who need high-fidelity 3D data. So, if you want to be one of the first to test pre-release products, offer your feedback, get gifts and special discounts, request an invite to beta here: https://wireshape.net/soon/ P.s. thanks to Marc for kindly helping to direction the location this announcement to the ODFORCE Community.
  3. Hi! I have created an asset(facial rig), and I want to use it as a part of another asset(character setup). I'm saving both of them into one .otl file, but because I'm using the absolute path for the facial rig("Save to the library" field in Type Properties) it stops working when I'm sending the .otl file to another computer. How can I embed one asset into another, so that they would be contained in one file? Also, when I'm trying to upload an asset to the orbolt, I'm getting an error "Embedded dependencies need to be within nested namespaces." I'm assuming that this error is related. Can you explain to me what does this mean and how can I embed the asset "within nested namespaces"?
  4. We have just published our latest GridMarkets Houdini Artist profile. This time we chat with talented Danish artist Pingo van der Brinkloev about his latest project, Knitbox, a collection of digital assets for the procedural creation of 3D fabric. There's a free downloadable asset for you to play around with. We hope you enjoy the feature, Patricia and the GridMarkets team
  5. Let's say I have an asset I have created with a number of dependencies to the files system, from ready flies, to caches, to creating point clouds and a not trivial (aka linear) approach in which the asset, based on certain conditions or user selection does one thing or another. If I want to publish this assets and all its dependencies to a repository I will have to traverse this, potentially, huge network with subnetworks inside (think Chops inside Sops for example) and rewire all these paths, move files to the repository and then export the asset. My feeling is that this particular task is kind of done in the Render Pre-flight but I wonder if it is accessible and more important, is this the best way to address a more compartmentalised pipeline? How are you guys approaching this? any suggestion? thanks in advance and hope this thread becomes a source of inspiration for everybody.
  6. I am using auto rig to create a character setup. It generates an animation rig and a deform rig. For convenience, I want to combine them into one network, so that animator would only need to create one node. I have just copied my deform rig into the animation rig network. It works, but I'm not sure if it's the right way to go about it. Also, when I'm trying to upload the asset to orbolt, I'm getting an error: "OTL file missing dependencies: [deform_rig_name]. Embedded dependencies need to be within nested namespaces. For more information see the namespaces section in the asset guidelines." So I have two questions: 1. Does it make sense to just copy deform rig into the animation rig to combine them into one asset, or is there a better way to go about it? 2. If I embed one asset into another one, how do I fix the missing dependencies error?
×