So I actually have the GoG version of Wing Commander 3, but I'm using the "patch" posted here that turns it into the Kilrathi Saga version.
It's been running quite well for me except for some odd behavior with the joystick. Basically if the joystick is centered, moving slowly the center position for slight aim adjustments causes the ship to go in the opposite direction for a brief moment. I.e. pulling the stick back actually causes the ship to pitch down a tiny bit. Pushing right causes a tiny turn to the right. Once I'm sufficiently out of the deadzone area, the ship moves as expected. However, this problem makes small aim corrections extremely difficult.
My joystick is a Logitech Extreme 3D Pro and I would be willing to chalk it up to back behavior with the stick itself, but I downloaded a joystick test problem that graphs movement, and I see no such bad behavior when leaving the center position there. Nor have I experienced this problem in Freepsace 1 & 2 played on the same stick.
So I'm thinking it's something with either WC3 or the KS version specifically. Has anyone else encountered this? Know a fix?
It's been running quite well for me except for some odd behavior with the joystick. Basically if the joystick is centered, moving slowly the center position for slight aim adjustments causes the ship to go in the opposite direction for a brief moment. I.e. pulling the stick back actually causes the ship to pitch down a tiny bit. Pushing right causes a tiny turn to the right. Once I'm sufficiently out of the deadzone area, the ship moves as expected. However, this problem makes small aim corrections extremely difficult.
My joystick is a Logitech Extreme 3D Pro and I would be willing to chalk it up to back behavior with the stick itself, but I downloaded a joystick test problem that graphs movement, and I see no such bad behavior when leaving the center position there. Nor have I experienced this problem in Freepsace 1 & 2 played on the same stick.
So I'm thinking it's something with either WC3 or the KS version specifically. Has anyone else encountered this? Know a fix?