Home
Creators
Search Recent Random
Posts
Search DMs Popular Hash Lookup Tags Random
Importer
Import FAQ
Register Favorites Keys Review DMs Logout
Community
Telegram ThePornDude
Home Creators Posts Import Register Favorites Logout

PDG 101 - Pt.5: Problem Solving in TOPs (Patreon)

Published:
2020-12-31 09:45:41
Imported:
2026-06
Tags:
haven't archived this post yet. have a subscription? use the importer!

Videos

Downloads

  • PDG05_Files.zip

Missing 1 full-res photo, 1 file, as this post has not yet been imported.

Content

It's time for our first meta-episode in this course! Chris shares his best practices for coming up with top nets to solve more unusual problems, that might appear in your projects.

You can find the model used in this episode on Grabcad. This needs a little extra preperation for houdini though, so we recommend starting with the smaller example bgeo file, you can find in the project folder.

https://grabcad.com/library/2003-honda-cbr954rr-engine-1

Files

Previews only

PDG 101 - Pt.5: Problem Solving in TOPs

It's time for our first meta-episode in this course! Chris shares his best practices for coming up with top nets to solve more unusual problems, that might appear in your projects. You can find the model used in this episode on Grabcad. This needs a little extra preperation for houdini though, so we recommend starting with the smaller example bgeo file, you can find in the project folder. https://grabcad.com/library/2003-honda-cbr954rr-engine-1

Comments

jimbachalo

Thanks for this. Really useful workflow. How did you convert the cad file to bring inside Houdini?

Entagma_Chris
>>57942721

Hey! The short answer unfortunately is: I didn't. Houdini is still lacking a STEP importer as far as I know and the IGES importer does not handle surfaces all that well. I used Rhino 3D, which I still had back from university but I've also heard good things about MOI 3D as cheaper alternative.

nox

Thanks for the very helpful video, I have a question tho, is it possible to split them up via the geometry input node, then proccess the split up parts and export them via a ropgeooutput? without it having to recook the whole geoinput for every workitem? can get very costly performance-wise(Especially RAM-wise)(crashed my machine on 1/4CPUCount). Should I add an intermediary step of caching to disc and reading it back with a filepattern and then process them?

Entagma_Chris
>>69115194

Hey! The Geo Input already has a mode to save the input directly to disk. I'm fairly positive, this should get rid of large initial load times. Especially if you use bgeo or bgeo.sc, compared to say obj. If that somehow will not work, you can always just wire a rop geo output in between, make sure its cache mode is set to either "automatic" or "read" and cook it to cache your geo to disc once and read from cache on al subsequent cooks.