- Mar 17, 2012
- 4,293
- 0
Physics data is apparently controllable on an object-by-object basis, so such data would be stored with the objects themselves in the table assets. The collision meshes and art/lighting resources are there as well, along with the table's ROM data (which would contain the operator menus).If they have to keep old assets for the one or two dumb asses who insist on not updating their tables, then the cost and complexity exponentially increases every time they update the tables. Thus, we may never see them improving the physics, fixing the Black Hole and Gorgar problems, add operator menus (or limited options) and other wish list improvements.
So I'm not seeing the issue. You either download updated tables and get whatever features happen to be included in the assets for those updated tables, or you don't and remain with the version you have. All the executable has to keep track of is which asset version you have. As long as the updates for a given table are cumulative (each update includes all prior updates in case a user has missed a version or two), this should be manageable.