Real Time Physics Lab 7 Homework Answers
Most students hit a wall when they try to set up the collision simulation in Lab 7 because the friction coefficient table in the manual doesn't match what the software actually uses. I spent three weeks debugging what I thought was a unit conversion error before I realized the manual's "kinetic friction" values are actually for static cases. The workaround is to divide everything by 1.3, which is the calibration factor baked into the Real Time Physics Lab 7 Homework Answers version they ship with. The core issue isn't your calculation. It's that the assignment expects you to use the nominal mass of the cart, but the software reads the actual measured mass from the sensor array at sample 47 of every run. That offset matters more than you think. When I first did this lab I got 0.84 for the momentum ratio instead of the expected 0.91, and my TA told me to "check my math" before I finally pulled the raw CSV and saw the mass drift. The momentum conservation check is supposed to show a 5 to 8 percent deviation due to air resistance, but the default simulation uses a vacuum model unless you flip the AirDrag flag in the setup window. Flip it, rerun, and your numbers should land within the acceptable range for the Real Time Physics Lab 7 Homework Answers rubric without any weird scaling hacks.
Setting Up the Collision Without Frying the Solver
Start the simulation in Step 3, set the restitution coefficient to 0.65, then immediately pause. Do not hit play until you see the timestep counter freeze at 0.001s. If it scrolls past 0.005s your integrator is stiff and the collision energy will dissipate into numerical noise before the first bounce even registers. I once ran a group project with that exact misconfiguration and we ended up with a coefficient of restitution above 1.0, which physically means the carts gained energy from nowhere. The fix was to reduce the timestep manually in the Advanced Settings panel, not to touch the restitution value. That setting is read-only during runtime for a reason.
Where This Method Actually Breaks Down
The Real Time Physics Lab 7 Homework Answers approach works fine for elastic and moderately inelastic collisions with masses between 0.2kg and 2.0kg. It fails hard when you drop below 0.1kg because the contact detection algorithm triggers ghost collisions at the boundary of floating point precision. I learned that the hard way when a lighter cart spawned a phantom bounce that added 12 percent error to the total system energy. For super-light objects you're better off switching to the impulse-based solver in the Alternative Physics Engine checkbox, which uses analytical contact resolution instead of the default penalty method. It's slower, roughly 40 percent, but it won't hallucinate collisions that don't exist.
Get the Full Details

Reading the Velocity Graph Without Being Fooled
The velocity plot in the Results tab shows instantaneous values, but there's a 2-sample delay baked into the display. If you see a sharp spike at time 3.2s that doesn't appear in the raw data table, that's the smoothing algorithm doing its job. Ignore it. The actual collision event sits at sample 3.4s in the CSV export, which is what your grader will check against. One thing nobody mentions is that the peak velocity marker appears before the actual impact because the software interpolates between samples. You can find the real impact time by looking for the first sample where the derivative of velocity changes sign, which usually takes about 30 seconds to compute manually or 5 seconds if you use the built-in differentiation tool in the Analysis menu.
Submitting the Lab Report
Export the raw data as CSV, include the plot screenshot with the timestep annotated, and write a one-paragraph explanation of any deviation above 5 percent. That's the standard format for the Real Time Physics Lab 7 Homework Answers submission, and it's been consistent across every section I've seen in the past four years. Anything shorter gets returned for missing context, anything longer gets skimmed.