First time install of WP3 has no track or roadbed??

[slipperman]

Hi lvlender,
Very simply, I created an empty folder named WP Feather River and ran the Feather River installer, WP_Setup.exe
When asked for the installation folder, I browsed to the one I'd just created. The installer added folders GLOBAL, ROUTES, SOUND and TRAINS.
Apologies if you already know how to make the route available to Open Rails, but if not, I went to the <Options> <Content> tab then pressed <Add> and navigated to the folder I had created then pressed <OK>..

Cheers,
Ged

EDIT : Sorry, Kasik - you posted while I was composing!!

[eric]

Ah.... I installed it to its own folder at first to see what would happen with the tsection, and then copied/pasted the route and trains folder over my main collection.

I'm guessing the clobbered skydome would have stayed in the standalone folder.

[lvlender]

Create a folder and install WP3 to it. In Open rails options add this folder in Content tab. After that you can choose WP3 from list in the main window in OR

Hi Kasik,

Per your instructions I created a new folder in my OR .../trainsimulations directory and named it Feather River Route.

I ran the WP3 installer, directing the installer to set up WP3 in the new...

D/trainsimulations/Feather River Route folder.

I then started the Open Rails main screen and selected, Options/Content and selected ADD NEW, to add D/trainsimulations/Feather River Route as a clickable selection in Open Rails.

It worked! Thanks for your post which allowed me to figure this out.

Edit: and thanks to all who posted and showed an interest 🤗

[geepster775]

The newer TrainSimulations routes that generally are found in the TrainSimulations OR installation use ScaleRail shapes in the global folder that call upon DDS textures.

If you have Mullan Pass or Shasta routes in the same installation folder you placed WP3 in, run them now and see if the tracks are still showing, or whether your WP3 installation overwrote those global files with older ScaleRail files that call upon ACE textures.

This is why they say the OR-grade routes from TrainSimulations needs it own segregated installation (I.E. do not mix with MSTS-grade routes) or that older MSTS-grade routes with ScaleRail cannot mix or mingle in the same installation with the new stuff. Hence the suggestion to keep treating the WP3 as a mini-route even in the OR setting.

[lvlender]

Hi geepster,

now that I know MSTS and OR designed routes don't play well, should I delete my MSTS routes and reinstall each as stand alone folders like the WP3 route? Here is a list of route I have installed in a common OR routes directory...

• ORTS 1974 Amtrak Empire Builder #8 Date 2023-04-08

1. Milw Road-Coast Division – 2nd Sub - Seattle, WA - Cle Elum, WA
2. Milw Road-Coast Division – 1st Sub - Cle Elum, WA - Pomona, WA

• Maple Leaf Tracks MLTP05 Cascades Crossing Willamette Pass (Date?)

• MSTS Monon-2 ver.17 Route Date 2014-05-08

• MSTS Norfolk Southern (Horseshoe Curve) Route Date 2011-06-17

• ORTS SoCal Route Date 2023-06-08

• MSTS RMD West (Hiawatha) Route 2016-07-06

1. Rocky Mountain Div. East
2. Rocky Mountain West Route

• MSTS Surfliner 2.20 Date 2017-07-19

• ORTS TrainSimulations BNSF Seligman Route (Date?)

[oper190]

I have grouped mine in folders togethers like in MSTS, and only made Folders set for OR for my own convenance for segregation. (RE: ACleanTrack, vs USTrack / Need Signal Glow or not, and all my European Routes and Train Sets in a separate Folder ) All are working fine. Scale Rail will need it's own folder ( don't have any Routes using it ) and any using .dds textures in Goble as well. I am guessing that if you had both .ace and .dds textures in the same Goble, Routes needing .ace should then work.

[geepster775]

Most people who installed MSTS on newer PCs by following the tutorial that was on Steam4Me likely have a "1MSTS" folder that all their MSTS routes (with the exception of routes that needed a Mini-route segregation in the MSTS days) can go into and they generally play well together.

If you purchase OR grade routes from TrainSimulations, the installer most often forces users to go with a "TrainSimulations" installation folder name. So, no, MSTS routes like WP3 should generally go elsewhere than into the TrainSimulations folder.

Inside open rails, under the content tab, you generally select "1MSTS" folder for your MSTS goodies and "TrainSimulations" folder for the newer made-for-OR content. The longer you stick around and learn and get the hang of things, you may decide to divide things up differently. By then you will know all the required dependencies.

You shouldn't have to delete anything, just move the routes around among installation folders. The Feather River possibly should be segregated (I called my installation "UP_Canyon", for the 3DTrains Feather River and "UP_Sherman" for the 3DTrains Sherman Hill route). Changes in ScaleRail and ScaleRoads packages, which impacts the Global folder, means these two routes from 3DTrains cannot share a common installation folder without one clobbering the other when installed together.

The ORTS Seligman route/Scenic Starter/Ruel/Shasta and Mullan should definitely be in the TrainSimulations folder. Being newer, they can all share the same Global folder that call upon DDS textures.

[oper190]

Not sure how this plays out: I have the latest TS Starter Route, installed in my OR-TS folder and so far the only Route of theirs's I have. All the textures in the Goble are .ace, the .dds are in the Route Texture Files. So why won't other Routes work if put in the same folder set? It seems to be using the new AcleanTrack profile. Just asking, I have it segregated.

[crstagg]

.............

.................. Changes in ScaleRail and ScaleRoads packages, which impacts the Global folder, means these two routes from 3DTrains cannot share a common installation folder without one clobbering the other when installed together.

..............

I disagree. I have both WP3 and Sherman Hill installed in the same mini-install. I also have both installed in my 1MSTS full install with 99 other MSTS routes. They work fine together and with other routes. But I DO NOT mix them with TrainSimulations routes for OR.

I was a Beta tester for the Feather River Route. One of the tasks while beta testing was to create a 'fresh" install of MSTS with no routes installed then install WP3 to that folder and test. It worked fine.

Later when early releases of ORTS became available; I created a folder structure with the root folder named WP3-Raw. NO MSTS files installed just the folder structure. I then ran the WP3 installer pointed at the WP3-Raw folder. Added WP3-Raw to my ORTS content tab. WP3 ran fine but, with only one noticeable problem: The diesel exhaust was square shaped. Added dieselsmoke.ace to the Global\Textures folder and that solved that problem.

Later when Sherman Hill was first released, I created an ORTS install named SH-ORTS and pointed the Sherman Hill install to that folder and installed it. Found it needed the Dieselsmoke.ace in Global\Textures also. Then I pointed the Sherman Hill installer at the WP3-Raw folder and installed it there with the Feather River Route. Both work fine together using ORTS. Later I created a third install of Sherman Hill in my main MSTS install. Runs fine there also.

FYI current system OS is Win 11 i7 11th gen CPU 16GB Nvida GeForce 3060 1GB.

BUT YES you do have too run ScaleRail routes with Super Elevation set to zero. Unless you have a super Elevation profile written for the route. As in this file: ScaleRail Dynamic Track Profile File ID 88545

[geepster775]

You may need to re-check, Charles. Brand new installation with just the two 3DT routes. Feather river installed first, then Sherman Hill. I've posted screens showing this before on here.

Remember that some of these Sherman updates introduced version 2 of the ScaleRail/Roads packages.

I don't have a problem with updating global files to finally eliminate some shortcomings in hard-to-change past 'cemented practices', but once you commit to it, you pretty much sever backwards compatibility with older routes and you need to segregate going forward.


Feather River 1.06 File: 3DTrains_WP3_Setup_080412


Sloat





Downtown Oroville





After adding Sherman Hill to the same installation.

Main route package: 3DTrains_Sherman_Hill_Beta_060217

Latest cumulative update: 3DTrains_Sherman_Hill_Beta_Update_050418


Sloat




Oroville

[eric]

I've been careful not to use the Sherman Global directory because of those inconsistencies.

Sent from my SM-S911U using Tapatalk

[crstagg]

Kevin,

I had not noticed that. Probably because I spend more time in ORTS being a loco engineer than a drone pilot.

[R. Steele]

I spend more time in ORTS being a loco engineer than a drone pilot

Just the opposite for me...spend more time in a drone following above the train. Wish OR had a configurable "Drone" camera.

[pschlik]

I got stupid news, ironic news, and good news.

The stupid news: This issue with grey textures was fixed 5 years ago and was subsequently broken so soon afterward it seems nobody realized it was ever fixed.

The ironic news: The thing that broke the fix was the addition of an error message. Yes, an error message can not only inform you when something is broken but can also break things itself!

The good news: A fix for the fix is headed to the unstable version, so no more broken track textures when you mix TS routes with MSTS routes. It's a tiny change, so it should show up in the testing version pretty quick, then the next stable release (Soon TM) for those of you not adventurous enough to enter the realm of untested code.

[R. Steele]

Thank goodness, was aware of the coding kerfuffle ---- brilliant Phillip.