It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
damson: @Fuglseth
could you post your [joystick] settings from conf file (joysticktype, timed, swap34)? How many axis does your joystick have (X,Y,throttle,rudder?).

@maxpacker
I never used frontend with dosbox. Does it changes the config settings on the fly (while dosbox is running)? That could be the problem. Long time ago while trying to get Wing Commander 3 working on DOSbox I stumbled upon joystick issue that caused calibration problems (drifting etc.). I found a solution to change timed value in dosbox.conf file from false to true. But the important thing I also noticed - that this only worked when the value was set in conf file. So for instance if the value was set to false and I run DOSbox and changed the value from DOSbox command prompt (you can do that) I had still problems in the game as if the value wasn't changed properly. So my suspicion is that if the frontend changes the config values similiarly (on the fly while dosbox is running) that caouses your problem. Try using dosbox without frontend, set the joystick values accordingly in the conf file and then run Tie Fighter and check if your joystick work as in GOG's version.
Thanks! this helped me figure out the problem. It was the custom keymapper file that the gog version comes with, once I pointed D-fend reloaded to that file the joystick started working. The file is called mapper-0.74.map. I had to rename it to a .txt file first.

I use a frontend so I can use a special build of dosbox with extra D3D shaders and other options not available in the version bundled with the installer.
So to apply the patch I have to download DosBox? There is no way to just apply this patch via Windows?

I have an old Microsoft Sidewinder Pro, I have the same non-detection issue at the start (it detects in mission). But even after calibrating in mission its wonky half the time with pulling in some random direction. Also menus are basically un-navigatable as the cursor keeps jumping around. I tried messing with the config file but nothing did anything.
avatar
ilves: So to apply the patch I have to download DosBox? There is no way to just apply this patch via Windows?

I have an old Microsoft Sidewinder Pro, I have the same non-detection issue at the start (it detects in mission). But even after calibrating in mission its wonky half the time with pulling in some random direction. Also menus are basically un-navigatable as the cursor keeps jumping around. I tried messing with the config file but nothing did anything.
Yes, this is a DOS-era patch. You can try to run it via Windows, but you'll just see an error. Fortunately, its relatively easy to run with DOSBox. Just mount the folder where TIE Fighter CD (1995) is installed and then run the TIECDJOY .exe (make sure to copy to that folder!).
FYI: Depending on windows version and security settings, you may have to use the "Run as administrator" option in order for dosbox to actually be able to change the file that it unpacks. Otherwise, it just won't have permission to write to the file.
avatar
damson: @Fuglseth
could you post your [joystick] settings from conf file (joysticktype, timed, swap34)? How many axis does your joystick have (X,Y,throttle,rudder?).
avatar
Fuglseth: The settings I started with are the same as the defaults:
2axis
timed false
autofire false
swap34 true
buttonwrap false

Tried playing around a bit with the timed and swap34 settings, without any luck.

The stick is a Cyborg EVO (so, X, Y, throttle, rudder and a hat switch in addition to a ton of buttons)
Check the Gamecontroller panel in Windows and make sure the T.16000.M is the prefered device or simply unplug all other controllers that might interfere.
avatar
Strijkbout: Check the Gamecontroller panel in Windows and make sure the T.16000.M is the prefered device or simply unplug all other controllers that might interfere.
Hey, that did the trick.

Thanks a bunch.
avatar
Strijkbout: Check the Gamecontroller panel in Windows and make sure the T.16000.M is the prefered device or simply unplug all other controllers that might interfere.
avatar
Fuglseth: Hey, that did the trick.

Thanks a bunch.
No problem, what I meant to say was your Cyborg not T.16000M, but you figured it out anyway. :^)