Beiträge von Tux

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

    Tatsächlich habe ich die letzten Tage/Wochen viel getestet was den RWA Manager und die Nordbahn anbelangt.

    Gefühlt habe ich alles 20x heruntergeladen, Probleme hatte ich keine.

    Wird noch die RWA Manager Installation verwendet oder der mobile Client?

    Grundsätzlich habe ich vorhin die Gesäusebahn vorhin auch geladen und das ohne Probleme, alle Assets vorhanden.

    Verwendest du die Installation mit oder ohne AP Wetter?

    Nur mal ne kurze Rückfrage Spikee1975 weil es mich interessiert.

    In welcher Konfigurationsdatei wird denn das Pwd in Klartext gespeichert? Wärst du auch bitte so frei mit mir die Info zu teilen, welche dll deine Festplatte scannt?

    Gefühlsmäßig würde ich sagen, 99,9% der Train Simulator fahrenden User verwenden Windows.

    Die zusätzlichen, nicht Steam-Store Addons, kommen alle als .exe daher und dahinter sitzt sehr oft auch DRM-Software.

    Mit GLÜCK könnte man dies mittels Wine zum Laufen bekommen, ich würde aber nicht darauf wetten.


    Mein Gefühl sagt mir, dir fehlen mit deiner Linux Mint Installation noch Dependencies für Proton und Wine.

    An deiner Stelle und wenn du es erneut ausprobieren möchtest, würde ich empfehlen, auf Steam OS zu warten ; dauert aber noch ein bisschen.

    Da ist die Chance am Höchsten dass der TS funktioniert.

    Um meinen PC vor unbefugten Zugriff und Datendiebstahl zu schützen. VPN ist ein Verschlüsselung System womit man im Internet Quasi Anonym sich bewegen kann und dabei werden deine Daten Verschlüsselt. Eine so genannte Ende zu Ende- Verschlüsselung, bekannt auch aus WhatsApp und anderen Sozialmedia Plattformen beim Nachrichten versenden.

    Marketing ... Dir ist schon bewusst dass der VPN Provider deine Daten lesen kann? Diesbezüglich gab es auch schon Datenschutzskandale wo der VPN Provider die Daten verkauft hat.

    Aber gut, jeder wie er glaubt.

    Bei so einem Vorfall würde ich gar den ganzen PC platt machen, wer weiß wie die Logindaten geleakt wurden.

    Wenn es erraten wurde wäre es ein Zufall weil man den Steamaccountnamen auch erraten müsste + MFA aktivieren.


    Weiters, einen Passwortmanager (Keepass z.B.) verwenden und Passwörter generieren lassen.

    Du musst dir nur ein Passwort merken und hast die best mögliche Sicherheit bei allen Accounts.


    Nach Möglichkeit nicht überall dasselbe Passwort verwenden und Variantion rein bekommen.

    In Österreich wird ohne Neigetechnik gefahren, wird in Passau immer ein bzw. ausgeschaltet.

    Von Passau bis zumindest Würzburg (bin im April die Route gefahren) war es dann eingeschaltet.

    Neuer Beta Build:

    Public Beta Build 77.1a
    Hello everyone, we'll shortly be pushing out the next Public Beta build for your attention. Please post your feedback relating only to the build...
    forums.dovetailgames.com


    Hello everyone, we'll shortly be pushing out the next Public Beta build for your attention. Please post your feedback relating only to the build version 77.1a here. If you wish to discuss things not relating to this beta, please use the other forums.



    What's Included/Changed



    Here's an outline of what we're providing in this update:


    • We have completed work to upgrade several tools to 64-bit and to support 64-bit addressing. 64-bit binaries have been added for the Blueprint Editor 2 and associated command line tools ConvertToGEO, ConvertToTG and Serz. These 64-bit tools have a “64” suffix to distinguish them from the 32-bit versions. The 64-bit Blueprint Editor 2 is contained within a Tools/x64 subfolder. These tools are currently considered experimental and feedback on their functionality is requested. Note that on first run of the 64-bit Blueprint Editor, the user should set the RailWorks Folder correctly by using the Tools > Options menu item and restarting the app. These tools are designed to be run in the Tools/x64 folder and should not be copied into a different location, nor should the Schema be copied into this x64 folder.
    • Implemented a fix for the 64-bit build failing to start with some Intel GPUs on Windows 11. This could cause the application to silently fail before the splash screen. By default, PhysX is now initialised using software rather than hardware. The hardware initialisation could cause a crash on non-CUDA GPUs.
    • Implemented a fix for SilverLining stars not being visible at night time. In some cases this bug could result in SilverLining sky being replaced by the default sky (although SilverLining precipitation would still work). The magnitude for stars should be adjustable by editing the SilverLining config file if required.
    • Increased the size of the heap using for loading geometry in 64-bit mode from 1 GB to 2 GB to stop some out of memory errors on the streaming heap.
    • Fix for a situation where a D3D "Device Not Reset" error can occur without first getting a "Device Lost" error. This should fix the remaining D3D crashes, such as those on alt-tab switching.
    • The FPS limit now defaults to 60fps (as opposed to 30fps). This limit is now enforced during menus and pause screens in all cases (no matter what command line option is used) to reduce uncapped frame rates and excessive CPU usage whilst browsing the menus, especially with some Ryzen CPUs.
    • Fast sound update optimisations have been implemented but are disabled by default due to triggering failures. These changes spread updates to sounds over multiple frames, but could cause problems with delayed sound triggering. This can be accessed by using the command line "-FastSoundUpdate" with an optional value for the update factor, e.g. "-FastSoundUpdate=10" (the default when enabled).
    • A new command line option "-ShowScriptTiming" has been added to aid developers when optimising their Lua scripts. This renders an overlay on screen showing all the Lua scripts that are being called, the total number of calls, and the total time spent in them.
    • A new command line option "-ShowAverageTiming" (which must be used in conjunction with ShowScriptTiming) has been added. This provides additional information - namely the mean and medium time spent in each script. This can be used to determine if the scripts are always performing poorly or if there are outliers. For example, an Engine script may be called 50 times, but one of those calls may take significantly more than the others (i.e. for the player loco vs AI locos).
    • A new log filter has been added - "Script Performance". When enabled this will provide performance hints via logmate. Currently, this only has one warning - when a script tries to set a value to the same value it already has (e.g. via SetControlValue). In some situations, this Lua call can have a huge performance hit, because the text-based lookup can be very slow. In general, scripts should only set values that they know have changed. Note that GetControlValue has a similar performance penalty, so using that followed by a SetControlValue will have worse performance overall. Instead, scripts should track these values themselves using internal Lua variables wherever possible to minimise these calls. An example might be a loco script that sets headlights and rear lights every frame, rather than when the loco changes direction. With some scripts this filter can cause a huge amount of extra output to Logmate, so a new filter was added rather than using an existing one. Developers should be aware of this when using the "All" filter.

    Of particular interest here is that we've added some additional support for developers to profile their content in terms of its impact on performance. The additional launch options added to the core should help with performance tuning overall as developers can now see which aspects of their scripts are taking the longest to process.



    As always, please let us know your thoughts on the above update and, let us know about any problems that arise as you play.



    Best, Steve