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
psalm8818: I have done EVERYTHING you just described, with the exception of your brand of joystick, and I have ALL the problems you don't, even with a fresh install. So you can sit there and tell me everything is fine and I'm stupid until you're blue in the face...that doesn't change the fact that I have TOTALLY different results following the exact same steps as you have taken
avatar
Antaniserse: Perfect, I believe you 100%... however if everything is the same, including Win 10, and the result are different, what does that suggest you?! it's all the OS fault?
I'm not telling that you are stupid, I'm telling that a) I'm not the only one that got this working and b) *your* Win 10 setup (not THE Win10 setup), has some problem somewhere; sure, it has to be related to the new OS, since it worked on Win7 on the same machine, not denying that, but it is not THE OS alone, and its not the GOG package alone... I am at 3 success on 3 different machines, I can't just be lucky, and I'm not doing anything special, just the above

avatar
psalm8818: Paying customers shouldn't have to jump through all these hoops just for a slim chance that the non-refundable product might possibly work.
avatar
Antaniserse: As far as I know, those titles follows the same 30 day refund policy as the rest of the GOG catalogue.... if you mean that you can't do it anymore because you bought that earlier and you are experiencing the problems only now, well I can undrstand the frustration but, again, that does not mean that if it is not available to you then is non-refundable as an absolute.

avatar
psalm8818: Also, there is no dosbox.conf file in the 98 version (there is not even a DOSBOX folder).
avatar
Antaniserse: No, there is not... his suggestion is indeed only related to the DOS version, which is the one that has no Win10 compatibility issues at all and he's implying it might be a better try on you PC

avatar
psalm8818: There IS a dosbox.cfg file in the 95 version, but there is no way to changed the "timed" setting. It's not a text-based app
avatar
Antaniserse: the .conf files used by DOSBOX are not apps (you are talking about the extra UI tool supplied by GOG, which is not part of DOSBOX proper), they are just plain text files, and you can open them with the text editor of your choice... if you are not OK with that, you can get yourself a more complete UI (eg. D-Fend Reloaded) and import the profile there, you'll find the full range of options available (and it's nice to have for for any other DOS games sold by GOG)

Whatever method you choose, the joystick section should be something like this (works on both X-Wing and TIE DOS titles for me):

[joystick]
joysticktype=4axis
timed=false
autofire=false
swap34=false
buttonwrap=false

This should be fine for most joysticks, and the bulk of the buttons will register natively in the game; you can then use your profiling software for all the other extra buttons/hat switch/throttle remapping

While you are there, if you wanna play TIE 95 in SVGA resolution, the processor section should be similar to

[cpu]
core=dynamic
cputype=auto
cycles=fixed 55000
cycleup=1000
cycledown=1000

and the renderer in the [sdl] section one of these
output=ddraw (this works fine for me)
output=opengl
output=openglnb
Ok I found what you're talking about, but even after making these changes, I STILL get cursor drift when calibrating, absolutely no way to map the throttle on my controller/joystick (best I can do is set the triggers/throttle to full power and 1/3 power, which is vastly inferior to the 98 version, and no better performance than the vanilla settings), or is there any way to remap the fire button (which I use the RB on a gamepad, I use the native fire button for targeting).

I'm sorry, but I simply prefer the 98 version to the 94/95 versions. With the 98 version I am able to map my controller/joystick to the exact same configuration that I have used for 20 years for TIE 98, X-Wing Alliance, X-Wing vs. TIE Fighter, Star Wars Galaxies Jump to Lightspeed, Battlefron 2 (the old one), and virtually every other space combat game I've played. Unfortunately, the 98 version does not function properly in Windows 10 without more tweaks than I'm currently willing to waste time testing and ultimately have not work. I have a new PC on the way, and if I continue to have these issues, then I'll simply uninstall TIE Fighter, go buy the new Battlefront II, and take my custom to Steam rather than GoG in future.
avatar
psalm8818: Ok I found what you're talking about, but even after making these changes, I STILL get cursor drift when calibrating, absolutely no way to map the throttle on my controller/joystick (best I can do is set the triggers/throttle to full power and 1/3 power, which is vastly inferior to the 98 version, and no better performance than the vanilla settings), or is there any way to remap the fire button (which I use the RB on a gamepad, I use the native fire button for targeting).
In DOSBOX all the non-standard remapping needs to be done in your joystick profiler software; there is an integrated remapper but is very clunky, so your T.A.R.G.E.T profiler is a much better UI... even the throttle work with "bands" settings.

