You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I was using vello, I found that it works very well when the stuff I want to draw is in full screen.
However when I zoom out to make it very small, the speed starts dropping down quickly.
The root cause is that I want to draw too much stuff in the same pixel.
I know there is a lot of pre-culling work been done, such as if the bbox of a path to less than a pixel, just skip it.
But I think there might be some edge cases, a lot of stuff is been queued in a same small area.
The truth is when a pixel is drawing stuff according to the PTCL, most of the later command is an opaque thing, which can override the current one, which means if there is 1000 things to draw, the first 999 is useless.
I am thinking if there is any optimize way to speed this process up.
Thanks a lot!
The text was updated successfully, but these errors were encountered:
Hello there
When I was using vello, I found that it works very well when the stuff I want to draw is in full screen.
However when I zoom out to make it very small, the speed starts dropping down quickly.
The root cause is that I want to draw too much stuff in the same pixel.
I know there is a lot of pre-culling work been done, such as if the bbox of a path to less than a pixel, just skip it.
But I think there might be some edge cases, a lot of stuff is been queued in a same small area.
The truth is when a pixel is drawing stuff according to the PTCL, most of the later command is an opaque thing, which can override the current one, which means if there is 1000 things to draw, the first 999 is useless.
I am thinking if there is any optimize way to speed this process up.
Thanks a lot!
The text was updated successfully, but these errors were encountered: