If you have a Tabletop Simulator save you’d like to move over to TTP, you can get a head start on that using the built-in Tabletop Simulator Importer tool. Be aware that this tool is still a work in progress, and has a variety of limitations, but for some projects it may prove to be a time saver. 

To start, go to Editor mode and create a new package. Once you’re on the table, open the top menu and select “Import TTS Package.” This will open a file selection window, showing you the contents of your TTS “Workshop” folder (where TTS keeps material you’ve downloaded from Steam Workshop).  If you would like to instead import one of your personal saves, navigate up two levels, and you should see a “Saves” folder, which is where those are stored. Either way, click the JSON file you want, and hit Import.

The Importer tool will pull in all the objects it can from TTS, and attempt to array them on the table as they appear in the TTS save.

It will also create Templates for all of these objects in the Object Library. Since this can sometimes result in a large number of templates, it will attempt to organize them by putting them in folders based on their names. If an object has no name defined in TTS, the importer will assign it a name based on its type and file it accordingly.

There are a few limitations and known issues to be aware of:

• Scripts will not be imported (TTP uses Javascript rather than Lua), meaning anything that relies on a script for placement will not be placed properly.
• The import process can sometimes cause TTP to crash, especially on lower-spec machines, or if the textures in the mod you’re importing are especially large. If you experience a crash, you can try the following:
  • Open Settings. In the Video tab you’ll find a “Texture Compression” option. Set it to “Compressed” or “Half Resolution.”
  • If this doesn’t fix the problem, try splitting the TTS mod in half, and importing each half into TTP separately.
• Some TTS mods use .rawm files for custom 3D objects; these are not yet supported in TTP and will fail to import.
• Due to the different texture mapping each program uses for dice, custom dice that are not D6 will not import their textures.
• The importer constructs decks based on which cards wind up stacked on top of each other on the table, and hence may be unaware of connections between cards that would have been present in TTS.