PDG 101 – Pt.7: Product Lineup by Christopher Kopic 28.01.2021 comments 4 Part of: PDG 101 PDG 101 automation, client work, csv, Houdini, lineup, PDG, product, Rendering, sidefx, tops, tsv, versioning, visualisation To view this content, you must be a member of Entagma's Patreon at $29 or more Unlock with Patreon Already a qualifying Patreon member? Refresh to access this content.
Peter 15.04.2021 Reply Hej! Thanks for great tutorials! You can type Single if(rint(atof(@Sc_Index)),0,1) Glass if(rint(atof(@Sc_Index)),1,0) To solve the string vs int problem. Have a great day / Peter
Steve 26.03.2022 Reply Bit late to the party on this one, but OMG this approach is going to change my life to product illustation work. Best thing I ever did switching from ‘other’ software to Houdini and thank you Entagam so much for all the great insights
Alex 16.03.2023 Reply You can simplify your display expression even more removing it completely and using: `@sc_name` in the Redshift_ROP>Objects>Force Objects. Candidate Objects set to * is evil
Alex 16.03.2023 Reply also if you want to cast a string to an int in a new attrib using the attributecreate node in tops, you can just use: int(“`@Sc_Index`”)
Unlock with Patreon
Hej!
Thanks for great tutorials!
You can type
Single
if(rint(atof(@Sc_Index)),0,1)
Glass
if(rint(atof(@Sc_Index)),1,0)
To solve the string vs int problem.
Have a great day / Peter
Bit late to the party on this one, but OMG this approach is going to change my life to product illustation work. Best thing I ever did switching from ‘other’ software to Houdini and thank you Entagam so much for all the great insights
You can simplify your display expression even more removing it completely and using:
`@sc_name`
in the Redshift_ROP>Objects>Force Objects.
Candidate Objects set to * is evil
also if you want to cast a string to an int in a new attrib using the attributecreate node in tops, you can just use:
int(“`@Sc_Index`”)