Update 5 Fixes v0.5.2.1

  • Bereit für Out of Time ? Dein Stuhl wartet bereits !

  • Eine neue Äre beginnt - bist du dabei? Fülle einfach das JoinUs aus

  • Helfe uns in einer aus den Fugen geratene Welt auf dynamischen Schlachtfeldern zu überleben. Zum JoinUs

  • Connecte auf unser Teamspeak unter diesem Link: Connect to OOT

  • Das Teamspeak Botsystem wird uns kostenfrei bereitsgestellt von JTS3Servermod.de
  • Update 5 Fixes v0.5.2.1

    24. Mai 2022 - 19:43



    Hi Pioneers!

    Hello everyone, today’s patch has a bunch of Path/Block signals fixes to address some old issues and some of the new issues introduced in the last patch, there’s a few remaining issues/polish related to them that we are aware of so please check the “Known issues” section for more.

    This patch should be pretty safe but if we somehow introduced some big bugs, please let us know over at our QA Site https://questions.satisfactorygame.com/ We’ll take a look at them ASAP!

    See you again soon <3

    BUG FIXES

    • Stations cannot be placed inside Path blocks anymore, path signals now give a proper error message if a station is found inside a block.
    • Short blocks, about 75% the size of a train cart, should now work with path signals.
    • Fixed Path signals placed right after a station being incorrectly reserved by trains going to the station.
    • If the timetable changes and the next station changes, trains should properly re-path now.
    • Fixed timetable getting “Invalid next stop” if the current station was removed when it is also the last station on the list.
    • Current stop should now properly display for clients in multiplayer or dedicated servers.
    • Fixed Truck Stations displaying at the center of the map


    KNOWN ISSUES

    • Remaining issues related to Path/Block Signals in the scenarios we have looked at can be solved by rearranging the signalling, replacing path signals before stations with block signals, using path signals at intersections and block signals along one-directional tracks, so consider trying those options if you’re still having issues.

    • A reminder for people who have been having issues with unexpected crashes on startup or weird behaviour with the game, in that case please try to verify your game files.

      You can do this on Steam by Right Clicking the game in your Library > Properties > Local Files > Verify integrity of game files...

      And on Epic by clicking on the three dots (“...”) next to the title or at the right side, depending on your selected library view > Verify

      This may or may not redownload a large amount of files which might take a while depending on your internet connection or hard drive speeds so be wary of that.

      If you are using mods, they might need to be updated or uninstalled after updating so please keep this in mind too.
    • If you are experiencing issues launching the game or loading a save and you have already verified your files, you might have some incompatibility with DX12 as the default renderer, you can try the following launch options to try to force DX11, DX12 or Vulkan to run respectively.
      • d3d11
      • DX11
      • d3d12
      • DX12
      • vulkan
    • Dedicated Server Crash reports, Currently Crashes that happen on a Dedicated Server are automatically sent to us, this is enabled by default, we plan on including a toggle for this in GUI but for the moment, if you want to disable automatically sending crash logs you can do this:
      • Go to the Server Install folder
      • Open “Engine.ini”
      • Add the following:
      • [CrashReportClient]
      • bImplicitSend=False
      • Save changes and restart the Server
    • Packet routing is incompatible with multihome, so we're automatically disabling the former when the latter is enabled

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!