Plunge View and Camera Differences?

[netizen]

Why is there such a huge difference between the plunge cam viewing angles between the mobile version of TPA and the Steam build?

On the mobile version of TPA a player can, in view 1, still see most if not all on some tables, see the plunger move and use the hash marks to gauge skill shots without needing to use view 2. However, on the Steam build view 1 has the player looking so low that you cannot even see the plunge lane on most tables, let alone have any base for making skill shots short of only using view 2. Besides the lack of ability to make skill shots due to the view differences, there is the question of why the views are so low in comparison, and there is no consistency in the viewing angles across the platforms.

Here are both Android and PC in Plunge View 1, notice how vastly different they are. For all intents and purposes they should have the same viewing angles, no? This table is the most similar in the viewing angle of the 2 platforms.

Mobile - Android in Landscape

Steam - a windowed view from my POS laptop

 

[Baron Rubik]

Why are the 'in game' camera angles so different across tables just on one platform? (Android in my case).

I always try to get the same angle for play in portrait. On some tables like Victory it'll be camera angle 3, on others the same angle will be camera 2, on TZ it's camera 1.

I appreciate different tables are different widths, but this should be handled with zoom.
The angle should be a set angle per camera setting across each table and be consistent.

 

[Jeff Strong]

Why are the 'in game' camera angles so different across tables just on one platform? (Android in my case).

I always try to get the same angle for play in portrait. On some tables like Victory it'll be camera angle 3, on others the same angle will be camera 2, on TZ it's camera 1.

I appreciate different tables are different widths, but this should be handled with zoom.
The angle should be a set angle per camera setting across each table and be consistent.

I often wonder about this too. The cabinet height and angle also varies based on the era and manufacturer, but they should be able to copy/paste the camera values from one similar pin to another.

 

[norbert26]

Why are the 'in game' camera angles so different across tables just on one platform? (Android in my case).

I always try to get the same angle for play in portrait. On some tables like Victory it'll be camera angle 3, on others the same angle will be camera 2, on TZ it's camera 1.

I appreciate different tables are different widths, but this should be handled with zoom.
The angle should be a set angle per camera setting across each table and be consistent.

one of the issues i have is cam can not be set for each table. Changing the CAM changes the view on all tables. On steam its a real PITA to change the cam view. First i have to plunge the ball into play. Then you have to get the ball cradled and start hitting "C". This was such a PITA i just live with cam 1 for better or worse.

 

[netizen]

Why are the 'in game' camera angles so different across tables just on one platform? (Android in my case).

I always try to get the same angle for play in portrait. On some tables like Victory it'll be camera angle 3, on others the same angle will be camera 2, on TZ it's camera 1.

I appreciate different tables are different widths, but this should be handled with zoom.
The angle should be a set angle per camera setting across each table and be consistent.

I tried asking that a while back to be greeted with the FS cone of silence

Perhaps by showing the platform differences and how it affects game play there might be an answer forthcoming, then it can be narrowed down to getting consistent views, and in a best case discrete individual table defined settings.

 

[haj]

I so want camera setting saved par table and shared angle and distance among all the tables, and say 8 different angles so most people would find one to suit.