Table not declared to DOF

Technical code : DOF_ROM_UNCONFIGURED

What it means

DOF is installed on this machine, but nothing indicates this table was ever declared to it — any physical toys it expects (light-up flippers, contactors...) may never trigger.

Why it happens

DOF (DirectOutput) drives the cab's physical toys via ledcontrol*.ini files, which organize their settings per ROM under "[RomName]" section headers. If this table's ROM name never appears in any of those files, DOF simply was never given a configuration for it.

How Pincab Toolbox detects it

The free scanner checks the following:

At least one ledcontrol*.ini file exists under this install (DOF is indeed configured here), but none of them contains a section with this table's exact ROM name.

What to do

DOF is installed on this machine, but no configuration exists for this table. In practice: your contactors, flashers and LEDs stay silent on this table while they work on the others.

  1. DOF does not guess effects: it reads a configuration file downloaded from the community's DOF config site.
  2. Note the ROM name given in the Pincab Toolbox scan result.
  3. Go to the DOF config site, sign in to your account, and check this table is in your list.
  4. If it is, re-download your full config pack: it is regenerated on every download and will include the new table.
  5. Extract the ledcontrol*.ini files into your DirectOutput folder, replacing the old ones.
  6. If the table is NOT in the site's list, nobody has created its config yet: you can request it on the DOF forum, or create it yourself in the site's editor.
  7. Run a new scan.

Check your own pincab

Pincab Toolbox is a free Windows scanner for Visual Pinball X and PinUP Popper. It finds and explains problems like this one. No account, no telemetry.

Download for free

Covered: Visual Pinball X (10.x) and PinUP Popper. Not covered: Future Pinball, Pinball FX, Visual Pinball 9 and the other frontends (PinballX, PinballY).

Other problems

All problems