Downstream Drei useProgress pmndrs/drei#314
I have a fix for useProgress but it highlights two things about our useLoader.
- We always call sync load actions
- We dont track a manifest of pending/loaded elements so cant accurately track progress.
What I want to do is cache the keys of urls called to load and then remove them on final.
This should really happen upstream in the loading manager but I think its something we can do first.
What this means?
When progress happens you get it in phases per loading call:
progress update 0 4193
progress update 0 4197.800000071526
progress update 100 5992.800000071526
progress update 100 5993.300000071526
progress update 0 5996.900000095367
progress update 50 6369.400000095367
progress update 50 6370
progress update 100 6382.700000047684
The first phase doesnt know the second exists, so it will report 100% done and then it gets reset. We could fix it when the next phase inits, but then we get that annoying windows 98 thing where the loading bar gets to 100% and resets over and over
If we had a manifest we'd be able to know in the progress/final call what item is being loaded etc and could give a better progress report.
Downstream Drei useProgress pmndrs/drei#314
I have a fix for useProgress but it highlights two things about our useLoader.
What I want to do is cache the keys of urls called to load and then remove them on final.
This should really happen upstream in the loading manager but I think its something we can do first.
What this means?
When progress happens you get it in phases per loading call:
The first phase doesnt know the second exists, so it will report 100% done and then it gets reset. We could fix it when the next phase inits, but then we get that annoying windows 98 thing where the loading bar gets to 100% and resets over and over
If we had a manifest we'd be able to know in the progress/final call what item is being loaded etc and could give a better progress report.