Below is a list of known issues when working with PIXERA's TouchEngine integration, which allows .tox files to be played back and interacted with on the PIXERA timeline. For a review of the TouchDesigner extension refer to Part 1 and Part 2. For more on Renderbridge, the mechanism used to build the TouchDesigner integration, refer to this article.

TouchDesigner not visible under VR Button

If TouchDesigner doesn't appear as an option under the VR tab within PIXERA's Resources tab, then check your version of PIXERA. 26.1 R1 is the first version of PIXERA which has the integration built-in. If you're using an earlier version of the integration then contact support directly by sending in a ticket.

Manager & Client are Out Of Sync

As of 26.1 R1 PIXERA's TouchDesigner integration is in BETA. Synchronization of the TouchDesigner frame between a directing system and it's rendering clients currently isn't supported. It is only recommended to run your .tox file on a local system which also outputs to your target display(s).

Spinning Blue Wheel / Takes A Long Time To Load

When you add a .tox file to a Timeline or a Display/Screen object, as soon as you release your left mouse button two actions occur:

• TouchEngine is launched as a sub-process of PIXERA if you're on Windows 11 or it launches as a process on Windows 10.
• A check occurs to see which TouchDesigner license you have, and if it is compatible with TouchEngine.

If your cursor wheel spins for an excessively long time (longer than is reasonable for your hardware), this is likely an issue with your license or your system's ability to process your license. For more on TouchDesigner's Licensing please review their licensing information on Derivative's website.

It's also possible the issue has to do with which version of TouchDesigner your .tox file was saved under.
 

To correct a license issue

• Make sure you've installed TouchDesigner in a standard location on disk. If PIXERA can't find TouchEngine then it won't launch TouchEngine. PIXERA expects TouchDesigner requirements to be located in: C:\Program Files\Derivative
• Make sure you can launch TouchDesigner natively on your system. If it fails to launch then this must be taken care of first before anything inside of PIXERA. Check that your dongle is secure in your system, or that your software key is correctly installed, or that your CodeMeter Control Center is running and registering your Floating Cloud License.
• Make sure you're correctly licensed for the version of TouchDesigner you'd like to run inside of PIXERA. Any version of TouchDesigner which can run TouchEngine and is also a valid TouchDesigner Commercial, Educational, or Pro license will work in PIXERA. If your system doesn't register a valid Pro/Commercial/Player license then it will default to Non-Commercial.  Non-Commercial doesn't work with PIXERA. Check out TouchDesigner's License Features here for more information.

• If you've installed an additional parallel build or two of TouchDesigner on the same system you may need to 1.) uninstall all versions except that which you intend to use with your .tox or 2.) specify what version is used for your specific .tox file. To specify which version of TouchDesigner used to launch your .tox file:
  1. Within File Explorer, navigate to the .tox file on disk, then right click on your .tox file and select Properties
  2. Under the General tab there is an option called Opens With
  3. Using the Change... button you can now specify which version of TouchDesigner to use with that specific .tox file.

Keep track of your TouchDesigner build

The excessive load time of a .tox file in PIXERA could be indicative of a TouchDesigner build mis-match. When in doubt, check the build the .tox file was built in and ensure that either A.) your target TouchDesigner build is installed on your system or B.) you save the .tox file in your target TouchDesigner build
 

To fix this you could do one of the following:

• After your preferred TouchDesigner build is installed on your system, open the .tox file natively in the TouchDesigner editor and save the .tox file to disk using the target build.
• Navigate to the .tox file within File Explorer, right click on the file and in the menu look for Properties. Select it and under the General tab look for a parameter called Opens with…. Select the button beside the parameter and navigate to the executable of your target TouchDesigner build. This will associate a specific build to your .tox file.

ExtTD Errors

Engine: Message - ExtProcess[4]:ExtTD: Frame did not finish successfully: Allocation of a GPU resource failed

“ExtTD: Frame did not finish successfully” is from PIXERA's integration. “Allocation of a GPU resource failed” is from TouchEngine. The TouchEngine extension couldn't successfully load likely due to it attempting to launch on a non-dedicated GPU. To remedy this please refer to this article under the section called “Multi GPU Systems”

Pixera extension could not be loaded.

Error: 'opening extension 'C:/Program Files/AV Stumpfl/Pixera/build_xx_x_x/data/rxExt/extTouchDesigner/extTouchDesigner.dll' failed: API version mismatch'

Make sure your NVIDIA drivers are up to date according to our recommended versions. 

If you're moving project files to/from server to server make sure you're also using the same version of PIXERA across servers as well as the same version of TouchDesigner across all servers.