Satisfactory Production Planner
🇯🇵 日本語
What the documented distinction says
The basis is Coffee Stain’s official Satisfactory 1.1 release notes. This is a 1.1 description, not a hands-on check of a current 1.2.x client.
Check the control before rebuilding the fitting
- Watch for a Junction route-choice hint. As you approach a Junction, check whether the client shows a route-choice prompt. The official 1.1 notes give E as the keyboard example for choosing a route while approaching, but this draft does not treat that key as universal across devices or current versions. Confirm the actual display and timing in the current client. For a Branch, check its shape and the path traveled separately.
- Use the hint for the input device you are using. Do not assume a PC key applies to every device. A PS5 player report describes missing or overlooked guidance while riding in the tube. That is an individual report, not a guarantee about the current UI.
- Check input settings and test at the choice point. If the displayed input does not respond, check the current Controls settings and connected device. Test the route choice before passing the Junction, one approach at a time. This draft does not claim an exact input window beyond the official phrase “while approaching.”
- Then inspect the physical connections. Once the prompt and input have been checked, trace which opening each tube connects to and whether that tube reaches the intended destination.
- For a Branch, compare the path with the shape constraint. When trying to reach the resulting branch path, check whether your route travels through the longer segment described in the official notes. If you also need a return route, ride and verify that route separately. The official notes do not say that every Branch layout is one-way-only or establish whether every configuration supports a round trip.
Troubleshoot by symptom
- A Junction takes you to an unexpected exit: Check the route hint and input first. After checking timing and device settings, inspect each opening and destination. Players and Q&A posts report route-selection problems, but those reports do not establish a persistent current-version bug.
- You cannot reach the Branch path: Compare the fitting’s shape and the route you traveled with the documented longer-segment condition. Record which connected path you used instead of calling the whole fitting “one-way.”
- You are unsure whether the return works: Do not generalize from a one-way trip. Ride the return route as a separate check. Update 1.1’s official description does not establish round-trip behavior for every Branch layout.
- The prompt is missing or input has no effect: Recheck the approach prompt, input device, Controls settings, exact game version, and approach path. Test another approach before concluding that the construction is wrong. Current 1.2.x reproducibility has not been checked for this draft.