Hi, I have quetion about Pack primitive and trasform
I imported alembic file with lots of primitives and when I try move by "transform" one primitive it works quite fast and responsive. It is exactly what I expect because I am moving one point.
But...
After I unpack and pack again the situation has changed dramatically
Technical it is still one point so it should be fast the same like on beginning - yes?
Name atrybute: path
Create packed fragments: off
Pack primitive and trasform
2474 9 2- Grzesiek B
- Member
- 26 posts
- Joined: Aug. 2014
- Offline
- Grzesiek B
- Member
- 26 posts
- Joined: Aug. 2014
- Offline
- goose7
- Member
- 68 posts
- Joined: Sept. 2018
- Offline
- TwinSnakes007
- Member
- 603 posts
- Joined: July 2013
- Offline
The Geometry Spreadsheet is your friend here....also the Node Information window would've answered this as well..
Packed Geo is compressed in memory and that's why you have a faster DCC viewport, because, its is indeed only transforming a single point.
Unpacking the Geo removes that compression and the DCC viewport bears the full weight of the Geo, all the points, vertices, primitives, etc.,......hence, a slower DCC viewport.
I would imagine that building in your example, belongs to Group 46, so whether or not you are Packed/UnPacked, you can still isolate that building using that Group identifier - which makes it "appear" to you as if you are still interacting with a single point when UnPacked, when in fact, you are interacting with the full geo of your Alembic file, but, isolating data that belongs to Group 46 only for your Transform operation.
Packed Geo is compressed in memory and that's why you have a faster DCC viewport, because, its is indeed only transforming a single point.
Unpacking the Geo removes that compression and the DCC viewport bears the full weight of the Geo, all the points, vertices, primitives, etc.,......hence, a slower DCC viewport.
I would imagine that building in your example, belongs to Group 46, so whether or not you are Packed/UnPacked, you can still isolate that building using that Group identifier - which makes it "appear" to you as if you are still interacting with a single point when UnPacked, when in fact, you are interacting with the full geo of your Alembic file, but, isolating data that belongs to Group 46 only for your Transform operation.
Edited by TwinSnakes007 - Jan. 29, 2021 10:26:14
Houdini Indie
Karma/Redshift 3D
Karma/Redshift 3D
- Grzesiek B
- Member
- 26 posts
- Joined: Aug. 2014
- Offline
- tamte
- Member
- 8532 posts
- Joined: July 2007
- Offline
- Grzesiek B
- Member
- 26 posts
- Joined: Aug. 2014
- Offline
- TwinSnakes007
- Member
- 603 posts
- Joined: July 2013
- Offline
tamte
I'd assume they'd have the same performance...
My understanding is a Transform is a Matrix operation per-point.
So, if my model, for example, has 100million points, I wouldnt expect that operation to be the same time for 1point vs 100million points.
Edited by TwinSnakes007 - Jan. 30, 2021 09:11:21
Houdini Indie
Karma/Redshift 3D
Karma/Redshift 3D
- tamte
- Member
- 8532 posts
- Joined: July 2007
- Offline
We are talking about Packed Alembic primitive VS repacked as Packed Geometry primitive as per first post
So in my head it comes down to how efficiently viewport can handle updating such geo behind the scenes
Cause for transform it's just updating one matrix in either case
So in my head it comes down to how efficiently viewport can handle updating such geo behind the scenes
Cause for transform it's just updating one matrix in either case
Tomas Slancik
FX Supervisor
Method Studios, NY
FX Supervisor
Method Studios, NY
- TwinSnakes007
- Member
- 603 posts
- Joined: July 2013
- Offline
..ahhh, I knew it was something I was missing, well, then, that would depend on HOW it was being re-packed - since Pack SOP is user configurable, you control the granularity.
Assuming that the Pack SOP was configured correctly, then yes, they should behave the exact same.
Assuming that the Pack SOP was configured correctly, then yes, they should behave the exact same.
Houdini Indie
Karma/Redshift 3D
Karma/Redshift 3D
-
- Quick Links