Tsw 3 Feedback Guide & Known Issues

We kindly ask that all players read this thread before submitting any feedback here or on Dovetail Support.

Useful Articles

• Train Sim World 3 FAQ
• Getting Started With Train Sim World 3
• How to Transfer Your Profile From Train Sim World 2 to 3
• How to Use Legacy Add-Ons in Train Sim World 3
• Train Sim World 3 Launch Article

To ensure that we can effectively prioritize and act upon any community feedback, please follow the guidelines below.

High Priority Feedback
For any issues which directly gameplay in such a way that you are unable to play segments of the game, please raise a support ticket with the details listed below.

Click here to submit a Support Ticket

For all other feedback, please check this section to see if the same issue has already been reported and add your own feedback as a comment. If an issue has yet to have a thread created for it, please use the information below to structure your feedback.

Feedback Template
To ensure that we have sufficient information to identify and reproduce an issue, please try to include the following details in your feedback. This can also be used as a template for creating a new thread.

Issue Summary:
Platform:
Game Mode:
Route Name:
Loco Name:
Service/Scenario Name + Start Time:
Step-by-Step Instructions:
+Screenshots
+Video Links

What do we do with your feedback?
Every piece of feedback we receive will be logged in our internal bug tracking system. This will be shared with other internal departments as we work towards a solution. New issues will be received by our development team and prioritized 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.

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.

How do I know when a bug has been fixed?
Due to the complex and sometimes lengthy process of bug fixing mentioned above, we are unable to provide a timeframe in which a bug may be fixed. Furthermore, while a bug is in this process, there is little we can provide in terms of meaningful updates on their progress. However, when we are ready to release a new game update, we will communicate this via our official community channels and provide release notes detailing the contents of a game update where relevant. Please use the following links to keep yourself up to date.

Lastly, we would like to thank you all for your time. Your feedback is greatly appreciated.

 

High Priority Known Issues
We are currently investigating a number of community reports. However, the following issues are known to be the most impactful. Therefore, we are prioritizing their investigation and will update this thread with their progress.

(updated 8th September, 09:53 UTC)

• The game crashes with a CE34878-0 error when switching cameras, if the camera is placed a large distance away from the train.
• Kassel - Wurzburg - BR185.2 - The Circle/Square button on the controller does not operate the SIFA pedal.
• There is no option to toggle motion blur on consoles - PlayStation is out, Xbox is coming soon.
• Performance Issues on Northbound services to Würzburg (Xbox One) Resolved in Day 1 Launch Patch
• Cajon Pass - ES44AC Introduction - The Engine Run switch defaults to Off, requiring the player to manually enable it resolved
• Steam - Profile transfer not visible on launch of game (if you've tried naming your profile the same as your TSW2 profile, please try removing the TSW3 profile and it should appear). Restart Steam to prompt the game to update.
• Cajon Pass - Some level crossings are not functioning as expected. Resolved
  
• Class 66 - There is a lighting artifact under the carriage.
• Timetables, Trains and Rail Journeys are missing in the menu UI on the Microsoft Store (PC). Scenarios and Training Modules can be accessed by selecting a route first and timetable services can be driven while exploring on foot - we expect this to be fixed in an upcoming update
• Class 375 - Missing deceleration sound effects.
• Unreal Engine crash log shown when exiting the game from the menu UI (Steam - PC).
• Class 31 and Island Line 2022 Content not being available yet (Steam - PC) resolved
• Preserved Collection roll-out for PlayStation will be staggered - more details here
• Epic players currently unable to access Preserved Content - more details here
• Some Xbox and PC Game Pass players currently unable to access Great Western Express, Rapid Transit, Peninsula Corridor, and East Coastway Add-ons - this is currently being tested