[dforrest]

dforrest, on 02 June 2015 - 02:21 PM, said:

I see in a post from James on 22 May that version 1.0 was replaced by 1.0.1. From the time installed, I installed 1.0 not 1.0.1. Would this have caused a problem with the documentation?

If so, can I now install 1.0.1 over 1.0 without causing any problems?

With a re-install of v 1.0.1 over my v 1.0, I now have a Documentation folder.

[markus_GE]

IIRC, there have been problems with the automated packing process, which "forgot" to pack the documentation into V1.0. James might know more, however.

Cheers, Markus

[CrisGer]

thanks James and copperpen much appreciate the info great help here I think I understand now what to do. thanks all. thank you for your data Lindsay that was a big help as well.

[R H Steele]

Lindsayts, on 02 June 2015 - 11:58 AM, said:

For each separate route/section you wish create a directory...

...Below each of these create the directories TRAINS, ROUTES, GLOBAL and SOUND
so you end up with the durectory structure
Lindsay

Am I correct in stating that you could use 1 master folder each of SOUND and GLOBAL and use junction points for the whole setup? So the contents of those specific folders need not be duplicated thorughout.

[Lindsayts]

R H Steele, on 03 June 2015 - 11:12 AM, said:

Am I correct in stating that you could use 1 master folder each of SOUND and GLOBAL and use junction points for the whole setup? So the contents of those specific folders need not be duplicated thorughout.

Probably, I have not tried that though as I am not crowded for disk space on my windows partitions as I ONLY use windows for train siming,. Even then MSTS's editior and tools is run under Linux using wine it being considerable more reliable than with windows.

I do not know if it would be worth it, doing a "du" (disk used, it scans the disk and tells one how much space is used) on my broad gauge Australian directory for OR shows the following...

GLOBAL         232M
ROUTES        20G
TRAINS          3.2G
SOUND          60M

So GLOBAL and SOUND are taking up not that much space.


Lindsay

This post has been edited by Lindsayts: 03 June 2015 - 11:51 AM

[CrisGer]

I like that system and it will help me instruct our testers how to set up their OR install of our route so they can operate it with OR alone. Because we are doing advanced modeling and using very advanced stock and engines, custom sounds and other environmental advances...OR will be the only way our route will run. We hope to make it a showplace and example of how good OR works and looks....which will of course take the same kind of time and long term commitment as is being thankfully given to OR itself

thanks again for the kindness shown here in helping me. :pardon:

:rolleyes:

[James Ross]

dforrest, on 02 June 2015 - 02:21 PM, said:

I see in a post from James on 22 May that version 1.0 was replaced by 1.0.1. From the time installed, I installed 1.0 not 1.0.1. Would this have caused a problem with the documentation?

If so, can I now install 1.0.1 over 1.0 without causing any problems?

I don't know how you ended up in the situation you did, since the only difference between the 1.0 and 1.0.1 installer is the contents of the documentation folder, not its existence or any of the shortcuts, but installing 1.0.1 over 1.0 is fine and gives the installer a chance to fix whatever's gone wrong.

[dforrest]

James, I have now seen that when I do an "unstable" update, the Documentation folder is deleted. Is this the expected behavior?

[James Ross]

dforrest, on 04 June 2015 - 02:48 AM, said:

James, I have now seen that when I do an "unstable" update, the Documentation folder is deleted. Is this the expected behavior?

Yup. Only Stable and Testing builds have documentation included; Unstable builds are far too frequent and numerous to sensibly include it (and it'll be way more likely to be out of date here).

[copperpen]

That is why I now have two OR installs, V1 stable release, never updated, and one that receives updates.