#[SPZ2-6072] [1.0.2-rc1] [⚠️ MODDED] How the way of connecting two train rails affect the preview of

13 messages · Page 1 of 1 (latest)

upper flower
#

If the blue train joins the red, then after unloading, the preview of red is normal, but the preview of blue becomes a mix of both. The same happens if you join red to blue, blue stays normal, red becomes both. If you join them at the same time, it becomes the mix of red and blue

sterile waspBOT
#

Thank you for reporting this bug! Our team will review your report soon.
Feel free to add more details in follow-up messages — we're also scanning for duplicate reports automatically now.
📨 There are currently 25 reports awaiting team review. Due to the high volume, it may take a little longer for us to get to yours.

📋 Log files help us investigate issues. You can find yours here:
Windows: %USERPROFILE%\AppData\LocalLow\tobspr Games\shapez 2\Player.log

💾 Savegame files (.spz2) are very helpful if relevant to the issue!
Export via Main Menu → Play → click the download icon on the relevant savegame.
You can also find them here:
Windows: %USERPROFILE%/AppData/LocalLow/tobspr Games/shapez 2/

#

Wait Stations cause train predictions to travel down areas that trains will never end up
Done • Priority: High • Fix: 1.1 Release [1.1.0] • Game: 1.0.0-alpha5-rc2 • Resolution: Fix Verified

Wait Stops cause Shape Previews to appear on rail paths that trains will never actually travel. In a setup with multiple colored train routes, a Wait Stop assigned to one train (e.g., blue) incorrectly causes predictions to appear on another train's route (e.g., red). The issue is persistent across savegame reloads. Expected behavior is that Wait Stops do not cause predictions to appear on unrelated routes. This was verified as fixed in a later beta build.
💬 Threads: [1.0.0-alpha5-rc2] Trains unload preview

#

For rails merge points and route configurators can stop predictions from working
To Do • Priority: High • Fix: None • Game: 1.0.3-rc3

Shape Previews can stop working when Rail Intersections and Route Configurators are used together on rails. To reproduce, start a new Classic Mode save in Regular scenario, enable cheats, and place a combination of Rail Intersections and Route Configurators. Removing a Rail Intersection can trigger the issue. Shape Previews should function correctly regardless of any combination of Rail Intersections and Route Configurators. The issue is still occurring and appears to be related to the presen...
💬 Threads: [1.0.3-RC3] Route Configurator may cause

#

Shape prediction does not update at vortex when changing rail route configuration from the same unloader into another
Done • Priority: Highest • Fix: 1.0.0 Release • Resolution: Duplicate

Shape Previews at The Vortex do not update correctly when the player changes a Train Route configuration to redirect a train from one Shape Wagon Unloader to another. When two differently colored Train Routes deliver shapes through the same Shape Wagon Unloader, both Shape Previews display correctly on the Conveyor Belts. However, after rerouting one train to a different Shape Wagon Unloader, the Shape Previews on The Vortex fail to reflect the change. The expected behavior is that Shape Prev...

#

Predictions will show up in the wrong places for trains that use the same rail network that will never meet if the rails change to another space level.
To Do • Priority: High • Fix: Post 1.0 • Game: 1.0.0-beta6

Shape Previews appear in incorrect locations for trains that share the same rail network but never actually meet because the rails transition to a different machine level. The previews seem to ignore elevation changes, causing them to display at wrong points along the route. This was observed in Classic Mode on the Regular scenario with cheats enabled. The expected behavior is that Shape Previews should only appear where trains can actually reach on the same level of the rail network.
💬 Threads: [1.0.3-rc3] [1.0] Incorrect shape previe

#

Rail Routing Indicators can create multiple paths
Done • Priority: Medium • Fix: None • Resolution: Missing Feature

Rail Routing Indicators display paths for train routes that are no longer reachable after track reconfiguration. The issue occurs when building an upper branch first, then building a lower branch that reroutes trains. The original upper branch continues to show routing indicators for trains that can no longer physically reach that section of track. This creates visual confusion as the indicators suggest multiple valid paths when some are actually unsatisfiable. The system marks this as intent...

#

Train predictions aren't recalculated after rerouting a train
Done • Priority: High • Fix: 1.0.0 Release • Resolution: Fix Verified

Shape Previews are not recalculated after rerouting a train. To reproduce, start a new Classic Mode savegame in the Regular scenario, enable cheats, place trains, and reroute a train to go in a new direction. After rerouting, Shape Previews for the new direction are not updated. Expected behavior is that Shape Previews should automatically refresh when a train's route changes. This issue has been fixed and verified.

upper flower
sterile waspBOT
# upper flower
💾 未命名存档

⚠️ Mods: Time Control — this issue may be mod-related

Started in

1.0.2-rc1

Last played in

1.0.3-rc3

Scenario

Classic - Regular

Seed

22906

Research

79%

Buildings

90,764

Completed

No

#

[1.0.2-rc1] [⚠️ MODDED] How the way of connecting two train rails affect the preview of fluids color

sterile waspBOT
#

[SPZ2-6072] [1.0.2-rc1] [⚠️ MODDED] How the way of connecting two train rails affect the preview of

#

🔁 This bug report has been marked as a duplicate of SPZ2-6072: Predictions will show up in the wrong places for trains that use the same rail network that will never meet if the rails change to another space level.

Shape Previews appear in incorrect locations for trains that share the same rail network but never actually meet because the rails transition to a different machine level. The previews fail to account…

Please refer to that ticket for updates.
If you believe this was incorrectly flagged, run /reopen-bug and we will have a look again!

Threads linked to this issue: