Table Master Issues Lists v2.0

In order to further aid FarSight in integrating these lists with their own bug tracking systems, to better organize the lists, and to allow FarSight personnel the ability to directly comment on these lists and their contents without having to wait for me to add their thoughts (since the previous lists were locked), we have created a separate forum for the Table Master Issues Lists. All new issues for existing and new tables will be posted here instead of in the table-specific fora.

Even though the threads are unlocked, only FarSight employees and the moderation team may post here. This is, again, to keep the lists confined solely to the facts and free of cluttering opinion. Posts expressing opinion should be made in the table-specific fora, the Art forum, or one of the discussion threads in the platform-specific fora.

Also, as part of this move, each of the 38 lists is being reviewed by FarSight and myself, with an eye to getting anything that might have been missed the first time into FarSight's internal tracker, to update bugs that were fixed long ago, and to purge bugs that can no longer be reproduced. As you can imagine, this process is not something that will get done in a single weekend, or even a single month. Your patience is appreciated.

Table Master Issues Lists:

Latest Updates:

10 Oct 2014

• Added HOF scoring issue # 00-011 for multiple tables.

27 Sep 2014

• Created initial list for Bram Stoker's Dracula.

11 Apr 2014

• Created initial list for High Speed.

15 Mar 2014

• Reversed slingshot art issue # 19-504 for Twilight Zone is fixed!
• Created initial list for WHOdunnit?.

13 Mar 2014

• Updated status of upper lock issue # 11-005 for Black Knight.

01 Mar 2014

• Created initial lists for Black Rose and Black Knight 2000.
• Added attract mode camera issue # 05-017 for Medieval Madness.
• Updated status of flasher art issue # 07-511 and reconfirmed Cannonball Run camera issue # 07-015 for Cirqus Voltaire.
• Added scripting meltdown issue # 11-014 for Black Knight.
• Updated status of many issues for Dr. Dude.
• Updated status of table nonprogression issue # 24-001 for Firepower.
• Insert art issue # 27-501, instruction issue # 27-701, and high score issue # 27-901 were fixed a long time ago for Space Shuttle.
• Updated status of many issues for Terminator 2: Judgment Day.
• Extra ball/special issue # 36-001 and scoring issue # 36-004 were fixed a long time ago for Haunted House.
• Updated status of many issues for Tee'd Off.
• Added insert art issue # 39-501 for Victory.
• Added display alignment art issue # 41-501 for El Dorado City of Gold.

CORE TABLES


SEASON 1 TABLES


SEASON 2 TABLES


SEASON 3 TABLES



SEASON 4 TABLES
[TR]

Thanks for taking on this task, it's appriciated

By the beard of Zeus, please add to TZ: table shadows missing!

I would say leave these threads locked because as soon as you open them they will become a shambles like every other attempt at a bug list. I know it means more work for you Sean adding bugs from other threads but at least we'll have one really nice well maintained list. Its your baby though so whatever you think is best, great job so far.

That's a big job. Thanks for taking it on Sean. It will be nice to have one place to see if something has been reported before. I'll bet FS has never heard about some bugs, while they probably received 50 support emails about others. And I've often seen the same bug reported in several different threads. This should clean a lot of things up.

Kevlar said:

I would say leave these threads locked because as soon as you open them they will become a shambles like every other attempt at a bug list. I know it means more work for you Sean adding bugs from other threads but at least we'll have one really nice well maintained list. Its your baby though so whatever you think is best, great job so far.

Click to expand...

Totally agree on keeping them locked.

Yes, keep 'em locked.

Maybe a locked list and another sticky'd thread for each table for reporting issues? I think if you don't there will be a thread for every little thing.

In order for it to not take on a chore assigned in the lower levels of Hades, I would suggest keeping the threads unlocked but deleting every post that does not conform to the bug reporting procedure.

Very nice work! I agree that it's probably best to keep the threads locked. BTW, you should send Stephen a link to this thread too.

Maybe you could arrange the bugs in the master table lists in order of importance? For example, with Dr. Dude, it would probably be the mix master multiball camera bug. Just a suggestion.

Keep up the great work Sean!

