Small project, runs smooth but one DAT is causing long save times

Hi all,

I’m using TD to playback positional data from a simulation - a Text DAT operator loads a large JSON file of ca. 150 KB. There are currently ca. 33,000 objects of which I retrieve coordinate data from each frame.

Using the Text DAT to load the JSON into TD seems to run smoothly when it is set to Bypass mode - I use JSON operators with path filters to retrieve the items I need depending on the frame. (side question… This works for now, however, I think my file might grow much larger. If anybody thinks there’s a better way please let me know :slight_smile:

I don’t know how to cut down my save times though. It takes a while to save the file now, which has me concerned when the dataset grows larger. Is there something I can do to stop the TextDAT interfering with the save? Sync to File, Load on Start and Write on Toe Save are all set to off.

I can’t upload the file here because it is too large. Perhaps there is something I need to learn about how TD is caching all this DAT info to keep the filesize down? Here is a link to the files from my drive: https://drive.google.com/drive/folders/1bcLvlFlE7aFsJ85NajxWZvBZGH6cOI4E?usp=sharing

I think you want sync to file on? That way it saves the text dat to a json file rather than in the toe

I just tried this and it doesn’t change the file size or the lag while saving. My solution for now is to .clear() the Text DAT before I save the file.