BUG in latest revision:
I found a small bug in the latest revision, it is about the Targets not showing the check mark in "Has Hit Event" property. It may be possible this bug has been in older betas, but I haven't notice that until now.
It is easy to check, make a table, add several targets, make sure all of them has a check in "has hit event", then save the table, quit, load it again, and some of the targets do not have the check anymore. I think it is just an editor thing, as all the targets seem to be working fine, but somehow it cannot read or display that "has hit event".
Made table
put in 30 targets
1st 2 had hit events by default, 3rd did not, next 3 had hit events, the 7th did not, and it kept going on like this at random
saved table exited vpx
reopened table
hit events still missing, assigned hit events to the affected targets
now all targets have hit events.
save table, close vpx
reopen vpx, now other targets have lost their hit events, one for each target i fixed.
closed vpx 10.7 with out saving
opened table in 10.6.1 looked at targets
all targets have hit event showing
Closed out of 10.6.1 no saving
opened back up in 10.7
hit events still missing
So the data is stored but it is not reading it back correctly
put 30 lights on table
hit the targets
results kind of random, inconclusive
save table exit vpx 10.7
open table in 10.6.1
run table, table is white, as expected
hit targets
lights work consistently
The targets drop fine in 10.7 hit event or not
but could be a problem if you wanted to use the hit part for something.
Like if you did not want it to be can drop until the 3rd hit or something.
Made table in 10.6.1
made 30 targets
verified all had hit events
saved table
opened in latest 10.7
every 6th target was missing hit event
closed table no save, exit vpx
kept going backwards in revisions that i still have
rev 4356
many targets missing hit events, like maybe 1 or 2 out of every 6 have them.
closed table
opened table made in 10.7 latest revision
more targets missing events in 4356 than what i initially saw in 10.7.4368
So looks like we have had this bug for a bit, and it may have been worse in earlier revisions.