-
Notifications
You must be signed in to change notification settings - Fork 229
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
unstable 3D translation (especially along depth) for monocular pose estimation #285
Comments
Hi, Zhengdi Yu, long time no see.
|
Sorry for my late reply. So it seems that only ' Q2. There are two ways to calculate the translation in simple-romp, where I believe the second one is the old one used in ROMPv1, the version I'm familiar with. And I also remember that the first method was marked as 'wrong' in the |
Yes, due to the usage of sim3dr, I think that directly convert cam to trans3d is of enough accuracy for sim3dr rendering usage. Therefore, I use it directly. But BEV has made some progress in depth reasoning. So I just use BEV for depth estimation. |
Hi, long time no see. Glad to see your BEV's contribution. I have been playing with ROMP+blender now and developing something interesting. But the translation along the depth direction is always shaking, we can only set the camera right in front of the character, otherwise, it's a bit ugly.
I have two questions now:
In ROMP, I remember that you said you determine the depth order by the scale. But I remember that you just transform add cam_trans to the verts then directly go into render process. I didn't see the code to "determine the depth order". I guess maybe you actually regard the translation recovery process:
verts += cam_trans
as the "determine depth order" process?In BEV, do we have a more stable 3D translation now? Will it still shake along the depth direction? I haven't tried BEV with Blender yet. I'll try this later.
The text was updated successfully, but these errors were encountered: