Touchline Tablet - Pass Maps

Second half displayed below.

(1. Tiles in the touchline tablet have changed without instruction. User changes them back to the prefered view.)

(2. Pass maps both show the Derby pass map, however the title suggests it should be showing one for each team.)

(3. Pass maps show correctly.)

 

(4. Pass maps both show the Derby pass map, however the title suggests it should be showing one for each team.)

(Image too large)

(5. Pass maps both show the Derby pass map, however the title suggests it should be showing one for each team.)

Next match.

(1. Pass maps both show the Derby pass map, however the title suggests it should be showing one for each team.)

(2. pass maps shown correctly.)

(3. pass map shown correctly.)

(4. Pass maps show correctly.)

Game progressed with no changes.

 

Game 3.

(1. Tablet tile needed changing to show both teams pass maps.) 

(2. Pass maps both show the Derby pass map, however the title suggests it should be showing one for each team.)

(3. Tablet tiles changed without reason. Opposition pass map not displayed.)

(4. Pass maps both show the Derby pass map, however the title suggests it should be showing one for each team.)

(5. Pass maps display correctly.)

Same match.

(6. Pass maps both show the Derby pass map, however the title suggests it should be showing one for each team.)

(7. Pass maps shown correctly.)

Next Day - Match 1

(1. Match starts with wrong touchline tablet tiles.)

 

(2. Upon changing the tiles, both pass maps show Derby highlighted, but the graphic is different.)

 

(3. Pre-half time, both pass maps show Derby's pass maps.)

4. After the first highlight of the second half, touchline tablet tiles have changed to not show Preston's pass map.

(78 minutes)

5. Pass maps shows correctly.

6. Match end - Pass maps both show Derby's stats.

Thank you for sharing this one with us. Can you share your pkm/pkm's where you have this happening? It may not be the easiest to reproduce so having games in which its clearly happening always helps our QA team look into it. A guide on how to share your file is available here:

 
 

We believe we've fixed this in one of our past updates now, but do let us know if you spot any further instances.