-
-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dataset import: Track progress of data texture and gradient texture generation #164
Comments
I sadly do not have a time for creating the proper PR for this, but here are the updated methods from my project which reports whole percent updates. The correct progressHandler just need to be passed to these methods. Hope it might help someone in the future trying to add it here. CreateTextureInternalAsync
CreateGradientTextureInternal
GetMinDataValue
GetMaxDataValue
CalculateValueBounds
|
Oh, I never noticed that you posted this here. Thanks @SitronX for sharing 😁 By the way, I think there's a small bug there, in case you didn't notice: You need to call using (ProgressHandler calcBoundsProgress = progressHandler.Fork(0.1f))
// use calcBoundsProgress as before instead of having to manually call |
Hello @mlavik1,
Ehhm, you are probably right, i made some modification in my project and used it kinda differently (also due to AR/VR nature), so the bug was a feature for me :D So ye it is possible there are some mistakes when translated here. In my project i used it with numbering the stages like you see here (this is not the 512x512x730 dataset :D) Loading.mp4 |
Ok, that's quite big for sure 😁 That gives 190 million iterations, so I guess that makes sense! Though, does it take as much as 19 seconds if you remove the progress reporting? I suspect that might be more expensive than the actual calculations.
Oh, right! That's definitely a use case that I need to support. As I've designed it now, you can only get the total progress value.. I'll add a By the way, I love seeing this in AR 😁 I'll really need to try out your project sometime soon. I don't have an AR headset, but I'll try with the Oculus headset I'm borrowing from my friend :D And mentioning VR/AR: If you were having performance issues when enabling lighting and cubic interpolation (render settings) in VR/AR, then you might want to merge in this fix: #178 |
Ahh that is cool, thanks for this notification.
I just tested it and the difference is actually really negligable, it is like 11 seconds when i removed it instead of 13
Actually this is a VR version just with added skybox :D But if someone has a hololens 2 device, the view you probably imagined is possible :D
Nice, thanks! :D |
See suggestion by @SitronX : #162 (comment)
The text was updated successfully, but these errors were encountered: