Just an idea I've been thinking.. Could we someday get a new file structure for the tables? Like a VPX file, but as source code! I've been collaborating with some table edits and it would be lovely to use Git for the table development and even releasing. There would be only images and models that are binary data, but all the rest would be C#, vb and XML. Then you'd get proper version control, commit history and maybe someday even a CI system with automated testing of certain table features. Implementing new mods would be just new feature branches, that the author could merge into master branch, if he's happy with them. This would give enourmous boost to all table development and collaboration with development and testing. Devs are always finding ways to implement more realistic physics and lightning and this would need continuous improvement for tables.
I had that idea as well, but didn't wanted to hijack the thread so i didn't mentioned yet. Wouldn't it be great if all (new Unity based) tables would be hosted on Github (or a substitute) and you could regularly just check out the newest additions & changes to the tables? Usually you only want to maintain certain things yourself (like POV (file), options, etc.) but keep up to date with the core table, script, etc.
Imagine a sync client (e.g integrated into PinballY) where you can checkbox categories you want to sync (EM, SS, Originals, mods, etc.) Also having all other assets synced as well would be great (backglasses, wheels, ipdb database infos, ...)
This is all only loosely related to the Unity development, but as already said, the right file structure could be the starting point for enabling this. That would be a major step forward into nowadays ways how to handle this. (Keeping things in sync by hand and monitoring forums to not miss a table update is very outdated...)
Another idea, which could potentially be picked up: I hate having to hand tune POV per table and its unflexibility (not able to switch quickly between alternative settings). It would be to great if you can define a personal set of only a few preferred POV settings (one for EM, a few for SS, some table specific ones maybe) which can equally be used on all tables. Cycling through these POV settings on the fly while playing a table would be great. Think of Pinball FX3. I know, this is currently not possible because VPX takes the bounding box of all 3D elements in the scene into account. Simple approach could be the definition of a user (table author) defined bounding box for the 3D volume which is the supposed viewspace.
This could alctually also be added to VPX 10.7.....
Not to forget:
It's great work what you are doing here!
Cheers