Spirit of Steam - Fahrplanmodus - Zug entgleist

Moin Community,

Das neue DLC ist ja noch ganz frisch und ich bin direkt auf ein Problem gestoßen:

Im Fahrplanmodus, bei der LMS-Stainer-8F, habe ich ein Problem bei der allerersten Mission um 0:45 Uhr (die ganz ganz oben), dort muss eigentlich nur der Zug vorbereitet werden. Ich habe alle Anweisungen befolgt. An der Drehscheibe war ich mir nicht sicher, ob die Lok einmal gedreht werden muss, aber da man extra dorthin geschickt wird habe ich es einfach mal gemacht. Dann fährt man rückwärts über das bogenförmige Abstellgleis bis zu den Wagen, die man ankuppeln soll. Ich habe es mehrmals probiert, jedoch entgleist jedes Mal, sobald ich die Wagen ankuppeln möchte, mein Zug. Ich habe probiert die Bremsen vor dem Kuppeln zu lösen, geschaut das der Abstand zwischen Lok und Wagen nicht zu groß und nicht zu gering ist. Jedoch: sobald ich meine Maustaste betätige, kippt der Zug einfach vom Gleis und das Szenario ist gescheitert.

Ist schon jemand das Szenario gefahren und hat dasselbe Problem, oder habe ich etwas übersehen/falsch gemacht.

LG

Habe heute folgende Antwort vom Dovetail Support erhalten:

"We understand that coming across bugs in your game can be a frustrating experience, but we are very grateful that you have taken the time to contact us. Additionally, we would like to express our apologies for any inconvenience caused or if your enjoyment of the game has been adversely affected. Community feedback is what drives our development, and your feedback will be used to better inform our future work.

Issue ReportedThe issue appears to be caused by the wagons clipping through a buffer, but this has now been corrected. However, the update is still awaiting further testing and release scheduling before it will reach players.

• Spirit of Steam - Buffers causing issues with collisions - player derails near Edge Hill
  
  

What do we do with your bug report?

The issue/s you have reported will be logged in our internal bug tracking system which is shared with other internal departments to work towards a solution. New issues will be received by our development team and prioritised based on their impact on gameplay and put into a queue for further investigation. While we would like to be able to fix every bug, we may not have the time or resources. This is why we will attempt to target the bugs which are most impactful on our players first.

Known Issues

If the issue/s you have reported were previously reported by other players or identified internally we will take the information you have provided us with to enhance our understanding of the problem. Any additional details you have provided will be added to our records to ensure we have a complete picture of the problem.

What happens next?
In most cases the bug will then be passed to our QA team to reproduce the issue. This is an essential part of the process and can greatly enhance our understanding of a problem. However, if we do not have enough information to reproduce the bug, we may reach out to those affected for more information.

Next, the issue will be passed back to the development for further investigation until a solution can be found. Once a fix has been found, it will be integrated into a new "build" of the game which the QA team can test to ensure that it is working correctly and has no adverse effects on other content.

To keep the frequency and size of game updates to a minimum, fixes will be grouped with similar content. When planning a game update, we will normally target a few specific routes/add-ons, which is why some fixes may be held back until the next time an add-on is due for an update. In exceptional cases high priority fixes will be moved forward, even if that add-on is not due to be updated.

Following this, the update will need to pass certification tests on the many platforms we serve. Lastly, we will need to book in a slot with each platform holder, to push the update out to players. Each platform will handle these stages in slightly different ways. "