Skip to content
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

meshimage vs image #256

Open
aplavin opened this issue Jun 25, 2024 · 2 comments
Open

meshimage vs image #256

aplavin opened this issue Jun 25, 2024 · 2 comments

Comments

@aplavin
Copy link

aplavin commented Jun 25, 2024

meshimage claims to b "the same as image, but more efficient", but is it?..
image
The latter doesn't seem correct no matter how you look at it: axis ranges and actual sizes don't agree.

@asinghvi17
Copy link
Member

asinghvi17 commented Jun 25, 2024

Axis ranges are actually the same but meshimage doesn't have tightlimits enabled. That would be an easy thing to add.

I guess this is down to the rotr90 again. I guess we could add a switch and slowly deprecate that behavior. It's not that hard to do the rotation in the uvs...

I think your image also has interpolation enabled? Meshimage can't do that since it's using a texture...

@aplavin
Copy link
Author

aplavin commented Jun 25, 2024

By the axis ranges issue I mean that the horizontal axis for meshimage goes from 0 to 10, but clearly displays 100 image pixels and not 10. The opposite is true for the vertical axis.
Yeah, seems to be the 90-deg rotation issue: meshimage does it for the array content, but not for axis ranges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants