Hi, I'm trying to setup my scene (first project in Solaris) in Solaris but when I use transform node it tooks so slow. I know there are lots of building but the mash is not too heavy.
Is it normal situation or I do something wrong?
I have strong CPU AMD, 2 x RTX 2070 super and 128 GB RAM
YT link:
https://youtu.be/DQQ3oxtzQSQ [youtu.be]
Very slow transform
2842 4 0-
- Grzesiek B
- Member
- 26 posts
- Joined: Aug. 2014
- Offline
-
- jsmack
- Member
- 7740 posts
- Joined: Sept. 2011
- Offline
You've got '*' in the transform field. It's applying the transform recursively to every prim in the scene. Scope it to just the top level prims, and it will only be really slow and not super broken and slow.
It's probably slow because each of those prims has many child xformable prims which require recomposing the stage each time the transform is changed. It's not like object level where there might only be one transform with lots of geometry inside. It's more like if you had thousands of geo nodes and tried to move them all at the same time.
It's unfortunately I don't see this getting much better due to the architecture of hydra. What should be happening is one matrix is updated and the next draw call has a different xform concatenated to the xform chain than the frame before. What it looks more like is that hydra is updated a transform for each prim in the scene when ever any parent xform is changed.
It's probably slow because each of those prims has many child xformable prims which require recomposing the stage each time the transform is changed. It's not like object level where there might only be one transform with lots of geometry inside. It's more like if you had thousands of geo nodes and tried to move them all at the same time.
It's unfortunately I don't see this getting much better due to the architecture of hydra. What should be happening is one matrix is updated and the next draw call has a different xform concatenated to the xform chain than the frame before. What it looks more like is that hydra is updated a transform for each prim in the scene when ever any parent xform is changed.
-
- Grzesiek B
- Member
- 26 posts
- Joined: Aug. 2014
- Offline
-
- CoreSign
- Member
- 18 posts
- Joined: Aug. 2016
- Offline
-
- mestela
- Member
- 1737 posts
- Joined: May 2006
- Offline
I tried recreating the original post in 19.5 quickly, it seems ok now?
Steps:
It's not blindingly fast, but it feels tolerable, maybe 0.1s between updates? Have attached the hip here too if others want to have a look.
-matt
Steps:
- Grabbed the free pack of assets from kitbash3d. It's not a big set I know, but its all I could find for quick testing
- Used a tops graph to convert them from bgeo's to usd
- Stage manager to quickly layout all the assets, put under a single parent prim
- Copytopoints a bunch of these with different scales and rotations
- Transform the top prim
It's not blindingly fast, but it feels tolerable, maybe 0.1s between updates? Have attached the hip here too if others want to have a look.
-matt
-
- Quick Links