Beiträge von oldsnake


Abonniere unseren Kanal auf WhatsApp (klicke hier zum abonnieren).

    0.7.20.0 update is now available :)


    For more details please visit this page: https://www.rwcentral.com/topi…pdate-07200-is-available/


    CHANGELOG:


    - Added 'FPS Limit' TS setting in settings menu

    - Added quickdrive time, weather and season randomization buttons in drive menu

    - Added timetable infos for scenarios in drive menu

    - Added timetable infos for scenarios in content explorer

    - Added 'Only Display Routes With Scenarios' filter in drive menu

    - Added 'Close window when cooking is finished' option in content cooker window

    - Improved track monitor refresh rate

    - Increased HUD accelerometer reactivity

    - Smoothed HUD accelerometer animation

    - Optimized train acceleration calculation system

    - Improved user account connection status logging

    - Fixed 'Station PIS' enabled/disabled state not correctly saved

    - Fixed being able to set '60' as minute in quick drive time in drive menu



    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.

    Next update should improve this. The speedometer animation should also be smoother.

    What i like about the new weather/season/time implementation is that you can choose what you want to have randomised. Much better than in TS where everything is randomised.

    You even have an option to randomize time but in the 'day' time range if you maintain CTRL while pushing on the "Randomize" button ;)


    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.

    Externer Inhalt www.youtube.com
    Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
    Durch die Aktivierung der externen Inhalte erklären Sie sich damit einverstanden, dass personenbezogene Daten an Drittplattformen übermittelt werden. Mehr Informationen dazu haben wir in unserer Datenschutzerklärung zur Verfügung gestellt.



    For me it seems RWE2 doesn't save the settings made for "Gameplay" correctly. I disabled the Station PIS, but when I start a new session it is enabled. This happens for me every time. The setting for the Onboard PIS seems to be saved permanently.

    Good catch ! Fixed in next update ;)


    EDIT: Cooking 'Close window when cooking is completed' setting done.


    And the scenario task timetable is now displayed in drive menu and content explorer :)


    Moin DonMattheo.

    Ja, Azuma ist kein AP Repaint. Probiere z.B. mal das GWR Repaint für den 800er von AP... da sagt er bei mir: "Missing element" und startet den TS ohne Enhancer, obwohl das repaint vorhanden ist. Bei sämtlichen anderen AP Reskins genau das gleiche...


    oldsnake RWE2 does not seem to recognise most of Armstrong Powerhouse Reskins. Says "Missing Elements" and starts TS without Enhancer showing.

    Have you at least tried a 'reset' in the content cooker ?

    Thank you for your patience and support ! In the end RW Enhancer 2 will be a central platform for many things including: hardware interface, modding tools and much more.


    EDIT:


    - 'Only Display Routes With Scenarios' filter in drive menu: implemented

    - TS FPS Limit setting support: implemented

    - Timetable display for tasks in drive menu: work in progress

    - Randomize weather, season and time: work in progress

    - 'close cooker when cooking is done' option: work in progress


    Everything should be done for tomorrow update

    oldsnake Would it be possible to make a “randomise time, season and weather” button?

    Could be done yeah, what would be the most convenient way, 3 "randomize" buttons for time season and weather. One global button to randomize everything, or both solutions ? :) Waiting for you guys advices on this.


    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.

    The English community is worried of using RWE 2 as in it's first days, there has been some important issues. But now most of the critical issues are fixed. So i need to regain confidence from a lot of potential and existing users. I'm confident that my commitment to improving and fixing things will help me. Please keep giving your positive feedback to the community and do not hesitate to redirect some users to the wiki (https://wiki.rwenhancer.com/) and help other users with their issues, i'm watching feedback everywhere and i try to respond as much as possible to users wishes. Just saw the latest post on UKTS forums and will include a new TS RWE 2 setting to set the FPS limit of TS directly in RWE 2 in the next update. ;)

    I'd like to have a big button to close the content cooker window instead of using the relatively small "x" on the top right corner. Of course that's not important, but I think it would be more convenient.

    What about a "close cooking window when cooking is finished" setting ? :)


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

    Script modifications are made to work even if TS is being played without RWE 2. But if this happen, the script(s) will be restored automatically next time RWE 2 cooking is started. So it's quite difficult to mess up things now :)

    RW Enhancer 2 is designed to mainly READ existing Train Simulator data. For the sound system, like jpvdveer said, RWE 2 is adding it's own sound layer and it's running completely independently from TS sound engine. No TS sound are modified by RWE 2. So you can just mute RWE 2 sound and everything should sound as it should like you were playing you regular Train Simulator content :)


    RWE 2 is taking a great care to not mess up/modifiy the content of Train Simulator but sometimes accidents may happen that's why the installation wiki page recommend you to make a backup of your Train Simulator Assets just in case something goes wrong. Just a simple backup and you are 100% safe if anything goes wrong.


    The only main content modified by RWE 2 at the moment is the engines script files (this is required so RWE 2 can read important data). But only the engines that you drive in your current RWE 2 service are modified. And then once your RWE 2 play session is finished (when you finish your service), the scripts are completely restored in their original state.

    Malkondo This is normal, at the moment RWE 2 is calculating the "flyby" direct distance (like TSW 2) and TS displays the "track length" distance. So it is normal to have a difference. Track distance can't be calculated by RWE 2 at the moment but this may change in the future.

    Thank you ! This can be done yes and this is a good idea. Will be done soon.

    Update 0.7.19.0 is available :) https://www.rwcentral.com/topi…pdate-07190-is-available/


    CHANGELOG:


    - Added TS windowed display mode support

    - Added RW Enhancer 2 window position/size restoration support when restarting the software

    - Improved display window management system

    - Fixed forced 'Bloom' and 'Procedural Flora' TS settings even when using legacy TS shaders

    - Fixed window size and position not being correctly restored when ending a service


    EDIT: 0.7.19.1 hotfix is released to fix the UI layout