Consensus seems to prefer clean and locked master threads, so that's what we'll have. I will probably keep the existing system of art issues go to the Art forum and other table-specific matters in individual threads in their table forums. The reason I'm leaning against a single companion discussion thread is that each bug in a list is linked to the thread I found it in. If all the bugs in a table are discussed on one thread, it'll get jumbled up between different bug discussions very fast. If I then link several bugs to that mess, it's hard for anyone to pick out the bits relevant to any one particular bug.

fenderbendr said:

Maybe you could arrange the bugs in the master table lists in order of importance? For example, with Dr. Dude, it would probably be the mix master multiball camera bug.

Click to expand...

It's possible, but it would involve some work and subjective judgment on my part to determine what qualifies as more important and then keeping the lists in that order. I'll have to think about if there's a relatively painless way of doing that.

just want to add my thanks for a superb job in collating all bugs in one place with great ease of overview, which will significantly assist FS in tracking & hopefully remedying. oh and one more vote to keep 'em locked. thanks Sean.


Tapatalkin' at ya

As someone who worked in the game industry as a QA tester for two years and QA lead for five, I have to say you're doing a bang-up job at this!

A couple suggestions:

- Keep the open/active bugs at the top of the list. The color coding works to an extent, but if the list gets big it will still require more hunting than necessary to find them.

- Assign the open/active bugs a severity rating and sort them accordingly, worst at the top. In my experience this was done either A,B,C or 1,2,3. An "A" or "1" is something that renders the game more or less unplayable, like a crash, stuck camera, and so forth, a "C" or "3" is something quite minor like a small backwards texture, or an innocuous typo, and a "B" or "2" is something in between those extremes; it sounds rather subjective but it gets pretty straightforward once you get used to it, and it's a big help in isolating the issues most in need of fixing.

- If possible, note the version number(s) and platform(s) in which the bug was found and--less importantly for us, but you never know--fixed. This could help FarSight track down the source of a problem, if they're using the usual types of revision tracking on their end...which I'm not convinced they are, but we can always hope!

Fourteen tables down, twelve to go! Everything from DLC Pack # 6 on is live, along with our primary infestations Cirqus Voltaire and Black Knight.

smbhax said:

As someone who worked in the game industry as a QA tester for two years and QA lead for five, I have to say you're doing a bang-up job at this!

A couple suggestions:

- Keep the open/active bugs at the top of the list. The color coding works to an extent, but if the list gets big it will still require more hunting than necessary to find them.

- Assign the open/active bugs a severity rating and sort them accordingly, worst at the top. In my experience this was done either A,B,C or 1,2,3. An "A" or "1" is something that renders the game more or less unplayable, like a crash, stuck camera, and so forth, a "C" or "3" is something quite minor like a small backwards texture, or an innocuous typo, and a "B" or "2" is something in between those extremes; it sounds rather subjective but it gets pretty straightforward once you get used to it, and it's a big help in isolating the issues most in need of fixing.

- If possible, note the version number(s) and platform(s) in which the bug was found and--less importantly for us, but you never know--fixed. This could help FarSight track down the source of a problem, if they're using the usual types of revision tracking on their end...which I'm not convinced they are, but we can always hope!

Click to expand...

Thanks for the support and advice!

I'll sink the fixed/unreproducible/not-a-bug issues to the bottom in a couple of weeks. Right now I'm more concerned with unearthing as much as possible, and that includes giving people a chance to indicate any "fixed" bugs that actually aren't before I throw them back in the depths. After that, I'll do the severity sorting on the remainder.

Added lists for Gorgar, CFTBL, HD and Taxi. That's 18 tables in the can, 8 left. Probably will be a little while on those; busy week ahead for me.

Sean DonCarlos = THE MAN. I am very hopeful FarSight will utilize your hard work to make the game better. Thank you.

Thanks so much for putting these together. Amazingly helpful, and I support the threads being locked.

It woud be great if someone could also do a General User Interface / Game Engine list (probably for each device). It would be good to have a master list of bugs like the fact that the nudge setting on iOS needs to be changed before each game to actually work.

Great job on putting this all together Sean. I wanted to do something like this awhile back, but ultimately decided against it since I already have a limited amount of free time as it is. Everything looks great so far and I'm sure the devs appreciate this as well.

When it was sjggested i thought of sean but didnt wanna lut him kn the spot,,i can think if ni memeber better for the job...and its time amd effort trawling through our anal posts lads

Kudos mynfriend