Support
Common questions and real troubleshooting situations from MotionMaster 3D support. Can't find what you're looking for? Contact support.
Troubleshooting finder
Filter by the exact error, symptom, workflow, license issue, or feature area. These entries are based on real support conversations and cleaned up for public troubleshooting.
The current supported/recommended setup is Windows. Mac/Linux support has been requested, but should not be promised as available.
MotionMaster 3D 1.0.6 is recommended for Windows with Blender 5.1. Mac and Linux support is being considered for the future, but there is no guaranteed release date. If you already purchased and are on Mac or Linux, contact support privately so your case can be reviewed.
In older support cases this often came from Blender/Python version mismatch, dependency/runtime conflicts, or using an older MotionMaster build with Blender 5.1. Current policy is to use the latest MotionMaster 3D 1.0.6 with Blender 5.1.
Use MotionMaster 3D 1.0.6 with Blender 5.1 on Windows. Restart Blender after installing dependencies. If it still fails, open Window > Toggle System Console, try enabling the add-on again, and send the full console error, Windows version, GPU model, Blender source, exact Blender version, and MotionMaster version. Remove old MotionMaster versions before reinstalling.
This happened when users installed over an old version or did not restart Blender between uninstall/install steps.
Uninstall MotionMaster from Preferences, close Blender completely, reopen Blender, then install the latest zip again. If an old extension folder remains, remove the old MotionMaster folder from the Blender extensions path before reinstalling.
At that point the exact Blender console error is needed. It may be dependency, DLL/runtime, old install conflict, Blender source, or environment-specific.
Open Window > Toggle System Console in Blender, repeat the action that fails, and copy the full console error. Send that error together with your Windows version, GPU model, Blender version/source, and MotionMaster version so support can identify the exact cause.
One resolved case found an old ONNXRuntime version/conflict after the user thought they had cleanly reinstalled Blender.
If normal reinstall does not work, check for old dependency/runtime conflicts. Do a genuinely clean Blender/MotionMaster install, remove old MotionMaster versions, and provide the console log so support can identify conflicting packages.
Blender 5.1 uses its own Python 3.13, so installing packages into system Python or an older Python can leave MotionMaster unable to load the correct build.
Install dependencies from MotionMaster preferences so they target Blender’s Python. If needed, open the Blender system console and check the full error. In one user-reported fix, PyTorch needed to be installed for Blender’s actual Python environment rather than Python 3.11/system Python.
The solver usually did not get enough usable information, such as not enough features, not enough matches, insufficient overlap, too much blur, or too little parallax/location movement. It can also be affected by dependency or import issues.
First check the console log. Then try footage with real camera position movement, not rotation only, with stable textured background, less blur, and enough overlap. Update to the latest version, reset/delete failed previous result files for that sequence, and share the footage if the cause is unclear.
3D camera solving needs parallax: objects at different distances must shift relative to each other as the camera position changes. Rotation alone gives no depth information, so the photogrammetry solvers cannot reconstruct a camera path.
Use the Tripod Tracker (new in 1.0.7, Max tier). Open MotionMaster 3D Planar & Tripod Trackers, choose Tripod, and it solves pan, tilt, and roll with automatic focal-length estimation (Auto Lens). It reports honestly when the focal length is mathematically unobservable. Only use Heavy or Quick Tracking when the camera physically moves through the scene; if it does not, Tripod is the right tool.
A planar tracker follows a flat 2D surface without reconstructing 3D camera motion, so it works on shots with little or no parallax. Camera solving (Quick/Heavy) needs parallax. Before 1.0.7 MotionMaster 3D only did camera solving; 1.0.7 added a dedicated Planar Tracker.
Yes, since 1.0.7 (Max tier). Open MotionMaster 3D Planar & Tripod Trackers, choose Planar, pick an engine (Production CUDA on NVIDIA, TAPNext++ Hybrid, or Classic CPU), and click Open Track Workspace. Draw a four-corner quad on the reference frame, track forward or backward, and correct any drift with AdjustTrack without overwriting the raw solve. Publish gives you a native Blender Plane Track, a compositor Corner Pin node wired to the clip, and a 3D plane, either camera-parented (Object Motion) or as a fixed plane with an animated camera (Camera Motion). For flat or low-parallax shots use Planar; for camera moves through a scene use Quick or Heavy Tracking. See motionmaster3d.com/documentation/planar-tracking.
Moving foreground elements are not stable scene geometry. Water/ocean changes shape frame to frame. If moving objects cover too much of the frame, the solver lacks stable background features.
Mask moving foreground objects when possible and use footage with stable background geometry and visible parallax. If the moving subject covers most of the frame or the background is blurred/featureless, the shot may be very difficult or unsuitable for a clean 3D solve.
This can be difficult because the moving subject covers/occludes the background and the background may lack sharp trackable detail.
This can work in some cases, but green screen shots are often difficult because the moving subject can cover the trackable background. Try Heavy Tracking with masking where possible. If AI masking is not enough, use polygon masks or a shorter test section first. If the shot is critical, contact support with a sample before relying on this workflow.
Resolution alone is not enough. Tracking needs clear texture/detail, enough parallax, low motion blur, stable background, minimal reflections, and visible features that persist through the shot.
Use brighter footage with faster shutter speed, less ISO noise, less motion blur, stable textured geometry, and physical camera movement. Mask moving foreground objects. Test shorter sections first before long sequences.
The quality score is about usable trackable detail, not just pixel resolution. Motion blur, low texture, reflections, compression, close-up objects, bad color profile, or lack of parallax can lower usable tracking quality.
Use footage with sharper details, more light, less blur/noise, more stable texture, and enough physical camera movement. Try a different color profile or image sequence if that helped in testing. Share the error and sample frame if it continues.
Large frame counts can be extremely expensive. One case involved about 10,000 frames, which explained the long processing time.
Test a shorter section first, confirm the solve works, then increase the frame range. Downscale or use a higher step rate for tests. If it truly freezes, send the log/screenshot and Blender/MotionMaster version.
Since 1.0.7 there is a real Cancel button (Max tier). Older versions had no built-in cancel and required a terminal interrupt.
Update to 1.0.7 or newer and click Cancel in the MotionMaster 3D Progress panel. The job stops and any partial output is kept. On versions before 1.0.7 the only workaround is to open the system terminal and press Ctrl + C, which can error if done during post-processing.
One support case initially looked footage-related but was later reproduced by Axel and identified as a bug in the add-on code.
First make sure you are viewing the MotionMaster-generated camera, not Blender's default camera. If the MotionMaster camera still has only one keyframe, update to the latest version and contact support with the footage, a screen recording, and your Blender/MotionMaster versions so the issue can be reproduced.
The Photogrammetry Importer add-on may be disabled or failing to enable. There were also version/dependency-related import issues.
Enable the Photogrammetry Importer add-on manually, then use Import Results again. If the error says enable() got an unexpected keyword argument default, check Blender 5.1 compatibility and dependencies, and send the full console log.
One resolved case had the camera animation starting at a high frame number while the background images started at frame 1.
Check the camera animation start frame and background image/movie start frame. If the camera animation starts at frame 86400, set the background image sequence to start at the same frame instead of frame 1.
Older cases included a bug or misuse of the selector. Image filenames also matter: frame numbers should only be at the end of filenames.
Use the small folder icon and select the folder containing the image sequence, not every image. Make sure filenames only have numbers at the end, such as name_0001.png, name_0002.png. Install dependencies and restart Blender. If it still fails, send a screen recording and sample frames.
A support reply said an update was being worked on to remove these warnings. In the meantime the workflow can continue by using the background movie clip normally.
If the track otherwise works, add the background movie clip to the camera as usual and continue. If results are missing or import fails, send the full log and project details.
For mesh/dense workflows, undistorted footage is part of the workflow and the generated undistorted footage should be used as the background.
In Heavy Tracking Simple View, enable Undistort when needed. After the run, use the generated undistorted image sequence from the results folder as the camera background. Mesh generation requires Undistort and High Quality Mesh/Dense workflow beforehand.
The plate is undistorted for tracking and CG is composited on the undistorted plate; the original distortion is then applied back to the CG or the combined result. Since 1.0.7 MotionMaster 3D exports lens calibration and STMaps for exactly this.
In 1.0.7 (Max tier), open Lens Distortion / STMap in Heavy Tracking, choose one of the 12 camera models (or enter known parameters), solve, then export lens_calibration.json plus undistort and redistort STMaps from the Solved Result you select. Use the redistort STMap in Nuke, Fusion, or After Effects (with an STMap plugin) to put the distortion back on your CG. Inside Blender you can still use the Movie Clip Editor lens values with the Movie Distortion node in Distort mode.
Anamorphic footage often needs de-squeezing before tracking. Since 1.0.7 MotionMaster 3D has a full lens calibration and STMap workflow with 12 COLMAP camera models.
MotionMaster 3D can usually track anamorphic footage; if squeezed footage tracks poorly, de-squeeze before tracking. For lens calibration and STMap workflows use the Lens Distortion / STMap section in Heavy Tracking (1.0.7, Max tier): pick a camera model, solve, and export lens_calibration.json plus undistort/redistort STMaps. A dedicated anamorphic model is not one of the 12 models, so use the closest radial model on de-squeezed footage and check the result. See motionmaster3d.com/documentation/lens-calibration-and-stmaps.
For masking out moving objects in Heavy Tracking, the Tiny model was previously recommended as sufficient.
Start with the SAM2 Tiny model. It is usually enough for masking moving objects in Heavy Tracking and uses fewer resources. If the mask quality is not sufficient, try a larger SAM2 model, but expect higher memory and processing requirements.
MotionMaster 3D 1.0.6 added multi-object AI masking and multi-layer/polygon masking workflows.
Yes, MotionMaster 3D 1.0.6 supports AI masking for multiple moving objects and multi-layer masks. Complex footage may still need manual review or polygon mask refinement.
The latest masking workflow supports multiple masks and single masks, including AI and animatable polygon masks.
Use the multi-layer masking workflow from the 1.0.6 update. Create the main mask first, then add additional AI or polygon mask layers for objects that need to be removed or refined. The 1.0.6 update video shows this workflow in the masking section.
Could be a model path, dependency, GPU, or PyTorch issue. Need full console output.
First confirm the SAM2 Tiny/model files are downloaded in preferences. Then open Window > Toggle System Console, try creating the mask again, and send the full console output/screenshot so support can identify model path, dependency, or GPU errors.
Users sometimes miss the website Download page or need to log into Lemon Squeezy/View Order to see files.
Use the Download page on motionmaster3d.com after logging in, or open the purchase email receipt, click View Order, and make sure you are logged into Lemon Squeezy with the purchase email so the files appear.
Support suspected credential/machine hash caching or stale local files. Steam Blender was suspected in one case, but another user had it without Steam.
Try revoking machines on the account page, installing the latest version, removing old add-on folders, and resetting the local MotionMaster cache in %LOCALAPPDATA%\MotionMaster3D\. Because this touches activation state, contact support if the issue continues.
The website supported a Standard-to-Max upgrade path where the remaining difference is paid.
Yes. You can upgrade later from the Buy section or account flow and pay the upgrade price instead of buying a full second license. Check the live Buy page for the current upgrade amount.
MotionMaster is positioned as an affordable one-time-license Blender tool.
MotionMaster 3D is a one-time purchase, not a subscription. Check the live Buy page for the current Standard and Max prices before purchasing.
No general free trial was available in prior replies. For uncertain users, support can help pre-check whether their footage/workflow is a good fit.
There is not currently a free trial. If you are unsure whether MotionMaster fits your footage or workflow, contact support with a short sample or description before buying. Check the live Buy and Terms pages for the current purchase and refund terms.
The dashboard relies on the add-on sending a finish message to the server. If the PC turns off or the job is interrupted, that finish message may never arrive.
This is usually a dashboard sync issue if the local process has already stopped. You can usually ignore the stale running job. If tracking is still running locally, cancel it from the system terminal with Ctrl + C. Future updates should make stale jobs clean themselves up more reliably.
Perspective Matcher was released before its documentation page; the page now exists.
See motionmaster3d.com/documentation/perspective-matcher. It covers aligning a Blender camera to a still reference image using perspective guide lines, vanishing points, focal length, and camera orientation. If you are stuck on a specific image, contact support with the reference image and the result you want.
Simply changing the original camera’s rotation mode can break animated rotation curves, especially with parent transforms and local/world-space differences.
Do not directly change the original MotionMaster camera rotation mode after solving. Instead, create a duplicate/export camera, bake the final world-space motion to XYZ Euler keyframes with Visual Keying enabled and Clear Parents enabled, then export that baked camera to FBX for Fusion.
A support user reported this as a potential bug in the batch process/watch folder workflow.
This is a known batch workflow limitation. Until it is fixed, convert or process videos one at a time, or manually separate each video into its own output folder so frames from different videos do not overwrite each other.
A support user reported this as a potential bug. Axel recommended Heavy Tracker as a more robust workaround.
Use Heavy Tracker for more robust results while the batch/Quick output issue is investigated. If reporting it, include the result folder, console log, MotionMaster version, Blender version, and steps.
Older versions may not have detected/used GPU as well. Version 1.0.6 improved GPU/speed behavior according to a user follow-up.
Use MotionMaster 3D 1.0.6, install the latest NVIDIA drivers, and make sure the CUDA/PyTorch dependencies are installed for Blender's Python. If the GPU still appears unused, send the Blender system console log to support.
Both can work, but action cameras/phones can introduce rolling shutter, distortion, blur, noise, and fast movement.
Both GoPro and phone footage can work, but use good light, sharper footage, less motion blur, and enough parallax. GoPro may work better in some user tests. For distortion-heavy footage, use the undistort workflow and test short sections first.
Vertical footage itself is not the core issue, but tools/settings and footage suitability still matter.
Vertical footage can be attempted if the workflow supports it, but make sure any vertical footage setting is enabled where applicable, and that the shot still has enough parallax, sharp details, and stable background.
MotionMaster uses online account/license activation. Exact offline options need confirmation before promising.
Offline VFX workstations need to be checked before purchase. Contact support with your activation requirements and workstation setup so the current options can be confirmed for your case.
1.0.7 added a Planar Tracker, a Tripod Tracker, and point-cloud surfaces. Object tracking is handled through Camera Inversion (turn a solved camera into object motion) rather than a dedicated object tracker.
Planar tracking: yes, since 1.0.7 (Max) with the Track Workspace, AdjustTrack, and native Plane Track / Corner Pin output. Tripod (rotation-only) tracking: yes, since 1.0.7 (Max). Surfaces: Point Cloud Surface builds triangle, quad-dominant, or grid surfaces from point clouds. Object tracking: use Camera Inversion to convert an animated camera into animated object motion for fixed-camera setups; a dedicated supervised object tracker is not included. Contact support with the shot type if you need something else.
MotionMaster does not currently natively support 360 videos based on prior support reply. Some extracted sub-camera sections might be trackable.
Native 360 footage support is not currently available. In some cases you may be able to extract normal perspective views from the 360 video and track those as separate shots. AprilTag scale detection should only be treated as available if it appears in the current documented feature set.
Advanced features are split across Standard, Max, and Studio. Every 1.0.7 capability (Planar Tracker, Track Workspace, Tripod Tracker, lens calibration and STMaps, 3D Point Generator, Point Cloud Surface, Camera Footage Projection, Multi-Frame Texture Bake, job cancellation) is Max-only. Studio has every Max feature plus priority support for companies at or above the commercial revenue limit.
Check the live pricing comparison at motionmaster3d.com/buy for the current Standard vs Max feature list. All 1.0.7 features are Max features; Standard receives the 1.0.7 update with its fixes and panel improvements and can upgrade to Max at any time for the price difference.
The website chat/upload can be limited, especially for videos, 4K frames, and sequences.
Upload the footage, the first 100 to 250 frames, a zipped image sequence, or a screen recording to Google Drive, WeTransfer, or a similar file-sharing service. Make sure link access is enabled before sending it to support. For private client footage, send a similar test clip if you cannot share the original.
The support page was replaced by the Contact page, and a forgot-password email link bug existed but was fixed in one case.
Use the current Contact page for support. If a forgot-password, download, or support email link opens a 404 page, report it with the email/context so it can be fixed server-side.
Could be the MotionMaster Buy page or Lemon Squeezy payment handler. Need a screenshot/screen recording to identify where it freezes.
Check whether the freeze happens on the MotionMaster Buy page or inside Lemon Squeezy checkout. Try refreshing, disabling aggressive browser extensions, or using another browser. If it continues, contact support with a screenshot or screen recording.
Payment may not have completed or may still be processing, especially across countries/payment methods. Need order details to verify.
If the payment was just made, wait a short while and refresh your account/download page. If the order still does not appear after a few hours, contact support privately with your order details, purchase email, and checkout name. Keep private payment details out of public comments.
MotionMaster 3D is a separate product, but Axel has previously offered sales/discounts to earlier customers.
MotionMaster 3D is a separate product from FlaxTrax and FlaxFlow. If a discount is active, use the approved discount code. If you previously purchased an older product and need help, contact support privately with your purchase or order email.
Different tools have different strengths. Overclaiming can create distrust.
MotionMaster 3D is built around an integrated Blender workflow: automatic camera tracking (Quick and Heavy), planar and tripod tracking, lens calibration and STMaps, masks, dense point clouds, mesh and surface generation, projection, texture baking, cleanup, alignment, and batch processing, with one-time pricing. The best tool still depends on the shot. We publish honest side-by-side guides against Camera Tracker 6, Blender native tracking, SynthEyes, FlaxTrax, FlaxFlow, PFTrack, and 3DEqualizer at motionmaster3d.com/compare. If you are unsure, test with your footage or contact support with your use case.
MotionMaster 3D is a one-time purchase, not a subscription, so there is normally no recurring subscription to cancel.
MotionMaster 3D is not a subscription; it is a one-time purchase. If you want account or data deletion, contact support privately because that involves account information.
VAT is calculated by Lemon Squeezy at checkout based on buyer location and tax handling.
VAT is calculated by Lemon Squeezy during checkout. Depending on your location, taxes or VAT may be added before payment is completed.
Earlier support history showed update notification emails were not always in place or obvious.
Check the MotionMaster Download page or your order page for the latest available version. Update email notifications may improve over time, but the Download page is the safest place to confirm the current version.
MotionMaster dependencies may rely on Microsoft C++ runtimes. However, not every pyarmor/DLL issue is necessarily solved by reinstalling VC redist.
Install both official Microsoft Visual C++ Redistributables, x64 and x86, then restart Windows. After that, install MotionMaster dependencies from preferences and restart Blender. If it still fails, contact support with the exact VC_redist installer error, Windows version, and Blender system console output.
A real Cancel button shipped in 1.0.7 (Max tier).
Yes, since 1.0.7. Click Cancel in the MotionMaster 3D Progress panel to stop any running Heavy, Dense, Mesh, or batch job; partial output is kept. Before 1.0.7 the only workaround was Ctrl + C in the system terminal.
Most MotionMaster failures depend on exact footage, Blender version, dependencies, paths, console logs, and workflow steps. Guessing can lead to wrong advice.
Logs, screenshots, version numbers, GPU/Windows details, and small footage samples make it possible to reproduce the issue and give a real fix instead of generic advice. The most useful details are the Blender system console output, Blender/MotionMaster version, exact error/result, and a shareable clip or test scene when possible.
Discounts can be platform-specific, time-limited, or configured incorrectly. Public comments should not expose purchase/account details.
Contact support privately with the product link, purchase email or order details, expected discount, and a screenshot of the checkout error. Keep private order details out of public comments.
There is no general free-license policy in public support. Axel may choose exceptions privately, but that should not be promised generally.
Free licenses are not generally available through public comments or support requests. MotionMaster is kept affordable as a one-time license. If you believe you have an exceptional case, contact support privately.
The three engines trade speed and robustness against hardware requirements.
Production CUDA (default) is the fastest and most robust on an NVIDIA GPU. TAPNext++ Hybrid adds long-track AI guidance for difficult, low-texture, or long shots and needs CUDA PyTorch plus a one-time verified model download of about 2.4 GB from the panel. Classic CPU runs on any machine without CUDA and is the right choice if you have no NVIDIA GPU. All three publish the same outputs.
Motion blur, low contrast, occlusion, or the surface leaving frame can make a corner lose lock. AdjustTrack exists so you correct it non-destructively.
In the Track Workspace, go to the first bad frame and either set a protected manual key on the corner or place AdjustTrack reference points and move them to the true position. Corrections are layered on top of the raw solve, so the original track is never overwritten and re-publishing does not stack corrections. Read the Track Error (Measured) curve to find where the drift starts. For intervals where the surface is fully off-screen, choose a gap policy (Interpolate and Hold Ends, Interpolate and Extrapolate, Hold Nearest, or Require Measured Frames).
Publish creates native Blender data so no external tool is required.
A visible native four-corner Plane Track, an animated compositor Corner Pin node with a connected Movie Clip source, and a four-vertex 3D plane. Choose Object Motion (camera-parented animated plane) or Camera Motion (fixed plane plus animated camera with focal-length estimation). Add To Existing Camera publishes further surfaces into the same camera. A portable planar_track.json is written so results can be recreated from Import Results without retracking.
1.0.7 added a complete lens calibration and STMap workflow to Heavy Tracking (Max tier).
In Heavy Tracking open Lens Distortion / STMap, choose one of the 12 COLMAP camera models (or enter known parameters), run the solve, then pick the Solved Result and export lens_calibration.json plus undistort and redistort 32-bit STMaps. The STMaps are Nuke/Fusion-compatible. Details: motionmaster3d.com/documentation/lens-calibration-and-stmaps.
Core FAQ
This error occurs when Blender detects a corrupted or conflicting version of the add-on already installed. Follow these steps to fix it:
Disable and uninstall the add-on
In Blender go to Edit → Preferences → Add-ons, find MotionMaster 3D, uncheck it to disable it, then click Remove.
Delete the leftover files manually
Blender sometimes leaves files behind even after uninstalling. Open File Explorer and navigate to:
%APPDATA%\Blender Foundation\Blender\<version>\extensions\user_defaultReplace <version> with your Blender version number (e.g. 5.2, 5.1). Delete the MotionMaster 3D folder inside user_default if it exists.
Fully close and reopen Blender
Make sure Blender is completely shut down, not just minimised. Reopen it fresh.
Confirm the add-on is gone
Go back to Edit → Preferences → Add-ons and confirm MotionMaster 3D no longer appears in the list.
Install from the zip file
In Preferences → Add-ons, click Install from Disk and select the .zip file you downloaded from your order. Enable the add-on by ticking the checkbox.
Still seeing the error? Contact support and include your Blender version and the full error message.
Make sure you are logged in to your Lemon Squeezy account. The download files are only visible when you are signed in. If you are browsing as a guest the files will not appear. The easiest way to get there is through your purchase receipt email. Open the email and click "View order". This will take you directly to your order page on Lemon Squeezy. Once there, log in if prompted, and the zip file download will be visible on that page.
After purchasing, download the zip file from your order. In Blender, go to Edit → Preferences → Add-ons, click "Install from Disk", and select the zip file. Enable the add-on by ticking the checkbox next to its name.
First disable and uninstall the existing version in Blender Preferences → Add-ons. Remove any leftover files manually (see the installation error FAQ above for the exact path). Then close and reopen Blender and install the new zip file from disk.
1.0.7 is the biggest MotionMaster 3D update so far. It adds a Planar Tracker with a dedicated Track Workspace (layers, holdouts, AdjustTrack non-destructive corrections, a measured Track Error curve, and Add To Existing Camera), a rotation-only Tripod Tracker with automatic focal-length estimation, a Lens Distortion / STMap section in Heavy Tracking with 12 camera models and calibration plus 32-bit STMap export, a Solved Result dropdown for choosing between numbered results, a two-view 3D Point Generator, Point Cloud Surface with density-adaptive detail, Camera Footage Projection, Multi-Frame Texture Bake, and a Cancel button for running Heavy, Dense, Mesh, and batch jobs. It also fixes the Blender 5 "'Action' object has no attribute 'fcurves'" error and reorganizes every panel to start collapsed with a MotionMaster 3D prefix. All 1.0.7 capabilities are Max features. The full list is at motionmaster3d.com/documentation/version-1-0-7.
No. Planar Tracking, the Track Workspace, Tripod Tracking, the lens calibration and STMap workflow, job cancellation, the 3D Point Generator, Point Cloud Surface, Camera Footage Projection, and Multi-Frame Texture Bake are Max-only. Standard licenses receive the 1.0.7 update with its fixes and panel improvements, and can upgrade to Max at any time for the price difference.
This error means the 3D solver ran successfully but couldn't produce a reconstruction from your footage. The most common cause is that your camera only rotated in place (panning left/right or tilting up/down) without actually moving through space.
Why does movement matter? 3D tracking works by detecting parallax, the way nearby objects appear to shift more than distant ones as your camera moves through space. Think of it like your own two eyes: they're spaced a few centimetres apart, and that small difference in position is exactly what gives you depth perception. Camera tracking works the same way. It needs to observe the scene from at least slightly different physical positions over time in order to calculate depth and reconstruct the 3D space.
When your camera only rotates without moving, every object in the frame shifts by the same amount. There's no parallax, no depth information, and the solver has no basis for building a 3D reconstruction. The result is this error.
The fix: your camera needs to physically travel through space while you shoot. Some examples of footage that works well:
Even a modest but steady physical movement is enough. Simply standing still and pointing the camera at different things, no matter how much you pan or tilt, will not produce the parallax the solver needs to work.
Locked-off pan or tilt shot? Since version 1.0.7 (Max), MotionMaster 3D includes a dedicated Tripod Tracker: a rotation-only solver that estimates the focal length automatically and creates an animated Blender camera for shots where the camera never moves. Use it instead of Heavy Tracking for tripod footage.
Camera tracking, also called matchmoving, works by analysing parallax: the way objects at different distances appear to shift by different amounts as the camera moves through space. Nearby objects move a lot in the frame while distant objects barely move at all. This difference is what allows the solver to calculate depth and reconstruct the 3D scene.
Think of it like your own eyes. They are spaced a few centimetres apart, and each eye sees the world from a slightly different position. Your brain compares those two views and uses the difference to perceive depth. Camera tracking works the same way, except instead of two eyes it uses many frames captured from slightly different positions over time.
A tripod shot with only pan or tilt does not produce parallax. When the camera rotates in place, every object in the scene, near and far, shifts by the same amount in the frame. There is no depth information for the solver to work with, and the reconstruction will fail or produce unusable results.
What works:
What does not work:
Even a small, steady physical movement is enough to give the solver the parallax it needs. The key rule is simple: move the camera's position, not just its angle.
The exceptions are the two shot-specific trackers added in 1.0.7 (Max): the Tripod Tracker is built precisely for rotation-only pans, tilts, and rolls, and the Planar Tracker follows a flat surface such as a screen or sign regardless of camera motion. Neither needs parallax, because neither reconstructs 3D depth from it.
The best footage for camera tracking has plenty of visible detail and texture in the scene, consistent lighting without extreme over- or underexposure, minimal motion blur, and a steady but translating camera movement. Footage that is difficult to track typically involves featureless surfaces (blank walls, sky, water), heavy motion blur from fast movement, lots of moving objects that occlude the background, or very low resolution.
Keep your shutter speed high to reduce motion blur. Move the camera smoothly. Avoid sudden jerky movements. Make sure the scene has enough textured surfaces for the tracker to latch onto. Avoid shooting plain walls, floors, or skies without any detail. If possible, keep the scene well-lit and evenly exposed. Wider lenses tend to give more parallax information than telephoto lenses at the same movement speed.
Use the Tripod Tracker (1.0.7, Max). Quick and Heavy Tracking need the camera to physically move through the scene; a nodal pan gives no depth information and will fail or produce nothing. Open MotionMaster 3D Planar & Tripod Trackers, choose Tripod, and it solves pan, tilt, and roll with automatic focal-length estimation, reporting honestly when the focal length is unobservable.
Yes. The Planar Tracker (1.0.7, Max) is a Mocha-style four-corner tracker. Draw a quad over the surface in the Track Workspace, track forward or backward with the Production CUDA, TAPNext++ Hybrid, or Classic CPU engine, fix any drift non-destructively with AdjustTrack, and publish a native Blender Plane Track, a compositor Corner Pin node wired to the clip, and a 3D plane, either camera-parented (Object Motion) or as a fixed plane with an animated camera (Camera Motion). Several surfaces can be published into the same camera.
In Heavy Tracking open Lens Distortion / STMap (1.0.7, Max), choose one of the 12 camera models or enter known parameters, run the solve, then select the Solved Result and export lens_calibration.json plus undistort and redistort STMaps. The STMaps are Nuke/Fusion-compatible, so you can composite on the undistorted plate and put the original distortion back on your CG.
One-time purchase. You pay once and own the license. There are no recurring fees or subscriptions.
Your purchase includes all updates within the same major version (1.x.x). For example, buying version 1.0 gives you 1.1, 1.2, 1.9, etc. for free. Major version upgrades (2.0, 3.0) may be offered at a discounted upgrade price.
We accept all major credit cards, PayPal, and bank transfers through our secure payment provider, Lemon Squeezy.
If you experience a genuine technical issue with MotionMaster 3D, contact our support team within 14 days of purchase. We will work with you to diagnose and resolve the problem. If we are unable to fix a verified software defect, you will receive a full refund.
Refunds are not granted for:
For full details, see our Terms of Service.
Yes. If you already own a Standard license you can upgrade to Max at any time by paying the $30 difference. Log in to your account, go to the Buy page, and the discounted upgrade price will be shown automatically. You keep everything you already have and simply unlock the additional Max features, including all 1.0.7 tools. Companies at or above $100,000 annual revenue should choose Studio instead.
Studio ($299) includes every Max feature plus priority support, and is required for companies with $100,000 or more in annual revenue. Standard and Max both include commercial use for individuals, freelancers, and companies below that limit. Studio can be invoiced to your company.
Each license supports up to 3 machines. You can manage your registered machines directly from your Account page: revoke old machines and register new ones at any time without needing to contact support.
MotionMaster 3D requires Blender 5.1 or newer and works with Blender 5.2. We recommend always using the latest stable release of Blender for the best experience.
An NVIDIA GPU with CUDA support is strongly recommended for best performance. The add-on will run on CPU-only systems but tracking speeds will be significantly reduced. For the 1.0.7 Planar Tracker, the default Production CUDA engine needs an NVIDIA GPU. Without one, switch the Engine setting to Classic CPU, which does the same job on any machine. The optional TAPNext++ Hybrid engine also requires CUDA PyTorch and a one-time verified model download of about 2.4 GB from inside the addon. Tripod Tracking, the 3D Point Generator, and the surface tools do not require a GPU.
MotionMaster 3D currently supports Windows only. macOS and Linux support is planned for a future release.
Full documentation is available at motionmaster3d.com/documentation, including the 1.0.7 feature guide, Planar Tracking, Tripod Tracking, Track Workspace, and Lens Calibration & STMaps pages. Video tutorials, including the 1.0.7 overview, are published on our YouTube channel.
Reach out through the Contact page (login required). We typically respond within 24 hours on business days.
We're here to help. Reach out and we'll get back to you within 24 hours.
Contact Support