Page MenuHomeFeedback Tracker

Periscope depth and camera position error
Closed, ResolvedPublic


SDV periscope camera position seems to be on the antenna mast instead of the periscope mast. Due to this error the periscope depth is incorrect (too deep). I believe the periscope camera should be moved to a position closer to the actual periscope mast head and the vehicles "periscope depth" should be adjusted accordingly.


Legacy ID
Steps To Reproduce

Choose maintain periscope depth in the sdv and observe the vehicle from 3rd person view.

You will see that the antenna is above water but the periscope is not.

The current setup allows the camera to see above water but the periscope mast is still visibly below the water line.

Event Timeline

sarlac edited Steps To Reproduce. (Show Details)Jul 7 2013, 12:56 PM
sarlac edited Additional Information. (Show Details)
sarlac set Category to Visual-Vehicles.
sarlac set Reproducibility to Always.
sarlac set Severity to None.
sarlac set Resolution to Open.
sarlac set Legacy ID to 2480596807.May 7 2016, 3:20 PM
Bohemia added a subscriber: sarlac.Jul 7 2013, 12:56 PM
b101uk added a subscriber: b101uk.May 7 2016, 3:20 PM
b101uk added a comment.Jul 7 2013, 5:58 PM


it seems like somehow they (Fireball) confuse "3d periscope head" with "3rd person camera" and tagged an older lower numbered post as somehow a "duplicate" of a newer higher numbered post defying logic and the English language, so I can only guess they are not interested in fixing it even IF you can get a "developer" (pettka) to agree with logic.

Even asked to have it reopened by email and got a reply back saying it's a duplicate! (CSR Kryssar) even though I said I have more proof from photos and the manufacture who sell them worldwide to military's (that they are permitted to sell to), can even tell the length it should extend to! which are ALL inappropriate in a topic specific to “3rd person camera” position.

I'll look into it.

What more do you need?

Mass closing ancient tickets with no activity this year; assume fixed or too trivial etc.

If this issue is still relevant in current dev build, please create a new ticket referencing this one and request for it to be re-opened.