Yes, you need a model of an object or a scene to perform tracking.

No, it shouldn’t. But the better model you have the better results you obtain from every key frame.

The model should fit the scene. Minor details aren’t very important and could have negative impact on tracking performance

No, GeoTracker can match the model movement on already filmed shots.

You may use 3D surface mask to exclude semi-transparent or reflective parts from tracking process.

If the overlapped area is relatively small GeoTracker will handle it. Otherwise you may use a 2D mask to exclude overlapping from tracking process.

GeoTracker’s output is the transformed input geometry.

No. As soon as you’ve done tracking you may export the results as a usual Nuke node (TransformGeo or Camera node) to pass them to other machines.

You can export the results as a TransformGeo or a Camera node on the Results tab.

You can use WriteGeo node to export geometry with its transformations.

Yes! Starting from the 12.2v4 version.

Yes, it's waiting for you in our Medium blog

Sure! They're on our examples page.

Yes, you can build a model using a video instead of a sequence of photos. Actually, there is no difference between the two ways.

Using all the pins from all the keyframes FaceBuilder recalculates the resulting model's shape and model's position in each keyframe.

Unfortunately, no. All the photos should have the same resolution. But we might change it in future releases.

Unfortunately, it's not possible now.

No, licenses for our plugins are host-independent.

Yes, our plugins licenses are independent.

No, it's not possible now, but we have it in our plans.

Yes, using Nuke's built-in WriteGeo node.

It's waiting for you here.

Sure! They're on the examples page.

We assume that you're going to use FaceTracker along with FaceBuilder, using FaceBuilder's output as an input model for FaceTracker. But you can easily use FaceTracker without FaceBuilder, check the question about a custom model below to find out how.

Yes, the workaround is described in the Custom Model question below. You don't need a license for FaceBuilder to export a default model.

You can export the default model of FaceBuilder, and then modify the shape keeping vertices count and order. Then you can import it back, and connect to FaceTracker. It uses vertices to understand what is what in the model (e.g. nose, lips, eyes, etc). So, you can manually move vertices if FaceBuilder's result doesn't suit you, remove or add faces, change normals and UVs, wrap a scanned model with our default model, etc.

Not at the moment, but we are considering adding support for custom blendshapes in future.

Not really, but it'd be easier if you can find a neutral expression to start from.

No, the tracking information is saved frame by frame, so you can abort tracking at any moment keeping the tracking information you have already got intact.

Yes, the FaceBuilder and FaceTracker are independent. You need subscriptions for both to work with both plugins. You can also get a bundle subscription.

You can use Nuke's built-in WriteGeo node with ABC format. After pressing "Execute" button specify the frames you want to export.

Yes! You'd only need to install Nuke 12.2v4 or newer.

Press ‘center geo’ button to position the object in front of the camera.

Click with right mouse button on a pin to remove it.

Nuke default camera is used in that case. The same as in ScanlineRender. Is has aperture of 1 and focal length of 1.

As the default camera with aperture of 1 is used when ‘cam’ input is not connected, small (< 1) focal length values are absolutely normal.

Sure! You will need Nuke 12.2v4 or newer.

ReadRiggedGeo’s goal is to introduce deformable geometry to Nuke so that the geometry can be deformed and animated. ReadRiggedGeo doesn’t imply making a fully functional 3D Creation Software from Nuke.

Currently it is not possible to export rigged geometry otherwise than as a sequence of rigid geometries or as an FBX with animated points.

ReadRiggedGeo supports a lot of geometry formats. FBX and Collada formats may be used to load rigged geometry when many others may be loaded with ReadRiggedGeo when ReadGeo in not enough. For example: Autodesk (.fbx), Collada (.dae), Blender 3D (.blend), 3ds Max 3DS (.3ds), Wavefront Object (.obj), Stanford Polygon Library (.ply), and some others...

Yes! You will need Nuke 12.2v4 or newer.

No. You can activate subscription keys manually from another computer with internet access using Manual Installation page. The Hardware ID can be found if you launch the License Server with the "run" command.

