Joystick Config

[SuPeRMaN]

How can i configere the joystick @@

[Caligo Clarus]

http://www.savingcontent.com/2014/08/09/guide-play-x-wing-tie-fighter-series-on-windows-7-windows-8-windows-8-1-with-an-xbox-xb1-playstation-ps4-controller-flight-stick/

[Horrido]

While not flying...

hit esc key
select 'config joystick'
hold down button
press key.

[SuPeRMaN]

there are some keys that are bind from the start, they can be unbind? looks like 1 key can have 1+ function..

Thanks for the replys!!

[albino1]

I don't think you can change Fire and Roll, at least I wasn't able to. But I could be wrong.

[Osnap]

anyone running into drift problems when flying in the classic version?

[Caligo Clarus]

Recalibrate your joystick in Windows.

[Osnap]

no luck with a recalibration. the drift only occurs during flight. the stick behaves as expected in the menus, mission select screens, etc.

[Osnap]

Problem solved. timed=false variable in dosbox config file in x-wing folder. (I was incorrectly modifying the variable in my local dosbox config file)

[sandogweps]

That SavingContent link is thoroughly unhelpful. When I get into the Calibrate Joystick menu, all I am able to manipulate is the buttons for the ThrustMaster HOTAS X Flight Stick. Will not recognize joystick movements AT ALL, only mouse. Is it wanting to default to the mouse? Or touchpad? I love me some Steam, but when I buy a thing from them, I kind of expect it to just, well, you know, work. Not have to partition a Windows 7 load, not set DOS 3.1 compatibility modes, not dance naked in the waxing moon.

Running Windows 8.1 in Administrator Mode. Have tried Win 95, 98, and XP SP 3 compatibility modes. Have run via the Steam Library and from the .exe icon itself.

Buyer Beware. This one, despite your nostalgic yearning, may cause some issues. Anyone have a semi-sane fix for any of this?

[Caligo Clarus]

Originally posted by sandogweps:

I love me some Steam, but when I buy a thing from them, I kind of expect it to just, well, you know, work. Not have to partition a Windows 7 load, not set DOS 3.1 compatibility modes, not dance naked in the waxing moon.

That's GOG, not Steam.

Are you using the DOS version? Try the Windows version instead.

See here for T.Flight HOTAS, where people say it is working:
http://steamcommunity.com/app/361690/discussions/0/620712364034997593/

X-Wing Special Edition 1998 for Windows is a remake of the original game in the X-Wing vs. Tie-Fighter game engine, which is the game mentioned in the other thread. I'm planning to get a T-Flight in a couple of weeks, so hopefully it can be setup OK.

edit: Actually here is another post indicating the Thrustmaster works with the DOS version Ok (may need calibration for drifting)

Also this guy:
http://www.pcgamesn.com/beginners-guide-to-x-wing-and-tie-fighter-joystick-issues-controls-and-picking-a-version
and this guy:
www.gog.com/forum/star_wars_xwing_and_tie_fighter_series/playing_with_an_x55_rhino_hotas

say to make sure your HOTAS is set as the default controller in Windows first.

[The Patch]

Originally posted by Osnap:

anyone running into drift problems when flying in the classic version?

Originally posted by Osnap:

Problem solved. timed=false variable in dosbox config file in x-wing folder. (I was incorrectly modifying the variable in my local dosbox config file)

Thanks Osnap!
I had the same problem, same solution.

Modified
C:\Program Files (x86)\Steam\SteamApps\common\STAR WARS X-Wing\classic\dosbox_xwing.conf
under the [joystick] section, timed=false

[J-Omega]

Don't mean to necro the thread but I too recently ran into worsening drift and random joystick inputs during the Collector's CD-ROM (condensed floppy - not 1998 rerelease) version only during flight (menus were fine). I'm using the Thrustmaster T.16000m FCS HOTAS and programmed my own scripts and was about to start digging through my code when I came across this. Thank you very much for this. I modified the game's config file to have 'timed=false' and it worked instantly. Ironically, the config file mentions this very issue and given its description there, my guess is that the line changes the game to read analog joystick input as opposed to digital. Guess I should have done troubleshooting like it's 1994! Thanks again!

[tarasis]

Originally posted by J-Omega:

I'm using the Thrustmaster T.16000m FCS HOTAS and programmed my own scripts and was about to start digging through my code when I came across this.

Would you be willing to share your T.A.R.G.E.T. config for the game? I have the same joystick and find the software a little intimidating.

[J-Omega]

Originally posted by tarasis:

Originally posted by J-Omega:

I'm using the Thrustmaster T.16000m FCS HOTAS and programmed my own scripts and was about to start digging through my code when I came across this.

Would you be willing to share your T.A.R.G.E.T. config for the game? I have the same joystick and find the software a little intimidating.

Sorry for the super late response but here is my thread with the links. I have setup a .PDF showing the mapping that you will see in the GDrive as well:

https://steamcommunity.com/app/354430/discussions/0/1760230682460010178/

[damson]

To clear things up, timed=false and timed=true are both valid analog ways of reading out joystick axis values. But depending on cycles setting the joystick might start to drift in game.

Generally what I found is that it's best to use timed=true if using constant cycle settings, like
cycles=27000
and timed=false when setting cycles to values that might change during gameplay, i.e.
cycles=auto or cycles=max

Keep in mind that when you use fixed cycle setting and timed=true you can still make your joystick start to drift by changing cycle count on the fly with CTRL-F11/F12 (default key combo for decreasing/increasing cycle count while DOSBox runs).

But why not just use timed=false for both cases? Well, timed=true is more precise - it yields better resolution for axis readout. You may confirm that in any DOS game that displays axis values during calibration routine.

For example in TFX when using timed=false you will only get around 32 discrete deflection values for entire range of each axis. When using timed=true you will get around 270 discrete deflection values.

Also if you haven't already check out my guide for enabling throttle support in both DOS versions of X-Wing games among other fixes here:

https://steamcommunity.com/sharedfiles/filedetails/?id=1895142633