Could someone from sidefx please explain why the polysplit node breaks across every version of houdini? and now I recently tried working on a Mac and load my modeling files that was originally created on a windows machine and the polysplits break on the mac that's using the same version of houdini that created them on windows. The only thing customer service could tell me was that I need to cache out the model! but maybe i'm dumb cause the one of the main reason I'm using houdini is for the proceduralism and polysplit nodes are a huge part of modeling even for procedural models for me! now I have a shit load of models that can only be opened on one computer using one specific version of houdini!
This is extremely unfair and it should be documented that probably the most important modeling tool is an unstable shit show in houdini or give guidance on what the issue is and how to avoid it! If it's some memory problem, will it be solved? what is the issue?
Polysplit Node Nonsense
280 6 1-
- traileverse
- Member
- 369 posts
- Joined: Nov. 2015
- Offline
-
- tamte
- Member
- 9344 posts
- Joined: July 2007
- Offline
You may want to post an example, if you want someone to try to figure out what may be the issue in your scene or whether it's really a bug
Since polysplit string is pretty clear description of what to split I'd assume it should be pretty clear if it's doing what it describes or not
Since polysplit string is pretty clear description of what to split I'd assume it should be pretty clear if it's doing what it describes or not
Edited by tamte - Nov. 13, 2025 13:02:09
Tomas Slancik
CG Supervisor
Framestore, NY
CG Supervisor
Framestore, NY
-
- traileverse
- Member
- 369 posts
- Joined: Nov. 2015
- Offline
Hello Tomas, here is a reduced file created on windows on H20.5; it doesn't work in H21 without polysplit errors and it doesn't work on Mac on H20.5 nor H21 for me either.
When I load this exact file on the PC it was created on in H20.5, no problems; If I try H21 on that same PC, errors all over the place! try it on mac on any houdini, errors all over the place!
When I load this exact file on the PC it was created on in H20.5, no problems; If I try H21 on that same PC, errors all over the place! try it on mac on any houdini, errors all over the place!
hou.f*ckatdskmaya().forever()
-
- tamte
- Member
- 9344 posts
- Joined: July 2007
- Offline
from a quick look it doesn't seem like the PolySplit is the main issue
it seems like by the time it gets to Polysplit, the geo is already not containing the elements that PolySplit is supposed to split
I compared 3 different builds, but can't find a single one that would work, however all 3 resulted in different geo after "fuse2" node
it may be easier to find a culprit knowing which build has it working
it seems like by the time it gets to Polysplit, the geo is already not containing the elements that PolySplit is supposed to split
I compared 3 different builds, but can't find a single one that would work, however all 3 resulted in different geo after "fuse2" node
it may be easier to find a culprit knowing which build has it working
Tomas Slancik
CG Supervisor
Framestore, NY
CG Supervisor
Framestore, NY
-
- traileverse
- Member
- 369 posts
- Joined: Nov. 2015
- Offline
hello again Tomas, it's working on 20.5.684. No errors. It's a large file with lots of models and when opened elsewhere tons of errors and all pointing to polysplit nodes.
In fact, all my files with huge modeling networks and lots of polysplits have errors in various houdini builds and only work well in the version they were created in and on the computer they were created on!
It all feels extremely fragile! I've created lots of models with semi procedural functionality where freezing does not make sense for some and I'm now very concerned!
In fact, all my files with huge modeling networks and lots of polysplits have errors in various houdini builds and only work well in the version they were created in and on the computer they were created on!
It all feels extremely fragile! I've created lots of models with semi procedural functionality where freezing does not make sense for some and I'm now very concerned!
Edited by traileverse - yesterday 10:35:43
hou.f*ckatdskmaya().forever()
-
- tamte
- Member
- 9344 posts
- Joined: July 2007
- Offline
traileversePolySplit is very sensitive to the input geo as it needs to do split on exact prim number, exact edge, etc.
tons of errors and all pointing to polysplit nodes
so it's likely to error out if for example is expecting to cut 10e5:0.5, but suddenly prim 10 doesn't have 6 edges anymore
so all I'm saying is that because Poly Split errors out it doesnt necessarily mean that polysplit is the issue
however if you stash the geo on node before in working build and then plug it to next PolySplit in non working and it still errors out, then you can assume it's the PolySplit, since on the same geo it should work
when I have time I'll check your file on 684 to see where the geo changes between builds
Tomas Slancik
CG Supervisor
Framestore, NY
CG Supervisor
Framestore, NY
-
- traileverse
- Member
- 369 posts
- Joined: Nov. 2015
- Offline
-
- Quick Links

