Beiträge von jpvdveer

Discord Einladung
Trete unserem Discord-Server bei (klicke hier zum Beitreten).

    An important thought on the station announcements. I just arrived at Nürnberg Hbf with a EuroNight service from Regensburg. The service in reality would continue all the way to Hamburg Altona, but in TS it is of course not possible to play beyond Nürnberg. Yet, the automated station announcements greated me with "welcome to Nürnberg, the terminus of the train". Fully understandable of course how this comes about. but appropriate it is not. It detracts fairly severely from the great immersion of arriving in the middle of the night at an intermediate stop of an overnight train that, in reality, would still have a long way to travel.


    Unfortunately, in view of the above, I think the default position will have to be that the automated station system cannot currently welcome travellers to the "final station of the train". The very nature of TS is that one often is driving just a portion of a longer train service, particularly as far as long-distance services are concerned. Absent information one way or the other, the station PIS will have to err on the side of caution (so just "welcome to Nürnberg" in the above example). Maybe in the future this can change if RWE2 were to develop more advanced scenario management capabilities (with the user being able to specify whether the final stop of the scenario really is the final stop of the train service that is being simulated?), but we are clearly not living in such a world yet.

    Was ich mir noch wünschen würde ist, das nach Auswahl des Szenarios und drücken des "Drive"-Button im RWE2 das entsprechende Szenario sofort gestartet wird. Im jetzigen Zustand wird ja nur der TS 2022 gestartet und man muss das Szenario, welches man spielen will, erneut suchen und starten.

    Wäre schön! Aber ich bin mir ziemlich sicher dass DTG diese Möglichkeit derzeit nicht unterstützt.

    A minor observation regarding the accelerometer when driving in cruise control conditions at constant speed (currently for me 200 km/h in the 3DZug ICE1).


    At zero gradient, TS and RWE2 both show the speed at a stable 200 km/h. In reality of course, the speed slightly fluctuates around this level under cruise control conditions. The speedometer does not show any decimal points so small fluctuations are natually not shown in the speed figure. However, they are shown in the accelerometer. which constantly shows small yellow/green movements. In the long term, this get annoying and does not serve any meaningful purpose.


    My suggestion would therefore be to apply a cut-off in the accelerometer, such that very minor speed changes are not shown. This could roughly mirror the effect of rounding to whole numbers in the speedometer. One does not see a change from 199,8 to 200,1 km/h in the speedometer so a speed change of roughly this magnitude should not appear in the accelerometer either. No need to be exact - an approximation will suffice. This will make for a more tranquil experience when driving in cruise control conditions.

    One function that I hope will also (eventually - not in the short term) be incorporated in RWE2 is a powerful search function. Like in TS (where a general search function also exists, although it is notoriously unreliable) it should be possible to search for "1S13", "TGV" or "186" and easily find the relevant scenarios incorporating that scheduled service or that specific rolling stock.


    A start already exists within the "route selection" menu, whereas it is possible to search for routes on the basis of, I believe, elements of the route name. This works well. [As the content explorer also lists all intermediate stations, one might eventually expect also to be able to search for these (e.g. search for "Valence" and and obtain "Lyon-Marseille" - this is more a nice-to-have however and not likely to be important for most users].


    A general scenario search function does not sit easily within the structure of the RWE2 interface where one first selects a route and then a scenario. For this reason, I would see a generalised search function as being more of a long-term addition to RWE2. But precisely because of the problematic nature of searching in TS, I do hope that one day we will have this.

    please keep supporting RWE 2 ! I need it !

    As has been pointed out above, RWE 2 is the most significant revolution in TS since the introduction of 64-bit. For journeys at higher speeds, I even think it is the most significant revolution ever. It is causing a notable shift in my TS usage towards higher speeds (where TS previously tended to be underwhelming), greater distances and more time spent in the cab (as opposed to external/passenger views).


    We all have a responsibility towards the developer, but also all other TS users, not only to point out bugs and areas for improvement, but also to promote this incredible and bold product wherever we can. I have opened threads for the product on the UKTS and Dutchsims forums and, whilst these are not as active as rail-sim.de, people have also responded favourably there.


    Eventually it would be great for the major streamers, for example AlanThomsonSim, to start discussing and promoting RWE 2. This is bound to happen. But for the product to reach mass market potential and consistenty positive reviews/comments during streams, some potentially controversial issues need to be sorted out first in my view, notably the need to cook upon every launch.

    And then once your RWE 2 play session is finished (when you finish you service), the scripts are completely restored in their original state.

    Just a question - what happens if the RWE 2 play session does not finish properly, eg due to a crash or power outage?

    I think I understand. Ludmilla-Fan All rolling stock sounds remain the same: nothing is changed. RWE2 only adds a number of additional sounds on top, which are often not adequately represented in TS.


    A key example is wind noise that in TS is usually completely absent. RWE2 makes for an incredible difference when driving at 200 km/h or 300 km/h.


    Importantly, for each additional sound layer, you have the option to reduce its volume, or to mute it completely. For example, and surely of interest to you as Ludmila fan, there is a "diesel engine layer" option that is great for stock with poor sounds, but that usually is not appropriate for stock that have high-quality sounds already. In such cases, you simply switch the diesel engine layer overlay off in-game.

    The content explorer could show all routes but the drive menu could only show routes that contains some scenarios for example

    I agree that that is an option. But the route interface in the content explorer, whilst being completely adequate for its purposes, is not as nice as the - simply outstanding - interface in the drive section.


    For me the route interface in the drive section serves a broader purpose than simply selecting a route or scenario to drive. It also shows off my collection. And it does so in a way that has never been done before - with large pictures that. in many cases, have appropriately been chosen (although there is room for improvement here in some cases).


    That "collection overview" feeling is bound to apply to other users too. And it would be lost if routes without scenarios are no longer shown.

    I have installed some routes that I need for route upgrades. For these routes, for example Altenburg - Wildau or Berlin - Wittenberg (KBS250),

    I agree that this is a good idea. But Jogibär, you never need the actual routes for route upgrades, just the associated assets. It is thus perfectly safe to delete these routes (eg in RW Tools or directly from the Content folder). This saves some disk space and will cause a slight speed gain when starting up TS.


    EDIT on reflection I am not so sure that this is a good idea. As RWTools does, I think there is a case to be made for RWEnhancer to show all installed routes, regardless of whether any scenarios are available. TS does not display these routes, in part because it has a horrible interface that quickly becomes messy if too many routes are shown. But with the nice interface of RWTools. and the capability to select routes by country, I think there is a case for all routes to be shown in RWE2, if only to remind the users of their existence! Routes that are only used for upgrades of other routes are redundant and are better deleted by the user.

    I think this is a good point. This is caused by the RWE2 HUD being centered. The TS HUD is also centered but has additional elements to the left of the track monitor. The track monitor elements of the two HUDs are not therefore at the same position.


    Opinions are likely to differ on this one - I guess most people would prefer the RWE2 HUD to be centered as currently is the case, but some people may (sometimes) prefer to have it at exactly the same position as the corresponding element of the TS HUD (eg when shunting, when the TS HUD continues to be useful). Perhaps this could be made an optional choice?

    Thanks for the update - getting better and better!


    One small comment - this morning I was driving in the Railstudio Class 43 and the notch name (which in the case of this engine can range from 1 to 40) was duly shown. Following the update it no longer is there, even if the corresponding option in the menu is selected.

    Just another feature request: it is great that the HUD can be hidden when in external views. Perhaps add an option (either separate or combined) also to have it hidden from the passenger view mode? The TS F3 HUD was always there so it was natural also to be there in passenger view. But with the modular, more flexible nature of the RW Enhancer HUD, having it also in the passenger view suddenly becomes more of a distraction.


    EDIT - this should also be the case in the route overview screen ('9' button), where the F3 HUD is not visible to begin with.

    Vielen Dank für die Weihnachtsaufgabe! Leider ist sie aber, meiner Meinung nach, fehlerhaft. In Lichterfelde Süd gibt es eine schöne Uberrasschung, dann aber sofort auch om 17:39 den Abfahrtbefehl! (Fahrplan: 17:45). Wenn man dann, gemàß Befehl, abfährt gibt es am Südkreuz eine Wartezeit von 7 Minuten. Vielleicht nicht so beabsichtigt?

    Just did a run with a BR155 on Project Freiberg and have the following two observations in this regard:

    • When taking an action which triggers a TS notification message in the top-right corner (eg enabling SIFA or PZB), the entire RW Enhancer overlay disappears (only pause notifications occur). I can only get the RW Enhancer overlay back by switching to another view (e.g. external view or passenger view). Further examination suggests that this is only an issue when the option to have the HUD disappear in external view is selected
    • Further on the pause notifications: Project Freiberg is a route prone to stuttering. At every stutter lasting more than 1 second, the RW Enhancer pause notification appears, rendering the stutters even more annoying. Happened at least 10 times during a one-hour trip, and stuttering is of course a problem in TS more generally. Not sure what the best way is to address this. One is perhaps to dramatically increase the maximum value of the RW Enhancer pause threhold, to perhaps 5000 ms, with a comment that the recommended setting is between 500 and 1000 ms and that higher settings should only be used on routes that are prone to stuttering. Not sure though whether a higher threshold will cause synchronisation issues. Another is perhaps to render the RW Enhancer pause notifications optional, i.e provide a setting to turn these off? To me personally these do not add a great deal.

    I also sent you a pm with some other, minor observations.