Voxel Link (VL) creates a couple of VL-specific files in the normal course of operation. Write access to each of these locations is required but typical environment configurations should already have write access to these directories.

  • An authentication token file (tokens.json) is saved to %LOCALAPPDATA%\VoxelLink (typically C:\Users\<username>\AppData\Local\VoxelLink) when the user first authenticates and runs Voxel Link. That token file is read each time VL starts so the user can be validated for that desktop. If VL is run every 30 days, the user will not have to enter their email and password (unless their account status has changed).

    This folder is typically writable however, some environments may have limited access to the %LOCALAPPDATA% folder. A warning is provided if the folder is not accessible but VL will continue to run if a valid email and password are provided. Although access to this directory is not required, it is an inconvenience to authenticate with your email and password every time you run VL. You may want to check with your IT folks about allowing access to the %LOCALAPPDATA%\VoxelLink folder.

  • Each RAM model that is imported into a Revit model has a:
     - settings file (<RAMModelName>_Settings.vlcfg) and a
     - map file (<RAMModelName>_Map.vlcfg).
    Both files are saved in the same folder with the RAM model and are required to accurately track imports and changes in the RAM design. The files cannot be viewed or edited manually.

  • Each Revit model has a file (<RevitModelName>_Models.vlcfg) that manages the RAM models associated with that Revit model. It is stored in the same folder as the Revit model, EXCEPT if the model is stored in the cloud. In that case, the file is stored in %LOCALAPPDATA%\Roaming\VoxelLink or %LOCALAPPDATA%\Local\VoxelLink or Windows Temp, in that order. The file name for the cloud vlcfg is <RevitModelName>__<projectGuid>__<modelGuid>_Models.vlcfg to eliminate model name clashs for cloud files.