Host: services.keentools.io, port: 443. It happens when a subscription key is being installed and when a running instance of License Server is checking installed subscription keys from time to time.

Definitely! When our plugins are loaded they check KEENTOOLS_LICENSE_SERVER variable, and if it contains a string with a host address and/or a port number, they try to connect using it and get a license. Here are some examples of what this variable could contain: localhost (the default port will be used), 192.168.1.42, server.local:4242, 10.0.0.66:7766.

This may happen with subscription keys of a wrong type. Only Studio subscriptions work with License Server.

Check there are no firewalls between the user's machine and the machine with the license server. The default port used by License Server is 7096.

Please, check there are no other processes using that port on the machine where License Server is being run.

You can redirect stdout to the License Server executable, i.e.
‍"cat keys.txt | ./KeenToolsLicenseServer install"
or
‍"echo 'key1 key2 key3 ...' | ./KeenToolsLicenseServer install"

The subscription keys are being read during the startup, so you need to restart the existing License Server process to make newly installed keys available for users.

There's no difference if you know how to use the OS of your choice as a server.

Yes.

Subscription key is locked for up to two minutes after it was used last time.

In that case you either need to coordinate your work between two or more machines, or just get more subscriptions.

We recommend using Non-Sucking Service Manager, it's free and easy to use.

Please try to install Microsoft Visual C++ 2010 Redistributable Package.

This may happen when root certificates on your OS are obsolete.
To update them on old versions of Windows please follow instructions on this page. Usually launching this command is enough: "CertUtil –generateSSTFromWU Rootstore.sst".
Alternatively, you can activate licenses manually and then place activated license files in the license storage folder of license server.

The simplest way to install KeenTools for Nuke is to run the installer.

Yes, but only in Nuke 12.2v4 and newer.

The installer copies KeenTools files to Nuke plugins directory:
• OSX: /Library/Application Support/NUKE/x.x/plugins/
• Linux: /usr/local/NUKE/x.x/plugins/
• Windows: C:\Program Files\Common Files\NUKE\x.x\plugins\
where x.x is Nuke version (10.5 for example).

You should check you’ve installed the correct KeenTools bundle (i. e. OS and Nuke versions match yours). If versions match and you can’t see KeenTools in Nuke try to perform manual installation.

Remove KeenTools folder from Nuke plugins directory to uninstall KeenTools.
If you installed KeenTools using our installer, then the files would be placed in these folders:
• OSX: /Library/Application Support/NUKE/x.x/plugins/
• Linux: /usr/local/NUKE/x.x/plugins/
• Windows: C:\Program Files\Common Files\NUKE\x.x\plugins\

No, Non-commercial version doesn’t support third-party plug-ins.

‘manual’ directory is only for performing manual installation. It isn’t required if you’re using the installer (i. e. you can only share the installer if it suits your needs).

• copy KeenTools folder from ‘manual’ directory to any place you want
• add the path to KeenTools folder to Nuke path by adding nuke.pluginAddPath('PATH_TO_KEENTOOLS') to init.py file.

• copy KeenTools folders from ‘manual’ directories for every Nuke version and operating system you want to any place you want;
• add the path to all that folders to Nuke path.
For example if you want to work with different versions of Nuke on Windows you may:
• unpack WIN_KEEN_TOOLS.zip to C:/KeenTools (could be any directory);
• write the next lines to %HOMEPATH%/.nuke/init.py:
nuke.pluginAddPath('C:/KeenTools/NUKE8.0/manual/KeenTools')
nuke.pluginAddPath('C:/KeenTools/NUKE9.0/manual/KeenTools')
nuke.pluginAddPath('C:/KeenTools/NUKE10.0/manual/KeenTools')
nuke.pluginAddPath('C:/KeenTools/NUKE10.5/manual/KeenTools')
KeenTools will automatically choose which installation should be loaded.

Yes: "/S".

KeenTools won’t be loaded and an error message will be written to Nuke console.

Making changes in KeenTools installation may break it’s operability.

You can find menu.py file in KeenTools directory and edit it as you see fit.