Common Issues

#No Dynos Stand

shared/dynos.lua is empty by default. Place dynos with /dynos, or add them to shared/dynos.lua. Props stream in within streamDistance, 80 metres by default. See Placing Dynos.

#Dynos From Another Resource Disappear After a Restart

Dyno forgets other resources' dynos, run checks, and power modifiers when it restarts. Register them again on onResourceStart; see Create Dyno.

#Dyno Cannot Be Placed

Aim at the floor within 12 metres of you. A dyno too close to another is refused; the bed needs 2.6 metres across and 7.2 metres along. The tool needs admin.permission and admin.enabled = true.

#Dyno Cannot Be Removed

Only dynos placed with /dynos can be removed with the tool; the others are marked red. Remove a dyno from shared/dynos.lua by deleting its entry, and one from another resource through that resource.

#Run Does Not Start

The panel at the bottom of the screen says why while the car stands on the dyno, and E tells you again.

• Only the driver can start a run, and only one car runs on a dyno at a time.
• The dyno's jobs, or Config.Settings.dyno.jobs, may keep your job off it.
• The engine must be running, with its health at minEngineHealth or above, and the car standing still.
• The front wheels must stand on the front rollers, within lineUp. Follow the panel until the strip turns green.
• The rear rollers reach wheelbases from about 2.05 to 3.45 metres.
• Check CanRunDyno in the hooks and any run checks from other resources.

#This Kind of Vehicle Can't Go on the Dyno

The car's class must be in allowedClasses, and it must be a regular automobile spawned on the network. The server also refuses handling values no car has, such as a mass over 30,000 kg, and power modifiers that multiply to more than 10.

#Run Stops Mid-Pull

A run stops when the driver leaves the car, the engine stops or its health drops below minEngineHealth, the car is gone, or no full pull is made within pull.maxMs, a minute by default. The notification says which.

#Graph Clears During the Pull

You lifted before the limiter. Hold the throttle flat, from 95%, until the car is on the limiter, then lift. See Running the Dyno.

#Numbers Seem Too High or Too Low

Sit in the car and run /dynocalibrate to see every input and factor in the F8 console. Change formula.scale for every car, formula.classScale for a class, or formula.models for one car. Power modifiers from other resources and SetVehicleEngineTorqueMultiplier also count. See Formula & Calibration.

#Screen Stays Dark

Only the screen of the dyno nearest you is lit, within screenDistance, 30 metres by default. A dyno without screen in shared/dynos.lua, or placed with No screen, has none.

#Print Key Is Missing or Printing Fails

Check printout.enabled. The dyno_sheet item must exist in your inventory, and the character needs room for it. Only the driver can print or show their own result, from the panel after the run.

#Printed Sheet Is Blank

Only sheets printed from a run carry its result. A dyno_sheet given through an admin or inventory command has no run in its metadata.

#No Discord Message

Set zyke_dyno_webhook in your server.cfg and check webhook.enabled. See webhook.

#Laptop App Is Missing

Check laptop.enabled and that zyke_laptop is started. The app only shows for a player whose job may use at least one dyno. With the laptop's app store on, download Dyno from the store first.

#Laptop App Cannot Connect

The dyno's jobs may keep your job off it, or it stands further than laptop.range from you. Connecting needs you to stand at a laptop.