lockheed02
Member
Perhaps someone could enlighten me about the current Route - Session concept.
When you created a session on someone else's route (e.g. from DLS or DLC), you simply got into the route, hit "Create Session", did your session settings and simply saved. Your session used to be bound to the route by default (provided you not messed with anything of the route itself).
In some cases you've got prompted when saving your new session, if you would like to save route and session, and you simply selected the "Only session" option and things were fine too.
Now in RC build I've got a route from someone and when I try to make a session on is route, I just "Create Session" - "Edit session" in Surveyor and give the session a nice name. When I want to save/save as, I am prompted with a nice pop up but the only option that is valid is "Save route and session". In effect, I have a clone of the route with my session bound to it. Unless I cheat and change the map kuid of my session I cannot create sessions for that route.
As route building is not my expertise, if this is not a bug, I suspect this is a kind of protection mechanism/feature? How is it set up? I might have missed some documentation about a new authorization concept ...
Thanks for any clarification
When you created a session on someone else's route (e.g. from DLS or DLC), you simply got into the route, hit "Create Session", did your session settings and simply saved. Your session used to be bound to the route by default (provided you not messed with anything of the route itself).
In some cases you've got prompted when saving your new session, if you would like to save route and session, and you simply selected the "Only session" option and things were fine too.
Now in RC build I've got a route from someone and when I try to make a session on is route, I just "Create Session" - "Edit session" in Surveyor and give the session a nice name. When I want to save/save as, I am prompted with a nice pop up but the only option that is valid is "Save route and session". In effect, I have a clone of the route with my session bound to it. Unless I cheat and change the map kuid of my session I cannot create sessions for that route.
As route building is not my expertise, if this is not a bug, I suspect this is a kind of protection mechanism/feature? How is it set up? I might have missed some documentation about a new authorization concept ...
Thanks for any clarification
Lockheed