Engine COMPs on build 2025.31550 seem to get stuck at the “engine_launching” state when initializing. I’ve tried loading several different kinds of tox files (files made with builds 2025.31550 and 2023.12230), but none seem to start up successfully. For testing, I loaded the same project file (created with build 2025.31550) with builds 2025.31550 and 2023.12230, and can only get the engine COMPs to load successfully within build 2023.12230.
I’ve included a zip file containing the .toe and .tox files I used for testing.
Thanks, and let me know if you need any further info!
TouchEngine Bug Testing 202531550.zip (77.5 KB)
Hi - working here with your files in 2023.31550.
Is the warning on the Engine COMPs in your picture just the “Loading…” warning or something else?
Can you post details of the machine including GPU model and driver version. If your GPU drivers aren’t the latest, please update them and try again.
You could also try in 2025.31740 which just got posted.
The warning given is the “Loading…” warning, yes.
The machine this was tested on is a ThinkPad P16 Gen 1, with an Intel i7-12850HX CPU and a RTX A2000 (8GB) GPU, with driver version 573.57.
I’ll update my GPU driver and see if results change, then try the latest TD version if that doesn’t fix things!
So I’ve tested:
Using build 2025.31550 with version 581.80 of my GPU’s driver, with toe/tox files originally saved in 2025.31550
Using build 2025.31760 with version 581.80 of my GPU’s driver, with toe/tox files originally saved in 2025.31550
Using build 2025.31760 with version 581.80 of my GPU’s driver, with toe/tox files re-saved/exported using TD build 2025.31760
Which all result in no change in behavior (Engine COMPs failing to load on version 2025.31760, but loading correctly in version 2025.12230)
Another interesting thing I noticed (though I’m not sure how related it is) is that the TouchEngine processes are also not killed successfully when exiting the program.
Thanks for the details.
It would be helpful if you could generate a dump file from one of the hung TouchEngine instances - could you open Task Manager, select TouchEngine (after an Engine COMP has been stuck for a while, or after quitting TouchDesigner), right-click and select Create memory dump file. The resulting file will be large but should compress well. Please either post a link here or send it to support@derivative.ca linking this forum thread.
It’s possible the integrated GPU is being used, so you should update your Intel graphics drivers as older Intel drivers are a known problem for TouchEngine: Download Intel Drivers and Software.
Then make sure TouchDesigner is running on the correct GPU - you can use a Monitor DAT in TouchDesigner or the Details section of Task Manager. If your laptop has its own power management software, make sure TouchDesigner is allowed to run on the Nvidia GPU.
As it’s running in 2023 builds, this may not be the issue, but worth eliminating as a possibility.
1 Like
I’ve gone ahead and updated all Intel related drivers on my system, and have not seen a change in behavior. I can also confirm that monitor DATs show that TouchDesigner is using my system’s A2000 GPU.
I’ve zipped together a few memory dump files, with 3 files being dumped before closing TouchDesigner, and 3 files after closing TouchDesigner. I’ll go ahead and send them in an email to the support address you mentioned!
