It affects our code preformance.
We do and we calibrate it but it still doesnāt do what its supposed to do.
We are a VEXU team, and we had a similar problem at our last competition. When we ran our skills auto or match auto using the remote, the practice switch, or the field controller that looks like a v5 brain, it worked. Only when we plugged into the field switches for a match did it not work. Our robot would drive to random positions on the field. We are using optical sensor odometry, and after getting help from another VEXU team, we fixed the problem by getting rid of the competition_initialize function in PROS since we were already using the initialize function. Basically, the initialize function runs when the program is run, and the competition_initialize runs when the remote is plugged into the field controller. This double initialization was messing up our starting offsets for our odometry somehow. I still donāt know why it didnāt do this with the practice switches, but our problem is solved now.
These are old topics, but worth reading through.
and this.