Polyextrude does not preserve point groups
3818 17 5- Rates
- Member
- 10 posts
- Joined:
- Offline
- Rates
- Member
- 10 posts
- Joined:
- Offline
- Aizatulin
- Member
- 495 posts
- Joined: July 2005
- Offline
- Gagui
- Member
- 55 posts
- Joined: May 2017
- Offline
- Aizatulin
- Member
- 495 posts
- Joined: July 2005
- Offline
- Gagui
- Member
- 55 posts
- Joined: May 2017
- Offline
- Gagui
- Member
- 55 posts
- Joined: May 2017
- Offline
- Hikari_
- Member
- 40 posts
- Joined: June 2023
- Offline
- jsmack
- Member
- 8041 posts
- Joined: Sept. 2011
- Offline
- Hikari_
- Member
- 40 posts
- Joined: June 2023
- Offline
- animatrix_
- Member
- 4712 posts
- Joined: Feb. 2012
- Offline
Hikari_
>Jsmack
Is the Edge Group Attribute lost in "Poly Bevel" also a intended one?
Unfortunately many nodes do not preserve edge groups either due to being overlooked or for performance reasons.
For example Subdivide SOP doesn't preserve the edge groups. If you want the original edge groups updated with the new topology, you have to write some VEX code.
Senior FX TD @ Industrial Light & Magic
Get to the NEXT level in Houdini & VEX with Pragmatic VEX! [www.pragmatic-vfx.com]
youtube.com/@pragmaticvfx | patreon.com/animatrix | pragmaticvfx.gumroad.com
Get to the NEXT level in Houdini & VEX with Pragmatic VEX! [www.pragmatic-vfx.com]
youtube.com/@pragmaticvfx | patreon.com/animatrix | pragmaticvfx.gumroad.com
- Hikari_
- Member
- 40 posts
- Joined: June 2023
- Offline
- animatrix_
- Member
- 4712 posts
- Joined: Feb. 2012
- Offline
Hikari_
>animatrix_
Thanks for the reply.
I will try to learn VEX as I go along.
If you don't mind, can you give me, a VEX beginner, some tips on how to take over group attributes?
For example, useful functions, etc.
These functions are useful:
https://www.sidefx.com/docs/houdini/vex/functions/inpointgroup.html [www.sidefx.com]
https://www.sidefx.com/docs/houdini/vex/functions/inedgegroup.html [www.sidefx.com]
https://www.sidefx.com/docs/houdini/vex/functions/inprimgroup.html [www.sidefx.com]
Senior FX TD @ Industrial Light & Magic
Get to the NEXT level in Houdini & VEX with Pragmatic VEX! [www.pragmatic-vfx.com]
youtube.com/@pragmaticvfx | patreon.com/animatrix | pragmaticvfx.gumroad.com
Get to the NEXT level in Houdini & VEX with Pragmatic VEX! [www.pragmatic-vfx.com]
youtube.com/@pragmaticvfx | patreon.com/animatrix | pragmaticvfx.gumroad.com
- Gagui
- Member
- 55 posts
- Joined: May 2017
- Offline
jsmack
This is not a bug, groups are not cloned onto extruded parts. Use a point attribute for extrusions to inherit.
Well, then is needed to rewrite the help pop up of the Preserve Groups option. It says face and edge groups are preserved but only primitive groups are preserved.
Edited by Gagui - Dec. 26, 2023 04:46:51
- HGaal
- Member
- 102 posts
- Joined: June 2023
- Offline
I also recently reported this bug and they even registered it. I naively hoped to use groups; after all, extrusion is the most important modeling function. And broken groups of edges and polygons are very annoying. But judging by the fact that the problem has been known since 2020 and after more than 3 years the developers haven’t lifted a finger to fix it, then expecting fixes in the coming years would be very naive on my part. In my opinion, this is a very shameful situation. And incomprehensible to us. How many people use feathers? 0.1% ? APEX? 0.0001% ? Why not spend part of your working time fixing the stupidest bugs that annoy 90% of users? Or on the tiny axes in the lower left corner that are hated by 100% of users? Or on the thin, barely visible axes of the handle? Or there are errors in all modeling tools, you don’t even need to look for them, users have been reporting for years. I honestly don't understand the company's strategy. Just to piss off users? Mystery.
- kodra
- Member
- 373 posts
- Joined: June 2023
- Offline
The strategical reason behind it is actually very simple.
People won't switch from Maya to Houdini just because Houdini has slightly better PolyExtrude. People wont switch from Houdini to Maya just because PolyExtrude is semi-broken.
Perhaps there are only 3 studios around the world that needs advanced feather tools. Then that's 3 more deals (that's quite a lot of money already, considering the price is like $6000 per seat). Fixing that little gizmos brings 0 sales guaranteed.
That's the best (and the worst) part about B2B business: if your software have one single advanced feature that people rely on, they have to buy it. Even the other 999 features are hard to use or borderline broken.
People won't switch from Maya to Houdini just because Houdini has slightly better PolyExtrude. People wont switch from Houdini to Maya just because PolyExtrude is semi-broken.
Perhaps there are only 3 studios around the world that needs advanced feather tools. Then that's 3 more deals (that's quite a lot of money already, considering the price is like $6000 per seat). Fixing that little gizmos brings 0 sales guaranteed.
That's the best (and the worst) part about B2B business: if your software have one single advanced feature that people rely on, they have to buy it. Even the other 999 features are hard to use or borderline broken.
Edited by kodra - Dec. 26, 2023 06:40:50
- HGaal
- Member
- 102 posts
- Joined: June 2023
- Offline
In search of some solutions, I downloaded several old but good hda for modeling on orbolt and decided to see what this wonderful developer is doing now. And in his channel for a long time there was only a blender. Apparently, he has completely switched to blender and is writing addons for blender.
Bugs and interface turn off many ordinary users. The developers are leaving behind them. The ecosystem shrinks and shrinks, there are fewer and fewer reasons to stay in it and do something for it, which tightens the vicious circle. That's how I see it.
And then wonder whether that “small” indifference really led to such bad results? but that's what always happens. Don't repeat these common mistakes, dear developers.
Bugs and interface turn off many ordinary users. The developers are leaving behind them. The ecosystem shrinks and shrinks, there are fewer and fewer reasons to stay in it and do something for it, which tightens the vicious circle. That's how I see it.
And then wonder whether that “small” indifference really led to such bad results? but that's what always happens. Don't repeat these common mistakes, dear developers.
- animatrix_
- Member
- 4712 posts
- Joined: Feb. 2012
- Offline
Hikari_
>animatrix_
Thanks for the reply.
I will try to learn VEX as I go along.
If you don't mind, can you give me, a VEX beginner, some tips on how to take over group attributes?
For example, useful functions, etc.
Here is an example that shows how to recreate a specific edge group after subdivision. It supports all subdivision algorithms except Houdini Catmull-Clark as that doesn't interpolate integer attributes (OpenSubdiv and Mantra-Compatible Catmull-Clark does).
int ptnew = findattribval ( 0, "point", "origpt", i@origpt ); if ( @ptnum == ptnew ) { int pts [ ] = neighbours ( 1, i@origpt ); foreach ( int pt; pts ) { int index = findattribval ( 0, "point", "origpt", pt ); if ( inedgegroup ( 1, "edges", i@origpt, pt ) ) { int newpts0 [ ] = neighbours ( 0, @ptnum ); int newpts1 [ ] = neighbours ( 0, index ); int sharedpt = -1; foreach ( int newpt; newpts0 ) if ( find ( newpts1, newpt ) >= 0 ) { sharedpt = newpt; break; } if ( sharedpt != -1 ) setedgegroup ( 0, "newedges", @ptnum, sharedpt, 1 ); } } }
If you want to handle all edges groups procedurally, you can either use a For Loop network or do everything inside a single Attribute Wrangle by looping over all edge groups within the same code.
Senior FX TD @ Industrial Light & Magic
Get to the NEXT level in Houdini & VEX with Pragmatic VEX! [www.pragmatic-vfx.com]
youtube.com/@pragmaticvfx | patreon.com/animatrix | pragmaticvfx.gumroad.com
Get to the NEXT level in Houdini & VEX with Pragmatic VEX! [www.pragmatic-vfx.com]
youtube.com/@pragmaticvfx | patreon.com/animatrix | pragmaticvfx.gumroad.com
-
- Quick Links