-
-
Notifications
You must be signed in to change notification settings - Fork 598
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
Wrong modelview when using pip version #219
Comments
Hi, thanks for the report! I think this needs further investigation. I don't think I currently have time to investigate. |
I've had one more person report issues with the projection being wrong in |
Hi @rstar000, I think this is a different (potential) issue from the one that was originally reported here. With "inverted", do you mean transposed? I would be quite surprised if the model-view matrix was transposed. Is it possible that you got fooled by the depiction of the three coloured drawn axes? They can often look like they point in the "wrong" direction, our brain's interpretation can fool us when only looking at a static image. I would suggest that you run it on a video where someone turns their head (or e.g. the live cam), it's much easier to see then whether the axes are drawn correctly. If you still think there is an issue, could you open a separate issue for it to continue the discussion there? Thanks! |
@patrikhuber Hey, sorry, I just found a silly bug in my projection code. I was using row vectors instead of column vectors for some reason. The matrix returned from pose.get_modelview() is absolutely correct! |
@rstar000 Great! :-) |
I am using eos 3D model to generate 2D depth maps. Initially, I used the python bindings compiled from source and everything worked fine. However, when using the version from pip, there is a problem with the modelview matrix that makes my code not work properly. Below you can see the difference between executing
demo.py
using the bindings compiled from source and the ones from pip (both of them are version 0.16.1):The text was updated successfully, but these errors were encountered: