Linke Rheinstrecke: Mainz-koblenz Feedback Thread

Yes but the term was have been insulated as if DTG are stopping them looking at the forums, which I do not believe to be the case. If they choose not to visit the forums, which is the assumption from Matt's wording that is a different matter.

 

I was very hopeful that this was a guarantied purchase for me next week. Going by what I have read above, it looks like I will be putting another route purchase on hold for a month or two, or three, or indefinite!
I am so dreading to see what the state of the Peak Forrest and Midland Mainline is going to be like!

 

On the Nidderlabahn route the route intersects with the mainline 3 times but of these 3 times which ones are seen on this route?

 

Yes, I saw on the stream that they are really just scenic elements, but I wanted them anyway.
Guess I'll take your advice, though from what is being reported about Mainz- Koblenz, I might just stick with Niddertalbahn alone.

 

All of them. In the preview we got to see AI traffic at Bad Vilbel and Nidderau. Im unsure if there will be some at Stockheim or not.

 

There's no overlap between the routes, just the locos (which were widespread across Germany during this period).

 

It was mentioned in the nidderatbahn preview that the db br 628 (not sure about the db br 365 thou) would have playable services on this route but that the 103/110 would only appear on niddatbahn as AI traffic,correct?

 

Yes you are correct...

 

Correct, and the BR 365 is playable.

 

Not on mainz koblenz. Only niddertalbahn

 

There are AI 628s there going in different directions. The stream service actually starts with a neat parallel departure.

 

Yeah, I was referring to the BR 103 and 110. Not sure if those make an appearance at Stockheim or not.

PS: Just watched the preview stream again and I did not see any OHLE at Stockheim, so I guess the answer is no.

 

This is becoming a thread about Niddertalbahn...

 

Not sure if this is reported yet

1- I did the first scenario there is no catenary in the yard when assembling the train

2- first scenario when stopped waiting for the train to go by the gates are down. Cars on one side of the crossing stop. Cars on the other go right on through the gate the train or anything else in the way …. Except for the camera they stop and honk for that

3- the 110 training is impossible gold unless you take loops on the track before you stop. Gold is 2000. The training for the n- wagon has gold at 1500 points. Exact same training. You can get gold there

 

I just noticed this when driving SE 3361, shortly before Oberwesel the HUD indicates 140 km/h about 200m before the actual sign, the HUD also changes to "allowed" 140 before the train fully passes the sign. So either the sign is placed wrong or the HUD get's wrong information about the speed limit.

EDIT: Same at "Bingerbrück" here it is the other way around, the 120 km/h sign comes before the HUD indication of 120 km/h. Difference is again about 150-200m.

 

Just tried to play service RE (3444) Frankfurt am Main to Ingelheim (Journey mode).

I spawned in a cab car. Opened the doors and waited for the time to depart. When the time came, I put the reverser forward and released the brakes, then I tried to get the train moving.

Nothing. It did not move at all. Checked everything and everything looked OK, so I thought that maybe the BR110 is not started or correctly configured.

I went out of the train, run to the other side and I found .... ANOTHER CAB CAR and no engine at all.

Jeeez!!!!!

PS: Found the problem. The 3444 service appears as a BR 110 service in the timetable, but when you start it from the "Alternate Current" chapter of journey mode it is bugged and spawns 2 cab cars.

PS2: Reported with ticket #58607

 

Sounds like another result for the beta/QA testing gang… Given Journey mode is supposed to be the “Editor’s Choice” of each route, all the scenarios should be hand checked and tested to ensure they work properly. DTG are getting lazy and complacent.

 

The slamming door sound of the n-Wagen is missing when driving with the 110.3, no matter if in cab or outside view. But the door sound is present both inside and outside if using the cab car.

 

This is one funny bug if you think about it

 

Is there an overview of all bugs and errors that have been found so far somewhere? I think such an thread would be very helpful for everyone, but especially for DTG, wouldn't it?

 

One would think DTG would publish something like a known issues list...

 

So, during my trip down the line looking for collectables I have noticed some additional items:
1. Boppard Stadt* station is missing (it should be at the car park south of the Hauptbahnhof). *correction Boppard Sud.
2. The humpshunt at Bingen is missing (TBH, I'm not sure if it was still in use at the time, but the brickwork was there for quite some time)_
3. Suicide squad and body parts at Bingen

 

I would also like to add that the 103 cab view is not perfect. Yes I know this is nitpicking, but the texture on the right side with the gauges is a bit blurry. The element also misses the crews which with the panel is attached. Also the bolts / screws in the window frames are missing.

Here is a link to a photo of the original cab: https://www.fotocommunity.de/photo/fuehrerstand-der-103-217-krokofan/20143233

For the 110 those small details like the wingnut attached panel on rhe right are their. So it seems like the 103 has been rushed at the end. As said, this is nitpicking for sure, I just like this loco and I think we will see it on more routes in the future. So now is the time to make it better ;-)

 

I can find no trace of any such station ever existing, where did you find it?

 

unable to change PZB mode in BR 110

 

The mode selector is in the second cab, on the place where the pantograph selector is in the first cab.

 

PZB switch is found on Führerstand 2 (Cab 2)

 

OK so a slight error on my part - it is actually called Boppard Sud (it's been a while) if you look on google earth you can see a platform next to the car park at the south of the town. Deutsche Bahn details are here - https://iris.noncd.db.de/wbt/js/ind...00324&lang=de&seclang=en&zeilen=20&style=qrab or here https://www.bahnhof.de/boppard-sued
It is used by the trains of the Hunsruckbahn, but the services are very light, as the link above shows.

 

Ah that makes more sense. I don't know since when Boppard süd has been an official station ( or Haltepunkt) though.

 

Just want to note that service with the 463 number D(1124) can not be completed as you get stuck behind a train that won't move just outside Koblenz.

 

So BRO released December 6th
BRO Patch 1: December 7th
BRO Patch 2: December 8th
BRO Patch 3: December 13th

With other fixes on 21st of December. This time we don't even get a reaction for the Issues with this route. What's wrong? Do we have to wait for the next Roadmap Stream? It would be really nice at least if DTG would confirm collecting the stuff here or make a known Issues list. Thanks.

 

[QUOTE="TKessel, post: 626835, member: 26615" It would be really nice at least if DTG would confirm collecting the stuff here or make a known Issues list. Thanks.[/QUOTE]

If you look on one of the earlier pages, JD wrote something to that effect.

 

redtrainz True, but an update on the issues after the weekend where a lot of stuff came up would have been nice.
I'm also sure that Mike and his fellows are fully in Niddertalbahn polishing, so no time to take a look at these issues. I don't expect that anything is fixed by now but at least something like "notes taken here is the known issues, we are working on it" would be nice.

 

It's an UMU - Unpowered Multiple Unit!

 

This may be nitpicking, but why are all 103 marked 140 (see picture)? This looks out of place because it can´t be a marking for the locos top speed.

 

This is the speed at which the 103 may be towed by another vehicle. Thats alright.

The own maximum speed is written in the driver's cab.


see below right

 

Tried a little Scenario out of the box:

103: Notabschleppung nach Störung am Stufenschaltwerk:

 

2nd Scenario:

Loküberführung nach Chemnitz Abstellgleise (End of the LifeCycle):

 

The Journey service D (200) Milano to Dortmund from the "Alternating Current" chapter can not be finished. There is a huge line of trains stopped at red signals, probably caused by another train stopped by a red signal at Koblenz that should have departed heading direction to Mainz.

Full map view.


The train that seems to be blocking everything at Koblenz.

My cab:



Reported with ticket #58654

 

Ok thanks for the heads-up! I didn't know that.

 

wasn't the autotester supposed to be simulating all the services to ensure they worked?

 

meridian#2659 Are those custom scenarios? I'm interested

 

Custome made consists with a lot of time effort because tsw lacks the stock creator.

 

One thing I recently recognized - seems that the 103 doesn’t have a light cone, so that the walls of the tunnels round St. Goar are not illuminated, like for example the 110 does. Looks a little bit weird.

 

https://www.trainsimcommunity.com/m...3401-lfr-db-br-103-headlight-intensity-update This fixes this issue

 

Thank you very much, but not for me since I’m playing on Xbox.

 

The engine of the 628.2 from Niddatalbahn can’t be startet at every service beginning at Mainz. It works at the services from Gau Algesheim, the engine is allready running when starting a service from there.

 

Hi,

This seems to be an enjoyable route. I do not expect perfection. As it has been said, perfection comes at a cost and I don't mind some buggy textures or missing OHLE as long as it is fixed in a patch. The driving experience matters more to me.

Unfortunately, the inaccurate braking physics are not surprising. Some rolling stocks exhibit ridiculous performance, such as the M7A on the Harlem Line which drives like a rocket in-game (too much acceleration and braking performance), accelerating at almost 1,3 m/s² instead of 0,9 IRL. I drove it enough to make an extensive report to DTG and explain what's wrong with it many months ago, without any change for now

I understand that reproducing accurate physics is not an easy task. It is even harder to get physics right on older rolling stock. However, when the community brings up the same issues multiple times, even on previous DLCs using the same rolling stock, it is not really acceptable. We can still hope some physics fix like what has been done to the BR Class 166, but "when" is another matter ...

I'm still hesitating on buying this route, as I like accurate behavior. I'm planning to buy the Niddertalbahn route as soon as it get released on Steam, it seems to be very well-made and interesting to drive.

 

Subway#2400 If you follow this thread or if you take a look here https://forums.dovetailgames.com/threads/brakes-on-the-db-br-103.68315/ you'll see that the brakes don't have a physical problem, but the system is just not working correctly.

Btw. I drove some services with the 110 yestrday into Mainz, PZB is getting more and more strange to me when entering the station.

 

Thanks, I'll read this soon. This still delivers an inaccurate driving experience, so it is more or less the same as inaccurate physics such as bad acceleration parameters. The same can be said about wheelslip, trains in TSW rarely exhibit wheelslip, whereas in reality it happens often with a little rain. But this could be even harder to reproduce ?

Edit : I just read the topic you linked, it's very informative. I hope this will get fixed and deliver something more realistic, and then ... I may purchase this DLC