FBX Camera Track causes patch to never open up again

POPs
1

Hi, been working on a gaussian splat project where I’ve imported in a FBX camera because need specific camera movements. If I close the file I’m working on I can never open it up again, I think it’s the FBX imported component because if I change the import scale and click import again while the internal camera is referenced to a render TOP it will also crash the system.

Attaching the crash file, let me know if I should also upload the full project folder to test on your systems as well.

Version: 32374
System: MBP M3 Max

TouchDesigner-2025-04-24-235631.ips.zip (20.4 KB)

2

image
image1098×626 101 KB

Put a onExit() script to kill cooking on the FBX component that didn’t fix the issue either

3

Okay, tried with the stable release and I get the same error and the files can’t be opening up again. Not an alpha release issue, just a general issue

4

Hello @aaronmylespereira
Thank you for reporting the problem. Could you please upload the full project? It would greatly help us in pinpointing the issue.

5

Hi, uploading a zip with all the assets here.

I’ve stopped the cooking for the container with the fbx, you’ll can check if allowing cook on the main container bricks the machine, if it does, reopen it, go inside, delete the fbx, reimport the camera track fbx, set import scale to 0.1, go inside, set the null camera scale to 1, and then refer the render to ‘Camera_convertedtoTD’ and it should work again.

On a MBP M3 Max with stable version 12230, but get the same error when using the POPs GS version rendering all toe files with the containers left cooking to never open up again and crash the system.

6

There doesn’t appear to be an issue with the FBX model import. Instead, the problem seems to occur in the Gaussian splat shader when a scale factor is applied to the camera. To resolve this, you can either ensure that no scaling is applied to the camera or modify the shader to account for any scaling on the camera.

7

Thanks got it, yeah suspected it was the camera scaling, our workaround for now is to always make sure the scaling is set to 1, or just not having the imported camera in while allowing the cook.