Loco Class 220 Voyager - Feedback

I had a Voyager announcement cut out temporarily so it ended up sounding out "this is a cross country"...pause..."Edinburgh Waverley"

 

Resuming a save game with the Voyager you load into a brake application even though when I saved the train was under power. Fortunately this is recoverable by throttling back and going into a brake position then releasing to regain power. However it looks like something amiss with the scripting not restoring properly.

 

That is probably not a bug.

 

The trainside PIS needs another pass:

 

I've seen this issue on the 801/802 too where the time on the internal PIS doesn't show 0's in the minutes. E.g. the in-game time could be 12:06 but the PIS says 12: 6

 

I feel like I've seen this on trains in game too - might've been the Azuma

 

AI trains show destination as out of service
Departure time is just the time in game
No carriage numbers / letters

 

The 395 does this as well.

 

Can confirm same problem as reported yesterday. Loading into a saved run with the 220 has a full brake application which you cannot recover from until the train is stationary.

 

I mainly drive in Freeroam but with other trains running round so I drove my train between timetables trains so i would like to have the ability to set the destination screens

 

Guard buzzer needs a key bind

 

Whats with the head lighting on the 220 in the dark you cant see nothing from the cab. But if you go external it lights up the whole of the track ahaed as it should. Ive included a few shots at diffrent lighting contitions. The 150 has excellent headlights at night.

 

Is it just because the cab is so high you cant see the effects of the headlights from there? I mean, they are not there for you to be able to see anyway.

 

When running it on free roam the traction lock doesn't go away meaning I can't drive it as a result

 

Some points I noticed about the 220:

I couldn't depart Exeter St. Davids due to the cab doors being open. This was despite the cab doors being not open.

Once I got moving after I restarted (seemed to work as long as I didn't touch the cab doors), the throttle/brake lever moves quite slowly meaning the train is harder to drive than it needs to be.

For some reason the rear unit seemed to permanently be in high idle despite even when the reverser was neutral

It would also be nice if the announcement system could be swapped out for the one on the 802 since that one reads all the stations and seems to be more suited to longer-distance journeys.

 

Was having fun on my first run until I made the first stop.... Couldn't get it to move again no matter what I tried. I didn't put the brakes in emergency or anything, all I did after stopping was put the reverser in neutral.

 

There's a work around for this.
Open and close the cab doors and the traction lock should be released. It seems when it spawns in, it believes the cab door is open.
Matt showed this work around tonight on the live stream.
The issue has now been logged and they are going to look into it and hopefully patch it.

 

The thing is you open the cab door on the voyager when driving along and it doesn't care, because apparently the cab door isn't part of the interlock system

 

well it thinks it is when you spawn it in freeroam.

 

I just found a workaround for the emergency brake issue. I don't know how consistent this would be but I put the reverser back to off, reset physics, then opened and closed the right side cab door. The moment it closed again the brake pressure came off.

 

The suspension model seems off. It’s subtle on Riviera but then when you take it onto other routes it gets incredibly bouncy.

Manchester Commuter & ECML both had this issue for me. Not sure if the issue is Riviera though as I did have to turn up my suspension on that route due to it being abit under done.

Playing it on other routes seems more consistent with each other, leaving Riviera as the outlier.

 

I don’t sign Voyagers but in the sim I’ve had the random fault about an engine stalling and needing restarting. Now, if they’re similar to a Turbostar this could only be done with the train stationary and the Directional Switch in Neutral.

 

PS5 player here. Sorry if this has already been raised but x2 issues:

If you toggle the aircon/temp, blinds and (possibly) the horn/wipers in neutral, the reverser moves to reverse.

The train remains idle/stationary if spawned in timetable mode on other routes - at least has happened on ECML.

 

See this:

 

are there meant to be 4 voyager varients on the riviera line, they all have different timetables and amount of services but there is no way of telling them apart currently. Is anyone else seeing this?

 

Im seeing 4 different voyagers and 3 different 802.

 

Use the top one, it has all the services.

This is an issue on ALOT of trains after yesterday’s update.

Be nice if DTG actually checked these things before pushing them, christ knows what they’re going to end up pushing to our systems one day.

 

Hmm, doesn’t seem to be working for me.

 

Open one door, then the other, then close both.

Its stupid but it works (for the free roam issue at least).

 

Ok, so cab doors at both ends?

 

Cab doors of whichever end you’re driving from.

 

Surprised this hasn't been mentioned already but the engine note is completely missing turbo sounds. This would probably be a simple fix, so that's my suggestion for things to add!

 

When AI is driving a 220 in service mode the PIS on the outside of the voyager says not in service.

 

According to a modder they didnt include cues for turbo sounds for whatever reason

- https://www.trainsimcommunity.com/m...6888-riviera-voyager-and-gwr-hst-interim-mods

 

Platform: PS5
The train won't move after changing cab ends
I drove the train from Exeter to Plymouth, waited for the next service, shut down the cab and set up the other cab, but the brakes wouldn't release and were stuck on 2.1
I checked to make sure I'd shut down the other cab correctly and I had, non of the doors were jammed either as I have faults turned off at the moment

 

Note: I checked this by restarting the service from Exeter and stopped and changed ends after driving for a couple miles, the exact same thing happened again

 

There's currently an issue with the voyager, the doors and brake interlocking.
If you can't get the brakes to release, open and close all cab doors. This should then release the interlock preventing the brakes releasing.

DTG are aware of this issue and are working to fix it.

 

Really liking this train, well done to all involved in the development of it! as others have said, the cab is too overexposed, and the headlights don’t seem to illuminate much.
Guard mode doesn’t really work on this train, unless you implemented the proper procedure.
The power handle could do with moving a little bit faster.

 

Guard Buzzer does have an keyboard shortcut however it’s is different from the other trains I believe it’s J

 

After a couple more runs, this appears to be the same bug as the 700 and 350 have where the train won’t show proper destination if it’s started time was before your start time. But if the AI start time is after player start time it will show correctly.
On PS5