Download
Firstly, the name of my flight stick in the Launcher -> Audio/Joystck tab is incorrectly recognised. It says "PC joystick driver from M company" (translation from polish). The joystick X and Y axes didn't worked initially, but when I turned off the mouse in the options it started to work. Checked if this was the case in WCSPrologue and when the mouse is on you still can control the craft with the stick. Don't know if it is a new feature - just pointing it out.
damson wrote:Firstly, the name of my flight stick in the Launcher -> Audio/Joystck tab is incorrectly recognised. It says "PC joystick driver from M company" (translation from polish). The joystick X and Y axes didn't worked initially, but when I turned off the mouse in the options it started to work. Checked if this was the case in WCSPrologue and when the mouse is on you still can control the craft with the stick. Don't know if it is a new feature - just pointing it out.
That is working as designed. The joystick AND mouse functionality can lead to problems and doesn't make sense anyway.
We'll also further improve the mouse steering in the next beta iteration.
Also your joystick is correctly recognized. Most joysticks are recognized as standard input devices and the standard Microsoft driver is used for them. So that's just fine.
About the mouse again... Are you saying that Mouse control was turned on by default?
Yes it was. Maybe that should be changed.
One thing though - when I started the WCSBeta for the first time I didn't select the joystick control in the launcher (due to the strange name), so maybe if you don't select joustick the mouse is used as default control device?
damson wrote:One thing though - when I started the WCSBeta for the first time I didn't select the joystick control in the launcher (due to the strange name), so maybe if you don't select joustick the mouse is used as default control device?
Possible. I'll check what's the default, don't worry.
Regardless of what Joystick you select the Beta defaults to mouse control. Happened with both the X52 and 360 wireless controller. I almost thought that the joystick interface had failed and posted a bug about it myself. 😂
The system works well though I can even bind the second stage of the trigger on my X52(button 15)with no trouble. (have it set to increase gun power for those moments when you need it) Also while I am on energy management increasing engine power seems to have no effect on velocity. Was this intended? I can see how it could be a side effect of switching to fuel based afterburner.
tehTwitch23 wrote:Regardless of what Joystick you select the Beta defaults to mouse control. Happened with both the X52 and 360 wireless controller. I almost thought that the joystick interface had failed and posted a bug about it myself. 😂The system works well though I can even bind the second stage of the trigger on my X52(button 15)with no trouble. (have it set to increase gun power for those moments when you need it) Also while I am on energy management increasing engine power seems to have no effect on velocity. Was this intended? I can see how it could be a side effect of switching to fuel based afterburner.
I changed it so that Mouse Steering is OFF by default.
About the energy level. Yes that is intentional since in Wing Commander going beyond the default level didn't increase maximum speed either.
My X52 isn't working with mouse steering off either; it worked in Prologue, but I had to select Force 1 for it to happen, and there's no such option in the beta
Buttons also react ok in the Windows control panel. I'll see if I can duplicate it on a different computer.
EDIT: Works as intended in Win7, so it's an OS issue, not a bug.
Citizen Bleys wrote:My X52 isn't working with mouse steering off either; it worked in Prologue, but I had to select Force 1 for it to happen, and there's no such option in the betaButtons also react ok in the Windows control panel. I'll see if I can duplicate it on a different computer.
EDIT: Works as intended in Win7, so it's an OS issue, not a bug.
Good to know. But such issues can rarely be a bug. The game simply accesses input devices via direct input. As long as Windows correctly recognizes the joystick, so should the game.
KeldorKatarn"]Agreed that it should; I have no idea why it doesn't, but I haven't given up on it. When I fix it, I'll report back in on how I did it just in case it's of any use. I'll make a second Windows partition just for WCS if I have to.