- Learn
- Tutorials
- Physics Labs
- Push Lab
- Appendices
- E Troubleshooting
Appendix E — Troubleshooting
Every chapter’s If it didn’t work names the slips most likely in that chapter, and how to find each one. Here they are together, chapter by chapter.
Two checks find most of them. First, names must match exactly: a message, a timer or a table row is matched letter for letter, capitals included. Second, compare with the chapter’s game. Every chapter’s Goal holds the game as it is at the end of that chapter, and its catch-up download is that chapter’s finished project. Play it next to yours.
E.1 Chapter 1: A Prepared Workshop
A cart seems to vanish? Start by comparing the Scene position with the setup card, before changing anything inside the cart. Find its row in the setup card and compare X and Y. Run Lab again; the cart should be back on its rail.
A rail looks doubled? Its painted version is already inside Chamber Art. Check Visible on the track’s Sprite, and keep that switch Off. Leave the Collider in place.
The Copper load sits away from its cart? Select Copper Cart’s additional Sprite and compare its local Transform with the card. Those positions belong inside the Object. Once corrected, the pictures sit together again.
E.2 Chapter 2: Place the Carts
A cart follows without a press? Look for the starting Mode on the held Event in Place Cart on Rail. Released starts empty; Holding carries the placement Actions. Restore that arrangement and the cart waits for your hand again.
Copper jumps onto Blue’s rail? Compare Copper Cart’s laneY with the lower lane value on its Copper Cart Object card. Give Copper its lower lane value. Run again, keeping the shared Logic as it is, and the carts should stay apart.
Neither cart takes a press? Open the Cart Press Input Library and check its Enabled switch is on. Compare Advanced Wiring and Load Order with the Library card. Compare Capture Cart Press next. The Script connects the listener; Place Cart on Rail still owns movement.
Home works but the orange button stays silent? Look for Return Button in Lab, then check both its Logic attachments. Listen for Control Press supplies the selection that Return Button Response needs.
A cart stays held after release? Look at Mouse Release in Place Cart on Rail. It needs Release Cart and the change back to Released. Restore those together and try dragging again, watching for the cart to stop when you let go.
E.3 Chapter 3: Deliver an Impulse
Space does nothing? Check Game Rules is placed in Lab. Then compare Request Pair Push’s Command field with Push Both. Restore that connection and try a fresh run, with both carts released.
Only a missing-cart message appears? Compare the carts’ cartNumber values and Identify Workshop Cart attachments. Each must claim its own reference. Run again after that correction, letting creation fill both empty sets.
The knob turns but carts keep their old speed? That is the next-push choice at work, waiting for the action that delivers it. Press the blue button. Watch the new reading after that action, comparing it with the one you saw before.
The dial keeps following after release? Compare its Mode changes with the release and interruption Events. They all return to Released. Restore that destination and the knob should wait for another press.
Help opens without readings? Make a push with both carts released. If the sheet still stays blank, compare Show Measured Reading and its caption attachment. The opening zeros deliberately stay hidden until an observation exists.
Bench labels disappear at the wrong time? Compare each Object’s showOnOpen value. The dial face and Next Impulse use No; sheet elements use Yes. Restore the mismatched value.
E.4 Chapter 4: Load and Measure
The rack stays empty? Look at Game Rules first. Prepare Workshop Weights needs its attachment, the named weight resources and matching object text in Weight Pattern. Restore one missing connection, then run Lab again.
Copper has two loads drawn in the same place? Compare the extra Sprite names with the removed components on Copper Cart’s marked Object card. The earlier painted load comes out when movable weights take over. Keep the generated copies and remove those old extra pictures.
A weight moves but mass stays unchanged? Follow its registry row and cartLoadChanged. Change Native Cart Load needs to be attached to each cart. Restore that listener and try the transfer again.
The whole gauge face turns? Select Follow Native Velocity on that gauge’s Logic workspace. Its Components Sprite picker needs Velocity Needle. Change that binding and the face should stay still while the needle turns.
A row expression names an unknown weight? Compare its For Each Row Variable Name with the expression below it. The row’s name belongs inside that loop. A temporary Declare Variable must also come before the Actions that change it.
An old paper changes when the cart stops? Check where its Text reads. Printer Reading and Reading Ticket use Push Readings; the gauges use native velocity. Restore that distinction and the paper can keep its moment.
The latest caption remains after its load changes? Compare that caption’s readingCartNumber with its cart, then check the added validity Events. A new accepted push restores a valid comparison.
The sheet opens on the wrong page? Follow inspectedPush through the view Functions, then compare the page choice on each caption Object. The historical captions use historyPage Yes; the current instructions and status use No. Restore the mismatched holder value.
E.5 Chapter 5: Compare and Remix
Copper keeps following the dial? Store its choice with V before turning the dial for Blue. Read both choices before pushing again, using the separate bench caption to check what each cart will receive. Linking with L deliberately restores the shared choice.
A goal still waits despite an earlier paper showing exactly the result you wanted? That is its freshness check. Make a newer accepted push with both readings valid. You can still inspect the earlier paper while the new attempt waits for its own answer.
A goal misses the first of two quick pushes? Keep Evaluate Workshop Goal directly after Record Pair Reading inside Push Workshop Pair. Restore that order so each accepted observation is judged before another can replace it.
Reset restores the wrong things? Compare the two Events in Reset Experiment Controls. Reset calls the Function. Defaults instead restarts Lab with its authored arrangement, rather than the loads you moved during play. Restore that distinction, then try the same chosen load again.
A setup opens with a missing weight? Check Restore Weight Setup on every weight resource and both named setup Events. Each copy needs the same identity it uses in Workshop Weights. Restore that connection before reopening the file.
A file is refused? Open U’s page and read the setupStatus message beside the file controls. The refusal is general. Keep the current experiment while checking the saved proposal.
Did you change Impulse Settings, Shared, maximum after saving that file? Tuning must match. Return to a matching project or save a new arrangement with today’s tuning, then try opening that new file.
Your own new file is refused too? Stop Lab and compare Apply Starting Setup with its card, beginning with the matching-settings checks. Check Restore Weight Setup’s attachments next. Run the completed Scene again and repeat E, rearrange, I to see whether the arrangement returns.
A label acts from the wrong page? Compare its visibility attachment and Object values with the card, then its response’s page check. Restore one mismatched value and test with the sheet closed too.
