RW2: The Bug Thread

[longbow]

Couple of minor ones:
Ox-Padd - Chasing Yellows scenario gives multiple errors on initial load, but works when reloaded.
Hedborough - static car/bus not removed from Level Crossing at docks exit, road traffic now drives through them.

[Trainguy76]

I've found that on "Heavy" trafficked roads, the cars stack up on one another. (At level crossings)

[black8]

hi,
Its Bugging me , the new size of the text in the world editor is bad news for those of us who can still remember seeing the "Age of steam."
Ross
NZ

Ross
NZ

What? What did he say?

Sounds like we are having fun with RW2. I cannot make any comments for now because my dear (not so) old computer has let me down again, (this post is coming through the work machine) but I follow these discussions with great interest. I still don't get it how so many bugs and other irritable issues are showing in RW2 after all this developing and testing by the RS folks ; especially annoying for new users of the sim.
cheers!
Jos

[bhl809]

On the whole I like RW2. Only one thing is bugging me so far: On the HUD the next signal is displayed, but not its state. Is this an oversight or on purpose?

Another more minor thing: From the speed display its not clear whether its kilometers or miles per hour. You can only assume by the type of route you're running what it is.

[qrdriver]

On the whole I like RW2. Only one thing is bugging me so far: On the HUD the next signal is displayed, but not its state. Is this an oversight or on purpose?

It's on purpose. As has been discussed previously, when you're driving a real train (which I do) you know where the next signal is going to be but you don't know the aspect until you see it, eg. if you pass a yellow signal you drive expecting the next one to be red until you see it. I think it's a very realistic change.

[FrankJ]

On the whole I like RW2. Only one thing is bugging me so far: On the HUD the next signal is displayed, but not its state. Is this an oversight or on purpose?

I believe it's on purpose you are supposed to look out of the window as per real life

Frank

[longbow]

Chasing Yellows scenario is broken again and Duff Coal scenario fails at start with similar multiple Many Failures/Route Blocked messages. Other Oxford-Padd default scenarios appear ok.

[michaelth]

Some of the locos are not shown in the list, i.e.

- all Class 390 variants
- some BR151 variants
- some Meshtools Class 24 & 42/43 variants

Michael

[ghawk2005]

I think it may be best to focus on the BIG problems here. There are niggles I have with the new driving interface too - the main one being that the gradients are not nearly clear enough on it - but these are not, as we call them in the business, "regressions", only shortcomings in a new feature that don't render it worthless.

Breaking the HST's brakes is a serious problem.

So, are there any other trains in RailWorks which suddenly have broken stuff? Are scenarios supplied by default non-completable? Do you get crashes when loading a route? These are the things which I'm looking for.

Its great to see notched brakes but the brake gauges are all over the place, and as you say, although there are the full 6 positions plus emergency, it doesn't work correctly at all,

Could this be fixed please??

G

[adburgess1992]

Text FAR too small in the 'asset' filter flyout (Blue box, right hand side) - using a 17" inch LCD here, not the mammoth monster that RSAdam has access to...

If you goto

Steam\steamapps\common\railworks there should be a file called Config.xml and if you edit it in notepad from the looks of it it changes the font sizes im not sure i haven't tested it because for me it used to be the other way around

i used to think in Railworks 1 the font was way to big but now running the game 1600x900 windows it fits quite nice on a 23" monitor

[markpullinger]

Hi guys, strangely enough managed to complete the chasing yellows scenario but I had to save & restart when the throttle hiss got too annoying & the AWS dropped out, Restart from save cured both & even got to end early - for once! But agree brakes are `interesting`! If you drag the brakes lever though they work normally between the notches for some reason. So some duff values for the notches might be in there!

[longbow]

More scenario problems:

"Oxford Bound" scenario fails to start, giving "Unable to load tracks.bin".
"Geordie Deltic" fails, with multiple "Route Blocked/Can't Find Destination" errors"

[bdy26]

Not so much a bug but a step to do and be wary of. I had a similar issue with RW2 not recognising the 37, 101 and WCML in the asset filter in the scenario editor. The scenario would load, but little track, few buildings, caternery etc despite full graphics settings. There were no boxes to tick to select 37, 101, WCML etc in the pop-out window. Most annoyingly all consists involving these assets were deleted from the scenario (I foolishly clicked save on exit - my fault).

Fixed by a full verify game cache and deletion of blueprints - suggest everyone does this before doing any editing - it's taken me a couple of hours to fix the scenario (will upload it for those who fancy a pair of 50s over Beattock in the snow).

Otherwise works very well, like the new F4 though I swore I wouldn't. WCML now runs far better too.

B

[ightenhill]

Theres definatly something amiss with the text in all screens.. To me it seems to have that effect where photoshops been used to over smooth the text giving it a blurry look that just doesnt work when its at a high res and small..

My only other bug is you cant turn off the splash menus using the old method because they are awful.

[styckx]

I know it's not a bug, but please bring back the -nosplashscreens command line option. As a guy who spends 70% of his time with Railworks repainting, that 15 seconds waiting for the splash screens to cycle seems like an eternity when all I need to do is load up a route real fast, look at a locomotive for two seconds to check the progress and exit to go back to Photoshop. Rinse and repeat, that 15 seconds adds up to a massive amount of time `waiting'.