@theol0403 Hello, I'm Theo. The FOV of the Vision Sensor varies depending on you programming software.
In the PROS 3 header files, it's
#define VISION_FOV_WIDTH 316
#define VISION_FOV_HEIGHT 212
It was different before, but I think they changed it to mirror the recommended amount from VCS.
You can think of them as pixels, but I think they are actually arbitrary units.
There are 316 "units" between the left and right FOV of the sensor.
I don't know what changing that number will do, I don't know the maximum hardware resolution of the sensor.
Hope this helps
I think you misunderstand. For a lot of purposes the FoV (the angle the camera sees) is really important to know. Without knowing this, knowing how many pixels you're dealing with may well be insufficient. There are a number of spots where you can find the pixels. But, though noted as FoV in those #define statements, this is really resolution, not FoV. We're waiting on the other piece. The best we've heard yet is from CMU's pixycam, as @Jacob Walter posted and has been posted before. Ideally, VEX will publish the FoV. Next best, someone with a vision sensor will place the camera somewhere and start making physical measurements to determine what the FoV actually is and let us know.