[Sumo2000]

I searched but couldn't find anything on this topic. I'm using a Thrustmaster T-16000 which the game recognizes to a limited degree. The hat works, all the buttons and the roll/twist works. The X&Y axis is not responsive. I can remap it in options and it senses the movement but once I'm in flight there's nothing. Not sure about the throttle since I can't get to that part of the briefing mission.

Anyone else run into this?

[AdmiralRalwood]

FSO currently can't recognize more than a certain number of joystick axes (I can't recall the exact number off of the top of my head). This should be fixed after moving to SDL2 for handling input, which is happening Soon™.

[deathspeed]

That's odd.  It's not a HOTAS, and you don't mention using pedals or anything.  It's a basic joystick, like a MS Sidewinder or Logitech Wingman.  My old Sidewinder has just X-Y-roll axes, throttle, hat, and 8 buttons, and it works fine.

You might try setting the joystick as the preferred device in Windows.  In Windows 7, go to start -> devices and printers, then right click your joystick and select game controller settings. Click advanced, select your joystick from the drop-down, then click OK back out of everything.



EDIT:  If you have a wheel, gamepad, or other controller, you might want to unplug them before opening the launcher.  Maybe one of them is causing interference.  My Saitek Gaming keyboard keyboard even causes issues with some games, like Need for Speed: Hot Pursuit.

[Sumo2000]

That's odd.  It's not a HOTAS, and you don't mention using pedals or anything.  It's a basic joystick, like a MS Sidewinder or Logitech Wingman.  My old Sidewinder has just X-Y-roll axes, throttle, hat, and 8 buttons, and it works fine.

You might try setting the joystick as the preferred device in Windows.  In Windows 7, go to start -> devices and printers, then right click your joystick and select game controller settings. Click advanced, select your joystick from the drop-down, then click OK back out of everything.



EDIT:  If you have a wheel, gamepad, or other controller, you might want to unplug them before opening the launcher.  Maybe one of them is causing interference.  My Saitek Gaming keyboard keyboard even causes issues with some games, like Need for Speed: Hot Pursuit.

I've set it as default for older games in devices and printers. I play Freespace 2 (which requires the same settings) and it works fine, just not in Diaspora.

[AdmiralRalwood]

I've set it as default for older games in devices and printers. I play Freespace 2 (which requires the same settings) and it works fine, just not in Diaspora.

Copy your FSO executable and pilot file (it's in the /data/players/ folder with a .plr extension) to your Diaspora folder and try running that.

[Sumo2000]

I've set it as default for older games in devices and printers. I play Freespace 2 (which requires the same settings) and it works fine, just not in Diaspora.

Copy your FSO executable and pilot file (it's in the /data/players/ folder with a .plr extension) to your Diaspora folder and try running that.

Just tried both, still no X or Y axis at all.

[AdmiralRalwood]

I've set it as default for older games in devices and printers. I play Freespace 2 (which requires the same settings) and it works fine, just not in Diaspora.

Copy your FSO executable and pilot file (it's in the /data/players/ folder with a .plr extension) to your Diaspora folder and try running that.

Just tried both, still no X or Y axis at all.

Are you selecting the copied pilot file? And are you sure it works when playing FSO without playing Diaspora?

[Sumo2000]

I've set it as default for older games in devices and printers. I play Freespace 2 (which requires the same settings) and it works fine, just not in Diaspora.

Copy your FSO executable and pilot file (it's in the /data/players/ folder with a .plr extension) to your Diaspora folder and try running that.

Just tried both, still no X or Y axis at all.

Are you selecting the copied pilot file? And are you sure it works when playing FSO without playing Diaspora?

Yes on both counts. They do appear to use a different launcher though so maybe that keeps this solution from working right?

[AdmiralRalwood]

I've set it as default for older games in devices and printers. I play Freespace 2 (which requires the same settings) and it works fine, just not in Diaspora.

Copy your FSO executable and pilot file (it's in the /data/players/ folder with a .plr extension) to your Diaspora folder and try running that.

Just tried both, still no X or Y axis at all.

Are you selecting the copied pilot file? And are you sure it works when playing FSO without playing Diaspora?

Yes on both counts. They do appear to use a different launcher though so maybe that keeps this solution from working right?

Are you using Launcher 5.5g for FSO? If so, you might also try copying it (Launcher.exe) and its settings (launcher6.ini) to your Diaspora folder and running it through that.

[Sumo2000]

I've set it as default for older games in devices and printers. I play Freespace 2 (which requires the same settings) and it works fine, just not in Diaspora.

Copy your FSO executable and pilot file (it's in the /data/players/ folder with a .plr extension) to your Diaspora folder and try running that.

Just tried both, still no X or Y axis at all.

Are you selecting the copied pilot file? And are you sure it works when playing FSO without playing Diaspora?

Yes on both counts. They do appear to use a different launcher though so maybe that keeps this solution from working right?

Are you using Launcher 5.5g for FSO? If so, you might also try copying it (Launcher.exe) and its settings (launcher6.ini) to your Diaspora folder and running it through that.

I was able to launch it with Launcher 5.5 but it still had the same problem. Is there a log file that might show the issue or something like that?