when i make light mouse movements, the character continues turning despite me not moving my mouse.
demonstration:
https://www.youtube.com/watch?v=TjeJccEFo7k&feature=youtu.be

yall want me to like upload my game?  or just my configs or something?  or might it just be a problem on my side?

You  have a joystick or something connected?
This looks like a thrust control interfering.

i  kind of said that it had already been resolved but i dindt want to be a bother and say that it wasn't actually solved but it wasn't.  i have done a variety of convoluted maneuvers that work by... some voodoo magic idk

i attempted to play my steamapps version which updated to 2.46 without my consent and it worked without the mouselook, but i really don't want to speedrun on it because of the pipe in rickenbacker pod 1 in the way of the optimal route, and didn't want to run some illegal chimera of 2.46 with rick1.mis from my copy of 2.45.

first i moved ss2 from steamapps to my downloads folder so i could try to sourcegear diffmerge all the config files to see what was different.  the things that were different was mostly cosmetic shit and screen resolution, but when i launched my copy of 2.46 in downloads, it also did the mouselook thing!  i concluded that it was because it was in program files that made it work... somehow.  i know it's literally the one thing im not supposed to do but i put a copy of 2.45 in program files, had no write access and therefore it didn't work, put it in steamapps, and then the mouselook thing happened in 2.45 as i named the common steamapps folder WHATTHEFUCKSS2.

i proceeded to name the 2.46 folder "SS2bu" and renamed my 2.45 file in steamapps to SS2.


and that.


of all things


made the mouselook shit go away.

woot
[fetti.gif expired]

It sounds like he may have exceeded the 80 characters max path length. That would explain why moving the game folder around or renaming it changed the behaviour. Program Files is still a bad idea.

When this happened to me it was because of some anti-aliasing setting in cam_ext.cfg. Disabling that setting fixed it for me.