I upgraded to betaflight 3.2 from 3.1.1 and went through and set everything up like usual. Everything looks fine on recievers tab when I move the 3d model around and all that but when I arm the quad and try to fly, every single stick movement acts like nothing but throttle... yaw is throttle, roll and pitch are throttle.. and throttle is throttle lol what's going on? All I did was flash to 3.2.

  this ones weird.  Sorry I don't have an answer but am curious to see what it is.

Especially strange since everything acts normal on the 3d model.

What FC do you have and what firmware did you upgrade to?

definitely a strange one.

When you said "the model" you mean the one in the preview box on the Receiver tab right?

When you say that they all act like throttle, do you mean that Roll, Pitch, and Yaw are responding by putting the throttle at 50% because they are centered, or is it any time you give any stick inputs moving them from center? If it's when moving them from center does it happen in both up and down / left and right directions?

Also do each of the input bars on the left respond as expected? Roll, Pitch, Yaw specifically or are they acting funny in any way?

and finally, for some specifics on how you upgraded... did you do a full chip erase? If you did, did you bring your settings over via CLI or did you just make note of the settings and return them to your preferences manually?

I'm using the Piko blx f3 micro board and yes the model in the preview box in receiver tab. You know when you have throttle at 0 and then you throttle up and all the motors increase along with the stick as they should? Well all of the other axis do the same thing as throttle lol. If I yaw to the left it acts as if I throttled up to 100% or maybe only 50% but I didn't max any axis to test it xD same if i yaw to the right or pitch up or down or roll left or right, all of them act as if they are simply the throttle stick instead of the other corresponding sticks. It's like all the channels are sending their data to the same throttle channel or something even though in receiver tab everything looks correct. I did a full chip erase and I manually went through the GUI default settings and adjusted accordingly. Which was only my PIDs, modes, switched uart2 to smart port, disabled accel, turned on telemetry, dshot 300, CLI command that enables the dshot mod for the piko and rotated my FC -90º since I have mine turned in order to access the usb.

Also something new I noticed after going to 3.2 was when I arm the quad, the motors spin up to the idle speed but the gyro no longer is in effect. They just statically spin. So now I have to add air mode as a mode to set after I arm in order for the quad to act correctly with the gyro and pids all working in order to fly.

If your receiver tab acts normally then I guess I have to draw the conclusion that your receiver is getting the correct stick input.
If your quadcopter is then not acting accordingly I'd say there is something strange in your motor mix.
Could you check what quadcopter type is selected in the config tab?
Additionally, check if a customer motor mix is active, and set is manually if needed.

In CLI:
mixer QUADX
save

If that doesnt work set is completely manually

In CLI:
mixer custom
mmix reset
mmix 1 1.000 -1.000 1.000 -1.000
mmix 2 1.000 -1.000 -1.000 1.000
mmix 3 1.000 1.000 1.000 1.000
mmix 4 1.000 1.000 -1.000 -1.000
save

So I tried the:
mixer QUADX
save

after reboot tried again and they're still all throttle.

I then tried the manual way, copy pasted

mixer custom
mmix reset
mmix 1 1.000 -1.000 1.000 -1.000
mmix 2 1.000 -1.000 -1.000 1.000
mmix 3 1.000 1.000 1.000 1.000
mmix 4 1.000 1.000 -1.000 -1.000
save

After reboot it shows the block 3d model on setup tab now with the "custom" mix instead of the usual quad model and the motors won't finish the beeps when plugged in. It beeps the first 3 but they are supposed to beep two more times right after and they will not now. They won't spin up on arm anymore either.

Alright so I went back to the github for betaflight and downloaded the 3.2 release once more for the piko blx and I noticed that the names weren't the same as the previous download from few days ago.

betaflight_3.2.0_FF_PIKOBLX-196-ce824a60d old
betaflight_3.2.0_FF_PIKOBLX-187-649ccd7c7 new

Flashed it with that one and it's working fine again lol... Thanks for all your help guys! Guess they maybe changed the file on the site or something I dunno.

Good to hear it was solved! Enjoy!