3ds max 9 x64 sp1
1.5.1.37369
The KPRTLBirth and KPRTLUpdate are visible in scene. They’re not hidden nodes. Is that expected?
- Chad
3ds max 9 x64 sp1
1.5.1.37369
The KPRTLBirth and KPRTLUpdate are visible in scene. They’re not hidden nodes. Is that expected?
They have always been (all of them), because we could not figure out how to make them invisible.
Will log it as a bug.
but you know who does
He is too expensive for consulting work. We have to figure this stuff ourselves.
Did you look at line 105 in PFOperatorDisplayDesc.cpp for maxsdk2010. I think this is what does it.
B.
I guess I should ask how are they visible? I don’t see any nodes in the VP nor do they select with the selection tool, they do however, select when I use the Select All command but in that case All PFlow nodes are selected.
This only being in 32-bit max (9, 2008, 2009, 2010) as I am a 600 miles away from my workstation at the moment.
Leading me to the second guess that this is a 64-bit issue?
I guess I should ask how are they visible? I don’t see any nodes in the VP nor do they select with the selection tool, they do however, select when I use the Select All command but in that case All PFlow nodes are selected.
This only being in 32-bit max (9, 2008, 2009, 2010) as I am a 600 miles away from my workstation at the moment.
Leading me to the second guess that this is a 64-bit issue?
The Select By Name dialog shows them as Helpers, while normal PFlow Operators are invisible helpers.
That’s what the report is about.
When you create a krakatoa operator in the flow, you see the helper object in the select by name list. Using max9-64bit. This should only happen for operators with “viewport gizmos” like ‘speed by icon’ otherwise you only see the operators as a sub-anim under the ‘pf source/event’.
It turns out that the mechanism used to hide PFlow Helpers is to have a special ClassID.PartB() that Max knows to not display. In the interests of not breaking everyone’s saved scenes, I have chosen to file this bug away under WONTFIX.
ugh. darn API after-thoughts. I bet a post-load callback could fix that. But those are a pain to write. I hope all future operators are hidden.
B.