Announcement

Collapse
No announcement yet.

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

Collapse
X
Collapse
First Prev Next Last
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • marklester01
    replied
    Well, Thanks for everyone's help! Turns out it was a mixture of both. Also Turns out also I seem to've missed a few Throttle-Air Stream-Strings that weren't present in the "Match-up". Plus, some Audio wasn't set-correctly( although it should've worked because ORTS can now read Stereo on The Outside as well too ?). Well, I just re-copied, re-named from a few things, & It's helped! Plus, I've got "Total" V.2+( Not sure Of Derek's actual Number Combined with some of Bob's Help on there ) ORTS Physics to Works! This was thanks to a Visual Template I needed.\ done by other Members.
    Last edited by marklester01; 02-26-2024, 10:38 PM.

    Leave a comment:


  • marklester01
    replied
    Updated Again, & FINAL Good Progress Made on FINAL Reply Below.
    Last edited by marklester01; 02-25-2024, 01:18 AM.

    Leave a comment:


  • marklester01
    replied
    Problem Solved! See LAST Reply. Pre-Thanks to All.*
    Last edited by marklester01; 02-25-2024, 01:31 AM.

    Leave a comment:


  • slipperman
    replied
    Hi Mark,
    If you're using .sms files from a different soundset, then you need to ensure that all the required .wav files are in the locations indicated by their .sms file entries - you can't use only the .sms file/s (unless you're extremely lucky!!).

    You should also ensure that each of your 'new' .sms files is error free, ONLY THEN you can start thinking about changing supplementary parameters, but bear in mind that many soundsets were created for use with MSTS and the .wav files may not play correctly if a higher frequency is specified.

    Cheers,
    Ged
    .

    Leave a comment:


  • marklester01
    replied
    Problem Solved! See LAST Reply. Pre-Thanks to All.*
    Last edited by marklester01; 02-25-2024, 01:31 AM.

    Leave a comment:


  • slipperman
    replied
    Hi Mark,
    One of the attractions of MSTS/ORTS is that contents of .sms files can be mixed and matched, BUT it's very important that you know exactly how all the lines of the file should be formatted and their interrelationship.
    You can use my sms_Checker to validate the file/s you're creating - just point the program at the folder containing the .sms file/s. If .wav files are reported as 'not found' it'll be either because the file doesn't exist in the same folder as the .sms file (if aliasing is not used) or it's not in the aliased folder

    sms_Checker is available from the file library as file ID 87505 (file name :- sms_checker_v5-1.zip)
    If you're using MSTS, single back-slashes ( \ ) are not permitted in aliased entries; I'm not certain if Open Rails allows these, but this program currently reports them as 'invalid'.

    It's a pity that the Steam4Me site is not currently available because it had a good tutorial on the construction/format of .sms files

    Cheers,
    Ged


    Leave a comment:


  • marklester01
    replied
    Problem Solved! See LAST Reply. Pre-Thanks to All.*
    Last edited by marklester01; 02-25-2024, 01:30 AM.

    Leave a comment:


  • marklester01
    replied
    Problem Solved! See LAST Reply. Pre-Thanks to All.*
    Last edited by marklester01; 02-25-2024, 01:30 AM.

    Leave a comment:


  • derekmorton
    replied
    Eng file:-

    I have never seen an eng file with both the old MSTS lines and the TS lines together, asking for trouble.

    sms files:-

    You have a mixture of alias and non alias entries, more trouble coming here.

    Leave a comment:


  • marklester01
    replied
    Problem Solved! See LAST Reply. Pre-Thanks to All.*
    Attached Files
    Last edited by marklester01; 02-25-2024, 01:29 AM.

    Leave a comment:


  • marklester01
    replied
    Problem Solved! See LAST Reply. Pre-Thanks to All.*
    Last edited by marklester01; 02-25-2024, 01:29 AM.

    Leave a comment:


  • R. Steele
    replied
    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
    This may have been previously reported. If so, my apologies. I do think it's important. Learning about the include files, reading the threads,...


    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.​
    Last edited by R. Steele; 02-22-2024, 11:39 PM.

    Leave a comment:


  • oper190
    replied
    Originally posted by marklester01 View Post
    "..\\..\\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 )

    Leave a comment:


  • marklester01
    replied
    Problem Solved! See LAST Reply. Pre-Thanks to All.*
    Last edited by marklester01; 02-25-2024, 01:29 AM.

    Leave a comment:


  • marklester01
    replied
    Problem Solved! See LAST Reply. Pre-Thanks to All.*
    Last edited by marklester01; 02-25-2024, 01:28 AM.

    Leave a comment:

Working...
X