Stuck In/On Notch8 @ The Start With Silent Cab?

[marklester01]

Problem Solved! See LAST Reply. Pre-Thanks to All.*

[derekmorton]

The OR log will lead you to the missing files or typo's.

[slipperman]

Hi Mark,

I used The .sms Checker. All good( except where it says the alias lines: "..\\..\\folder\\.. )

The alias lines are very important so can you please give more details?

As Derek pointed out, the OR log will also point to any aliasing errors.

Cheers,
Ged

[marklester01]

Problem Solved! See LAST Reply. Pre-Thanks to All.*

[slipperman]

Hi Mark,
Without seeing the actual .sms files and/or the OR log and knowing where the aliased files are located, there's not much we can do to help.

If you wish to know more about aliasing, I included a short document on the subject with the readme for my MSTS_Check utility, which might help
MSTS_Check will also show errors in aliasing sounds and cabviews; It may be downloaded from this site's file library as file ID 85979 (msts_check.zip).

Cheers,
Ged

[derekmorton]

could The Cabview be Wrong?

Most unlikely, other people are using it.

[R. Steele]

I went to test a CSXT SD70AC

Please be more specific, so other members can download or find the exact same piece of equipment to check it....Which CSXT SD70AC???

[marklester01]

I didn't use the correct words,lol. I meant, could I've installed it wrong?*

[marklester01]

Problem Solved! See LAST Reply. Pre-Thanks to All.*

[marklester01]

Problem Solved! See LAST Reply. Pre-Thanks to All.*

[marklester01]

Problem Solved! See LAST Reply. Pre-Thanks to All.*

[oper190]

"..\\..\\Common.Snd\\MLW_Horns\\x_K5LA-R24_HP.wav" -1 ),

I see a problem with this line back slashes should be "//". Here is a line from an alias sound file I know works : File ( "../../Dash9/sound/x_d9_power_cruise3.wav" -1 )

[R. Steele]

I don't think it matters, as long as you are consistent in your method. I've been using double back slashes for years, in all sorts of alias paths, sms files and cvf file. Others use single forward slash, that also works.


One of the best explanations I have read of paths is this post by Jovet at Elvas Tower: especially posts # 6 & 14
http://www.elvastower.com/forums/ind...in-the-manual/

An absolute file path starts from a "fixed" point, such a drive mount or a machine\share name:
C:\MSTS\Open Rails\OpenRails.exe
or
K:\Users\Default\AppData\Local\Microsoft\Key.dat
or a network path:
\\BACKUP\BK_STA0\STD\20150703\MSTS\Open Rails\OpenRails.exe

An absolute file path is completely independent of the current folder. It doesn't matter what folder your program is looking at right now, because the absolute path overrides that.

A relative file path is dependent on the current path your program is looking at right now, and is relative to that path (hence the name).

The simplest relative file path is just the filename:
OpenRails.exe

This is relative to the current folder your program is looking at. It is also the same as this:
.\OpenRails.exe

The folder "." is a special relative folder name that always refers to the current folder. Because it's often redundant and unnecessarily verbose, it's seldom used and rarely seen. Again, remember those two previous examples are exactly the same.

If there is a folder in the current folder with the file then you could do something like this:
Open Rails\OpenRails.exe
If whatever program is looking at C:\MSTS (per the above examples), then the OpenRails.exe file could be found by specifying the path "Open Rails\" - again it's relative to the current folder. If you add the current folder and the relative path together you get C:\MSTS\Open Rails\OpenRails.exe.

The next special folder name we've all seen is ".." and it always refers to the parent folder (if there is one).

Let's say we have our fancy Open Rails include file for a route, located at: C:\MSTS\Routes\MyRoute\OpenRails\BestRouteEver.trk

The reason this file contains the line include ( "..\\BestRouteEver.trk" ) is because it's invoking all of the contents of the route's main .trk file that exists in the route's main folder, which is the parent folder of the OpenRails folder. Open Rails sees the file in the OpenRails folder and ignores the main one, but upon reading the OR one, OR sees that it specifically includes the contents of the main one. This allows you to maintain settings for both MSTS and OR but not have to change two files constantly, which is a good thing.

Relative paths can be as long or complicated as you wish.
..\..\..\MSTS3\Routes\SOUND\goodsound.wav
could actually refer to a file in another MSTS installation by navigating up three folders and then down into another folder tree.

Lastly, when a relative path starts with a backslash, it always refers to the root folder of that storage drive (its mount point):
\MSTS\Open Rails\OpenRails.exe
The file would be found if the current path the program is looking at is on the C: drive (per above examples) but would fail if it was, say, the D: drive.

So the trick with relative paths (and include files) is to know where your target file is relative to the current file, and be able to spell out the relative path accordingly.

[marklester01]

Problem Solved! See LAST Reply. Pre-Thanks to All.*

[marklester01]

Problem Solved! See LAST Reply. Pre-Thanks to All.*