Naming and companions
Visual Pinball — and therefore vPinOps — finds a table’s companion files (.directb2s, .ini,
.vbs, .info, .scv) by searching three ways, in order.
The three-step companion rule
Section titled “The three-step companion rule”-
Exactly the table’s own filename.
Medieval Madness (Williams 1997) VPW v1.0.1.directb2snext toMedieval Madness (Williams 1997) VPW v1.0.1.vpx. -
The folder’s name.
Medieval Madness (Williams 1997).directb2sinsideMedieval Madness (Williams 1997)/, even though the.vpxcarries a longer name with the author and version on it. ⚠ Do not rely on this one — see below. -
A folder you have told Visual Pinball to look in. Its documentation describes one and does not say how it is configured, so vPinOps does not set it and does not guess a default.
Name the folder Title (Manufacturer Year)
Section titled “Name the folder Title (Manufacturer Year)”Medieval Madness (Williams 1997)/Attack from Mars (Bally 1995)/The Machine: Bride of Pin·Bot (Williams 1991)/The importer suggests this name from a catalogue of 2,554 machines, offers alternatives, and always gives you a box to type your own into. The catalogue suggests; it never gates — a table nobody recognises still imports, under the name you gave it.
Table identity — title, manufacturer, year, VPSId — comes from VPSdb.
Keep the table’s own filename
Section titled “Keep the table’s own filename”Do not rename the .vpx to match the folder. Authors put their name and version in the filename
on purpose, and that is how you can tell two builds of the same machine apart. The three-step rule
exists precisely so you do not have to flatten them.
When a name cannot be matched
Section titled “When a name cannot be matched”In a flat pile of downloads, backglasses and companions whose names differ from the table’s are matched by what they have in common. When it cannot tell, it says so and lists the file with a reason — it never guesses, because a wrong guess attaches somebody else’s backglass to your table.