-
Notifications
You must be signed in to change notification settings - Fork 27
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
mark points obtained by converting to marker are not animated #249
Comments
Hi @ShuJiangLiu, Thank you for reporting this issue. I seem to be getting the following error when I try to use the menu "mmSolver > Convert To Marker":
This error is probably related to your issue - either way, it needs to be fixed. |
@ShuJiangLiu has confirmed (through email) that the error above is the same as he gets, however upon investigation even after fixing that error, there appears to be an error in the Convert to Marker UI. I have found that it's possible to fix the problem by manually entering the Frame Range as "Custom", and typing the Start/End frame numbers. This is a secondary bug, but it needs to be fixed. |
Python 2.7 returns a list from 'range()', but in Python 3.x 'range()' returns an iterator. To be compatible with both, we must force-convert the frame ranges to lists. GitHub Issue #249
I've fixed this issue and it will be released in v0.4.7, which will hopefully be released soon. |
Hi @ShuJiangLiu, v0.4.7 has now been released with the fix included. https://github.com/david-cattermole/mayaMatchMoveSolver/releases/tag/v0.4.7 |
Python 2.7 returns a list from 'range()', but in Python 3.x 'range()' returns an iterator. To be compatible with both, we must force-convert the frame ranges to lists. GitHub Issue #249
Problem or Feature
Hello, I can see in the camera that the locator points I have tracked perfectly match the head, but when I use the locator to generate mkr points by covert to marker, I can see in the camera that only the last frame has been picked up and no other frame range has been picked up And it turns out that his translateX and Y values haven't changed at all
Expected behavior:
Actual behavior:
Steps to Reproduce
Software Versions
mmSolver version: 0.4.6
Maya version:2022.3
Operating System: Windows 10 Pro v2009 (Build: 19045)
Cut ID: 202110272215-ad32f8f1e6
Maya Version: Autodesk MAYA 2022.3
Maya API: 20220300
Qt Version: 5.15.2
Compositing Manager: True
Window Manager: Windows Aero
GPU: Version : 2016.11.62.12. Feature Level 5.
Adapter : NVIDIA GeForce RTX 4070 Ti
Vendor ID: 4318. Device ID : 10114
Driver : 袀栿ǐ:17.1.58.818.
API : DirectX V.11.
Max texture size : 16384 * 16384.
Max texture coords : 32
Shader versions supported (Vertex: 5, Geometry: 5, Pixel 5).
Active stereo support available : 0
GPU Memory Limit : 12282 MB.
CPU Memory Limit : 124298 MB.
The text was updated successfully, but these errors were encountered: