Railworks America

I have been working in a couple QD scenarios for the NERW Lafayette in Indiana, which I attach to this post. Any comments about them will be welcome right in this thread.

The following description is a copy of the README included with the attached file:

"The folder included in the zip has the first release version for two QD scenarios, one westbound, the other eastbound, for the NERW Lafayette (Indiana) route, released recently in RWA by Bob Artim and his team.

To install drop the zip contents into Railworks folder. It will install in the scenarios folder of the Lafayette route.

The QD include only player spawn points, nearly 60, with 30 startup points. All spawn points are numbered, lower in the east (Tipton) and higher in the west (Lafayette). Only a few routings are touching exclusively passenger stations, but most of them are freight oriented from/to yards or sidings.

You have to consider that in many cases you will need to throw some yard or sidings manual switches in order to be able to reach your destinations or even avoiding derailments (due to switches set against your path).

I haven´t been able to decorate the QD routings with consists. I tried both, consist and AI spawn points, getting weird results. I also tried placing consists added along the route. Those when increased in numbers produced continuous crashes, making the QD fully unstable.

Even so, I will keep trying to get this part done. I still have a few ideas. Particularly I would appreciate any advising from more experienced members in RWA concerning this part.

For the moment this file is released attached to this thread. Bob and Buzz will decide in the future if they (or updated versions) are to be released along a next route update or any other way."

jalsina wrote:I have been working in a couple QD scenarios for the NERW Lafayette in Indiana, which I attach to this post. Any comments about them will be welcome right in this thread.
\

Great work! I'm a little slow responding due to YET another reinstall, but what an excellent list of spawn points. If I can find some time this week, I will mess with static consists for the yards and possibly some simple AI. That will be a challenge with so much single track, but I know it can be done in theory.

Thanks!

Overshoe wrote:Great work! I'm a little slow responding due to YET another reinstall, but what an excellent list of spawn points. If I can find some time this week, I will mess with static consists for the yards and possibly some simple AI. That will be a challenge with so much single track, but I know it can be done in theory.

Thanks!

Thanks Tom.

The Preload has only 2 trains, the Monon and a CSX Tropicana train
I have started today with some testing to place consist spawn point and they are working nicely.
What I am doing now is starting to make pure freight cars fragments (and the bin to run them) plus train consists. My intention is populating the Preload folder with additional trains and fragments, mostly using rolling stock included with the route.

The problem you might have is the fact there are nearly 60 destination points and you can´t place consists in those places or paths to it.

The following shot is a Sherman Hill train which I have modified (after the shot) to have a NS ES44AC pair of locos in the lead (and a UP SD70M).



I know this will be a bunch of work but I would like to get something more complex than simple, praying at the same time, for not having crashes and getting the scenarios as stable as they are now.

What I would like to know is if you or someone else know how to add train "types" to the spawn points selection. What I mean is that in Lafayette we have for example Custom 1 to 8. However in Sherman Hill there is a type called FreightCustom 1 to n.

I would also like to know if it is possible adding the spawn points to a third QD scenario so they can be read by both the east and westbound scenarios (and avoid double work), but I don´t know how to do that if at all possible.

EDIT As I explained in the first post, static consists without using spawn points have caused a sea of crashes when the file gets bigger that about 3-400 Kb. The full route would require nearly 1 Mb of static consists.