How to Synchronize Multi-User Assets in SightLab VR Pro with Syncthing
September 3, 2025
This guide explains how to synchronize your multi-user resources folder across all machines using Syncthing. Syncthing works both online and offline over a local LAN. This will also work to synchronize over separate networks if using Radmin.
This can now work with all Multi-User features of SightLab including examples such as the VR Presentation Tool, Multi-User Eye Tracking Experiments, Visual Search and more.
How to Ignore Sub Folders
To ignore sub-folders, in the web interface click Edit on the Shared Folder, then go to "Ignore Patterns". In the field enter the name of the folder with a forward slash (i.e. sightlab_configs/)
Important notes:
Use forward slashes (/) even though it's a Windows path
Don't include the drive letter or the synced folder's full path
End with / to indicate it's a directory
The path is relative to whatever folder you've set up for syncing in Syncthing
Troubleshooting
GUI Not Opening in Browser
If GUI not opening in browser (note this opens in a browser even if offline in LAN mode)
Sometimes the GUI won’t auto-open, so try manually in your browser: http://127.0.0.1:8384/
If that still won’t load, something (firewall, antivirus, browser plugin) is blocking localhost connections.
Extra Files Being Added with Conflicts
Sometimes *.sync-conflict-YYYYMMDD-HHMMSS-<DeviceID>.osgb files are created by Syncthing whenever two devices modified the same file before syncing.
The original file (e.g. Business_Office.OSGB) is still there.
The *.sync-conflict… copy is Syncthing’s way of making sure you don’t lose either version.
Safe cleanup options:
If you know which version is correct → open the files in Vizard/SightLab, confirm the “real” one, then delete the conflict files.
If you don’t need the alternate copy → it’s safe to delete the *.sync-conflict* files and keep only the base ones.
If you’re not sure → you can archive the conflicts somewhere else (e.g. a conflicts/ subfolder) before deleting, just in case.
How to prevent future conflicts:
Try to designate one “writer” machine (e.g. your primary/host) and keep others read-only if possible.
In Syncthing, you can set the folder type on clients to Receive Only if you don’t want them to push changes back.
If you need true two-way sync, conflicts can still happen, but they’ll be rare if only one person edits at a time.
✅ Bottom line: The .sync-conflict… files are not required for SightLab or Vizard to run — they are just duplicates for safety. Once you’ve confirmed you don’t need them, it’s safe to delete them.
For more information see this page in the SightLab documentation. To request a demo of SightLab VR Pro click here.