Is there a better format than PNG to store R16uint depth data on Android
I find I get precision artifacts when using ASTC.
\$\begingroup\$
\$\endgroup\$
4
-
2\$\begingroup\$ I get the sense from your past four questions that there's an effect you want to achieve, but the way you're trying to achieve it isn't quite working the way you want. Unfortunately, you've never told us what that overarching goal is, just asked about individual symptoms. This leads us to an XY problem, where an efficient way to achieve your end goal may exist, but none of our experts here will know to suggest it because they can't see what you're trying to do. I'd recommend backing up and asking "how to achieve this effect", including examples. \$\endgroup\$DMGregory– DMGregory ♦2024-07-24 11:02:09 +00:00Commented Jul 24, 2024 at 11:02
-
1\$\begingroup\$ Better in what way? You've identified that you've run into a precision problem with ASTEC, but you haven't shared the problem you have with using PNG. Without knowing why PNG isn't good enough &/or explaining the context of your problem, readers can only guess at alternatives. What problem are you having with using PNG to store depth data? \$\endgroup\$Pikalek– Pikalek2024-07-24 13:04:06 +00:00Commented Jul 24, 2024 at 13:04
-
\$\begingroup\$ depends on what you are aiming for. a raw blob of 16 bit values also works \$\endgroup\$Raildex– Raildex2024-07-24 17:55:07 +00:00Commented Jul 24, 2024 at 17:55
-
\$\begingroup\$ Thanks for all:) \$\endgroup\$gpu– gpu2024-07-25 00:28:22 +00:00Commented Jul 25, 2024 at 0:28
Add a comment
|