Engine COMP not working in 2025 builds?

Hi all,

i’m trying to make some tox run inside an Engine COMP but somehow i’m not able to get any tox loaded. Not on my maching whit a commercial license and also not on this device (see screenshots below)

Windows 11 Home

Intel(R) Core™ Ultra 9 275HX (2.70 GHz)

image

Any idea what i’m doing wrong?

In the past when using Engine COMP’s it just worked (exposing custom parameters and inputs/outputs) but now i don’t manage to get it to run my tox in a separate process, or something maybe has changed on how to get them working?

Could you please assist or investigate?

Thanks & Gr,

Thomas

Hi

Palette components are in a wrapper with no parameters, inputs or outputs (try opening one by dragging the file into TouchDesigner rather than via the Palette to see). It looks like this component has loaded correctly.

Hopefully if you try another (non-Palette) component, with inputs, outputs and/or parameters, you’ll see those.

Think it also didn’t work with my custom tox files but will try again with the latest release and report back

Happy New Year everyone!

Seeing an odd thing as well. I’ve found that my tox files created in older builds (2025.30280) are opening in Engine COMP with disabled pars that I’m unable to Enable. I created the Float in the middle of the of the existing custom pars and this is what shows as enabled specifically when loaded in Engine COMP.

I am using Google Drive Desktop to store this project. I know that that has caused some issues for .toe vs #.toe files. It appears that this might be the core issue as I located it inside of my Desktop for a test and it didn’t cause this issue. Wonder if this is a truncation error.

Current version experiencing the issue: 2025.32050 - Windows 11 Home - Alienware M18 R2

Temporary solution: The only way I was able to get them enabled was to make my project folder “Available Offline.” I bet that Google Drive <> TD connection isn’t pulling the entire file but instead is pulling the proxy file.

Hi @Matterform - if this is a Google Drive issue, there may not be much we can do - it would need a fix to Google Drive. We’ll see if we can recreate the issue anyway.