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.
Download from https://syncthing.net or install via your OS package manager.
Run Syncthing once to generate a unique Device ID and initial configuration.
Open the web GUI at http://127.0.0.1:8384.
The primary machine will initially hold the master copy of your resources folder.
On the primary machine:
In Syncthing, click Add Folder.
Folder Path: point to your resources folder. Example:
C:\Users\<username>\Documents\Sightlab2\Projects\SampleProject\Resources
Folder ID: use something simple like resources.
Folder Label: optional display name.
Click Save.
Open Syncthing’s web GUI (http://127.0.0.1:8384).
Go to Actions → Show ID.
Copy the long Device ID string (or scan the QR code if adding from another device).
In Syncthing, click Add Remote Device (bottom right)
Paste the client’s Device ID.
Name: give the device a clear name (e.g., VRClient1).
(Optional) Tick Introducer to have the primary automatically connect new devices to each other.
Click Save.
On the client, accept the connection request from the primary:
"Device PrimaryMachineName wants to connect."
Click Add Device, give it a name, then Save.
Once both sides have accepted, the devices are paired and ready to share folders.
Find the resources folder in Syncthing’s folder list.
If you didn’t add it earlier, repeat Step 2 above.
Click the Edit (pencil) icon next to it.
Go to the Sharing tab and tick all the client devices that should receive this folder.
Click Save.
Accept the folder share request from the primary:
“Device PrimaryMachine wants to share folder resources.”
Click Add.
Choose the Folder Path where the synced copy should live.
This path should match what your SightLab scripts expect, e.g.:
C:\Users\<username>\Documents\Sightlab2\Projects\SampleProject\Resources
Click Save.
Syncthing will automatically keep the resources folder in sync between the primary and all clients.
Any file added, edited, or deleted in the folder on one machine will be reflected on all others.
If clients also have write access enabled, changes flow in both directions.
Go to Actions → Settings → Connections
Disable Global Discovery and NAT Traversal.
Keep Local Discovery enabled (fastest inside a LAN).
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
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.
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.
See here for more information https://docs.syncthing.net/v2.0.0/users/foldertypes
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.