A Structured Vision for the Future of Train Sim World 1. Core Development Priority: Technical Stability Before System Expansion Before introducing new large-scale realism systems, Train Sim World must ensure long-term performance stability—particularly in scenarios involving consecutive services and dense network hubs. Current Observations When operating consecutive services (for example, arriving in Frankfurt and immediately taking a return service), noticeable performance degradation occurs. This is especially evident in major nodes with high AI density and layered timetables. The core issues likely include: Persistent AI entities not fully cleared from memory Dispatcher recalculations stacking under load Unreal Engine streaming limitations High-density timetable layers overwhelming CPU and memory Inconsistent resource cleanup between services This significantly impacts immersion, particularly for players who aim to simulate realistic locomotive driver workflows rather than isolated, disconnected runs. Strategic Recommendation Before implementing advanced realism systems, development should focus on: Improved memory management between service transitions AI lifecycle optimization Dispatcher stability over extended sessions Optional AI density scaling Performance profiling specifically for consecutive duty simulation A stable technical foundation is essential for any meaningful expansion of realism. 2. Implementation of an Optional “Duty Cycle Mode” (Umlauf Mode) Once stability is ensured, the next logical step is the introduction of a structured Duty Cycle Mode. Concept Overview At service selection, players could choose between: Single Service Mode (current standard) Duty Cycle Mode (Umlauf Mode) Duty Cycle Mode would allow players to simulate a realistic shift rather than a single isolated trip. Structure of Duty Cycle Mode In this mode: Services are dynamically linked into a coherent driver shift Turnarounds and layovers are simulated Dispatcher continuity is maintained AI traffic evolves realistically throughout the shift Players may operate 2–4 connected legs within one duty XP and progression rewards are scaled for full completion Importantly, this would remain optional to preserve accessibility for casual players. 3. Why Lower Austria (Niederösterreich) with Vienna Is Ideal for Duty Mode To fully utilize Duty Cycle Mode, route selection must support operational realism. Lower Austria connected with Vienna presents an exceptionally strong candidate. Reasons for Explicitly Supporting Niederösterreich Routes Operational Structure Favors Umläufe Regional services in Lower Austria frequently operate in realistic cycles such as: Vienna → Wiener Neustadt → Vienna Vienna → St. Pölten → Amstetten → Vienna Vienna → Laa an der Thaya → Vienna Vienna → Krems → Vienna Vienna → Retz → Vienna These routes are naturally structured for multi-leg duties. Manageable Length and Performance Stability Unlike long-distance corridors (e.g., Munich–Berlin), these services: Range between 30–90 minutes per leg Allow 2–3 leg duties within reasonable session length Avoid excessive AI congestion outside Vienna Contain rural and semi-urban density transitions This makes them ideal for performance-conscious design. Vienna as a Structured Hub Vienna is a major node, but it can be designed intelligently: Focus on Vienna Hbf and key corridors rather than full metropolitan sprawl Use controlled AI density Allow stable turnaround simulation Vienna offers operational depth without requiring full cross-border complexity. Strong Rolling Stock Identity Lower Austria operations allow authentic Austrian rolling stock such as: ÖBB 4024 / 4124 Talent ÖBB 4020 ÖBB 4744 Cityjet ÖBB 1144 with CityShuttle Regional Railjet services This creates strong regional authenticity and variety. 4. Designing Lower Austrian Routes Specifically for Duty Cycle Mode Instead of building a long single-corridor route, design it modularly to support realistic Umläufe. Example: Vienna – St. Pölten – Amstetten Concept Leg 1: Vienna Hbf → St. Pölten Layover: 10–20 minutes Leg 2: St. Pölten → Amstetten Layover Leg 3: Amstetten → Vienna This structure: Encourages extended but manageable play sessions Reflects real-world ÖBB operations Enables performance segmentation outside Vienna Example: Vienna – Laa an der Thaya (Highly Suitable) This is particularly suitable because: Mix of suburban S-Bahn and rural regional operation Lower AI density outside Vienna Clear turnaround logic Natural two-leg duty structure This route would be ideal for introducing Duty Cycle Mode in a stable environment. 5. Commercial and Design Advantages For Players Strong immersion Realistic locomotive workflow Optional deeper simulation Rural scenic value Authentic Austrian railway identity For Dovetail Games Performance-friendly route design Reduced asset overload compared to megahubs New regional market appeal (Austria has strong railway culture) Clear differentiation from repetitive German main corridors 6. Balanced Philosophy: Simulation Depth with Player Choice The key is optionality. Casual players: Continue using single-service mode Short play sessions Hardcore players: Engage in full Umlauf simulation Experience professional shift structure No audience is alienated. 7. Long-Term Strategic Vision If implemented in this order: Performance optimization Duty Cycle Mode Carefully designed Lower Austrian regional routes with Vienna hub Train Sim World could evolve from a scenario-based simulator into a structured operational railway platform. Not merely driving trains from A to B, but simulating the professional workflow of railway staff in a coherent, stable system. Lower Austria, especially routes connected to Vienna, provides one of the strongest real-world foundations for making this transition successful.
all nice and all, but too many km ... I would LOVE some proper Vienna content, especially some route involving S-Bahn, Stammstrecke and such... maybe sth like St. Polten - Vienna + Stammstrecke + S/REX7... and we would get 4746 and RailJets... for St. Polten - Vienna we would get the highspeed new Westbahn (including Tullnerfeld station), then Stammstrecke, and as for S/REX7... RailJets would terminate at Hbf or Vienna International Airport, we would (among many others) also get Desiro ML services to VIE, CAT train to VIE (with appropriate livery)... and of course then the nice chill route to Wolfsthal or s45 + S80 + maybe Marchegger Ostbahn? a lot of possibilities or Aspangbahn, with both legs - Wien Hbf - Traiskirchen Aspangbahn + Traiskirchen Aspangbahn - Wiener Neustadt (joining mainline near Sollenau station) really, anything involving a major Vienna station (Hauptbahnhof preferably with both upper and S-Bahn level, Westbahnhof, or even newly reconstructed Wien Franz Josefs Bahnhof... Wien Mitte is just underground mumbo jumbo, tho an impressive one ) and my fav train Siemens Desiro ML would be most welcome and yeah, improving the experience when chaining services together would be welcome (sometimes things like required uncoupling dont register etc.)