You lost me a bit with the "RB gamepad" however.... how many devices are you trying to use, throttle/stick and gamepad together? I'm pretty sure those cannot be read by DOSBOX concurrently, unless you merge them in a virtual joystick
Are you sure those worked like this in TIE 98? Because I just tested mine, and the built in mapping screen does not allow to map controls from two distinct input devices unless i tamper with some external software; it either reads the HOTAS or the Gamepad, whatever I set as the preferred device in JOY.CPL, so there's no (native) way to fire with the pad and control with the stick

avatar
psalm8818: I have a new PC on the way, and if I continue to have these issues, then I'll simply uninstall TIE Fighter, go buy the new Battlefront II, and take my custom to Steam rather than GoG in future.
Well, good luck with the new PC and also good luck with Steam that if you are interested in retro compatibility for legacy games; much of their retro catalogue is based on the same packages and tweaks as GOG, in some cases you'll even find remains of the GOG installation files, so that would hardly make a difference
Post edited October 09, 2017 by Antaniserse
avatar
psalm8818: Ok I found what you're talking about, but even after making these changes, I STILL get cursor drift when calibrating, absolutely no way to map the throttle on my controller/joystick (best I can do is set the triggers/throttle to full power and 1/3 power, which is vastly inferior to the 98 version, and no better performance than the vanilla settings), or is there any way to remap the fire button (which I use the RB on a gamepad, I use the native fire button for targeting).
avatar
Antaniserse: In DOSBOX all the non-standard remapping needs to be done in your joystick profiler software; there is an integrated remapper but is very clunky, so your T.A.R.G.E.T profiler is a much better UI... even the throttle work with "bands" settings.

You lost me a bit with the "RB gamepad" however.... how many devices are you trying to use, throttle/stick and gamepad together? I'm pretty sure those cannot be read by DOSBOX concurrently, unless you merge them in a virtual joystick
Are you sure those worked like this in TIE 98? Because I just tested mine, and the built in mapping screen does not allow to map controls from two distinct input devices unless i tamper with some external software; it either reads the HOTAS or the Gamepad, whatever I set as the preferred device in JOY.CPL, so there's no (native) way to fire with the pad and control with the stick

avatar
psalm8818: I have a new PC on the way, and if I continue to have these issues, then I'll simply uninstall TIE Fighter, go buy the new Battlefront II, and take my custom to Steam rather than GoG in future.
avatar
Antaniserse: Well, good luck with the new PC and also good luck with Steam that if you are interested in retro compatibility for legacy games; much of their retro catalogue is based on the same packages and tweaks as GOG, in some cases you'll even find remains of the GOG installation files, so that would hardly make a difference
No, I'm only using one or the other. Why would I be trying to use both at the same time? Is that your opinion of me, based of what you've read, that I'm THAT stupid? Quit TRYING to find stuff to call me out on.

I'm done trying to troubleshoot this. I shouldn't have to bend over backwards and forwards to get these games to work properly, and none of these tweaks work FOR ME. And frankly, the "tech support", while appreciated, isn't all that great.
avatar
psalm8818: No, I'm only using one or the other. Why would I be trying to use both at the same time? Is that your opinion of me, based of what you've read, that I'm THAT stupid? Quit TRYING to find stuff to call me out on.
It's not that i want to call you out, but in the same sencence you mentioned throttle remapping, a "native" fire button and a gamepad trigger; plus, you talked above your tries with the T1600 stick and now of your "20 years old" habitual configuration, so I assumed we were still talking about joysticks and not gamepads with analog and triggers that were hardly commonplace 20 years ago!

Since you seem to have problems with just about EVERYTHING on EVERY version of the game, I was starting to believe you were trying some unconventional setup and that could be the core of the issue... Now that we have established that you are not, and are just trying using a gamepad, then I can only say that the RB can be mapped just as any other input provided you help yourself with some joystick tool; that is the nature of the DOSBOX environment with modern controllers, not an inherent issue with TIE or the OS you are using.

While we are here, note that you have to do a different approach when mapping analog triggers and a proper throttle to the in-game throttle, since one has a single, fixed resting point on the center, the other a variable one on the same axis, so you can't go back and forth without having two different profiles in your mapping software.

Even in the 98 version, were the throttle is supported natively, you can't simply substitute the one from a stick with with gamepad triggers, because they do not behave as expected (for example you can't mantain full power without constant pressing), and you still need help with external software, so that also confused me when you stated above that throttle mapping in 95 is "vastly inferior" to 98: joystick throttle, yes, gamepad throttle, same issues

I don't think there is anything else that can be done here; even in the worst scenario with the Win32 version, the DOS based versions are the ones that almost invariably just works, and yet you have all sorts of issues with them too... so cross your finger on the new PC, try the games as soon as possible before introducing some more variables in a clean environment, and if that isn't working either, well...
Post edited October 10, 2017 by Antaniserse