Railworks America

I have found that the Castle Rock Scenario doesn't work ( Pueblo to Denver) Anybody having this issue?

Have not tried that one yet as the SB&B scenario is giving me trouble.

Gents,

Just my observation, and it is only that as I do not have this pack yet, but descriptions like "doesn't work" and "giving me trouble" are very vague. I bet you will have more luck after giving more detail on your issues.



Regards,
Trevor

Edit, James I see you posted your full issue in another thread. Please disregard my advice.

worked fine here this morning. did you try the usual stuff, verify game files, clear blueprint cache?

Just ran the Castle Rock scenario. Worked correctly.

I must admit that at least the SanB-Barstow are more likely to cause problems.
Just because I put a lot of AI trains in the scenarios.
Moreover, these AI trains are very long and also the long scnerio duration can cause problems because a lot of stuff is loaded while you play over the time.

It could be that some "not so good" PCs may have problems.

I get frame rates in the 70's most of the time, altho there is the usual "stutter" and frames drop to 30 or so. But overall, these scenarios are really well done.

micaelcorleone wrote:I must admit that at least the SanB-Barstow are more likely to cause problems.
Just because I put a lot of AI trains in the scenarios.
Moreover, these AI trains are very long and also the long scnerio duration can cause problems because a lot of stuff is loaded while you play over the time.

I got stuck in the eastbound Cajon scenario by a long AI train in Victorville that was blocking the track. I was stuck at a red signal about 1.5 miles out of town. Undoubtedly there is a rule of some sort that kicks it loose, but whatever it is, it didn't get triggered. I was running the route a few minutes early, if that explains anything.

Toonces wrote:I got stuck in the eastbound Cajon scenario by a long AI train in Victorville that was blocking the track. I was stuck at a red signal about 1.5 miles out of town. Undoubtedly there is a rule of some sort that kicks it loose, but whatever it is, it didn't get triggered. I was running the route a few minutes early, if that explains anything.

One of the testers also had this problem in the development (at least sometimes).
For others it worked well. I don't know what causes this, but I promise that I'll look it up again and if I find a solution it'll get updated when the pack gets the update for RW3.

micaelcorleone wrote:One of the testers also had this problem in the development (at least sometimes).
For others it worked well. I don't know what causes this, but I promise that I'll look it up again and if I find a solution it'll get updated when the pack gets the update for RW3.

Based on a hint from someone at uktrainsim, I saved, exited and then continued the scenario. The blocking train seemed to have disappeared, but the signal was still red (I could use tab to get permission to pass however). It starts to sound like a more generic RW bug than anything else..

One more weird nit - I was navigating through the passenger view zooming through the various cars and in and out on various things, and somehow the zoom level got screwed up. When I went back to the loco cab, I was zoomed in so far that the speedometer on the console filled my whole screen. Nothing I could do would reset the zoom level to normal. When I get a chance I will see if I can come up with repro steps.

Toonces wrote:One more weird nit - I was navigating through the passenger view zooming through the various cars and in and out on various things, and somehow the zoom level got screwed up. When I went back to the loco cab, I was zoomed in so far that the speedometer on the console filled my whole screen. Nothing I could do would reset the zoom level to normal. When I get a chance I will see if I can come up with repro steps.

OK, try this - it will only take 3 minutes. Start the "Riding the Chief" scenario. First press "1" to get to the engine. Next press "5" to get the passenger view. Then hold Control+rightarrow for a few seconds - it will cycle through some things and settle down. Press control+uparrow - this zooms in a bit. Next hold control+leftarrow for a few seconds until it again settles down. Finally press "1" to get back to the engine. What you are left with is a view from the cab that is out the window, but it is zoomed so you cannot see any of the controls in the cab, and pressing the downarrow button won't zoom out. You can repeat this sequence multiple times - each time the view from the cab is zoomed in a little bit more.

I tried the same thing with Oxford->Paddington. The control+left/rightarrow keys don't do anything there, so it doesn't really tell me whether this is a generic issue with RW or an issue with Genesis/Superliner.

Ack! I usually drive out of the cab so I never saw this issue. Good thing the alerter on the Gensis sounds out of the cab, eh?

Have you tried another keyboard? Maybe arrow keys aren't working? Did you remap any keyboard commands? That will seriously FUBAR this sim.

arizonachris wrote:Have you tried another keyboard? Maybe arrow keys aren't working? Did you remap any keyboard commands? That will seriously FUBAR this sim.

I think the only thing I remapped is something needed for the German Railways ICE (Shift-TAB). Everything else should be identical.

I haven't tried another keyboard, but in all other respects the keyboard seems to function normally. If nobody else can repro, I can find another one to try..

On the P42 scenario for the SB&B, the issus is that the AI train #8340 will not move. I noticed that there was a duplicate instruction for the same location. An intermediate instruction for the Summit Portal and a final destination for the same location. Removed the th duplicate intermediate instruction. Still will not move. Now I am suspect of the marker "BNSF Amtrak meet". I have found in the past that markers put in under a scenario often do not function correctly. Will try to remove instruction and try again.

Don't know about Ox/ Pad, but I finally finished this route/ scenario this morning (jeese, 2 hours!) and it ran fine. Now, I can't seem to get the Genesis up to track speed limit at times, so maybe being slow helped? Hit a few yellows, never a red.