Workspace converted from Rm1. All tracks are on network drive with assigned letter (names in db with letter, not with network path). No one can be opened, got error can't locate. But opens ok after manual location at the same place. It' annoying to locate each track.
And about generated .idx - what if I want to store all tracks on readonly drive? How will sonar viewer handle such case? Now I see that it generates indexes in original location.

It was unable to locate tracks in the same location? I will look into that, but it shouldn't happen - thanks for the feedback. You are saying that this is a mapped network drive? We are looking into a solution to allow "bulk relocation" of tracks (i.e. RM will search from a new root location and try to match up existing tracks with files on disk). This would make it easier to move workspaces between computers etc.

Yes, IDX files are now created for each file - the location must be writeable. Although I know this might be annoying for some (the files are quite large, as they contain sonar imagery and indexing info), there are also big benefits - e.g. sharing corrected files across workspaces, no need to reimport files to other workspaces once the IDX files have been generated once and, most of all, far better performance when reading sonar data so that we can now do things like show SS mosaic at all zoom levels.

Yes, the same location on mapped network drive.

Just wanted to add a "plus one" to the idea of a bulk relocation option...I'm spending my morning opening dozens of files because I had to move my data folder for a large project. Nice that it does not break Reefmaster when I do this (it knows to ask me for a new location), but given the parent folder is all that changed it would be great to be able to just specify a new folder and have Reefmaster locate all the files in the nested folders.