Inherent y drift depending on order of calls in the python script

[amaalo2]

Similar to Git Issue #2851, I am experiencing Y drift depending on the order of the calls.

`import setup_path
import airsim
import pprint
import time

for i in range(10):

client = airsim.MultirotorClient()
client.reset()
client.confirmConnection()
client.enableApiControl(True)
client.armDisarm(True)
client.takeoffAsync().join()


while True:
    collision_info = client.simGetCollisionInfo()
    client.enableApiControl(True)

    #Move Straight
    client.moveByVelocityZAsync(1, 0, -2, 1).join()

    quad_state = client.simGetGroundTruthKinematics().position
    pos_x = quad_state.x_val
    pos_y = quad_state.y_val
    pos_z = quad_state.z_val

    print(pos_x,pos_y,pos_z)

    if collision_info.has_collided:
        print(i)
        print("Collision at pos %s, normal %s, impact pt %s, penetration %f, name %s, obj id %d" % (
            pprint.pformat(collision_info.position), 
            pprint.pformat(collision_info.normal), 
            pprint.pformat(collision_info.impact_point), 
            collision_info.penetration_depth, collision_info.object_name, collision_info.object_id))               
        break

`

This is the code used to run a drone in a straight line.
Specifically, using the lines below from the code above in this order:

collision_info = client.simGetCollisionInfo()
client.enableApiControl(True)

I get much different results in terms of Y drift if I swap those lines around.

client.enableApiControl(True)
collision_info = client.simGetCollisionInfo()

I do not believe the order should matter here, and I do not understand what is causing this drift.