The symptom:
When working in an ACC model with point clouds linked from ACC, the point clouds wouldn’t load for me, only for others. When I used Reload From… in ACC (with the same path as everyone else), I could load the point clouds, but then other users couldn’t. So it was either only me or only the others, but never both.
After several hours of Googling and reinstalling, the main clue was that the point cloud path contained an extra directory level /.../ before others' path.
The difference between my setup and everyone else’s was is Revit → Options → File Locations → Point Cloud path settings:
Mine:
C:\Users\User\<company name drive>\Documents\PointClouds
Others:
C:\Users\User\Documents\PointClouds
It turned out that OneDrive’s backup/sync of the Documents folder was the root cause.
Revit uses that folder for something, and the OneDrive redirection adds an extra path layer, which breaks linked paths.
Workaround:
Don’t use OneDrive’s automatic backup for your Desktop/Documents folders.
Alternatively, you can set Revit’s point cloud location to the default local path (C:\Users\User\Documents\PointClouds), even if it doesn’t actually exist in the filesystem.
It looks like that’s enough to prevent the conflict.
