Buy a modern computer?

2400 mghz should be able to run tie fighter I would say

1. read the Readme
2. *really* read the Readme (because if you don't you probably won't get much help here) 🙄
3a. open the file dosbox.conf in your DOSBox directory, look for the entry "core=auto" and change it to "core=dynamic".
3b. change the entry "cycles=auto" to "cycles=max"

it works 😀

thanx 😀

That's weird. Tie Fighter should work fine with core=auto and cycles=auto.

no - with "auto" - it is slow - very slow 🙁

Yeah, setting "auto" cycles doesn't work very well with this game. I'm playing the collector's CD-ROM, and had to use "max" cycles to make it work well. Another speed boost can be obtained by choosing the fastest "output" mode (depends on the system).

I'm using Gulizoka's build on Windows with the "direct3d" output method, and the game runs perfect in SVGA and full details on my crappy P4/2.6Ghz. After some heavy mapper config, i can play the game with a XBox gamepad, only using the keyboard occasionally for stuff like the map or the "Goals" display. Now, if only the missions weren't so frustratingly difficult... (;

Oh, and btw: the correct game name is "TIE Fighter" (_T_win _I_on _E_ngines).

game is probably a real mode game.

Ah, you and your technical terms! (; Yes, it's using the DOS4GW extender. Replacing this with DOS/32A makes it run a bit more smoothly, too.

If it's using DOS4GW, it's a protected mode game then.

hmm then max and auto should be identical. Maybe they do some timing when still in real mode then.

I might have this game at home. Will check later.

I guess it's version dependent. The first TIE Fighter version is probably real-mode (like its X-Wing predecessor), but the Collector's CD-ROM (which I have) is protected-mode.

I can confirm that the first release of Tie Fighter (Disks) runs very slow.
You need to set cpu=dynamic and cycles=max.

Then (depending on your PC's horsepower) it runs absolutely fluid.

The differences between the fist release (Disks) and the CD-ROM Collectors Edition?

Well, i quote mobygames here:

Beside the new missions, some technical improvements are made in the game:

* improved screen resolution to SVGA (640*480)
* added new cut scenes
* full voice mission briefings and radio calls (the so called "Talkie" version)
* improved the interactive mission briefing

Hope that sums it all up. 😁

Addict,
Could you post the DOSBox joystick settings and the mapper file
you used to run TIE Fighter with XBox controller?

I am myself trying to do the same for TIE Fighter Collector's CD Edition and the results are far from satisfactory (no hat mapping, poor calibration)

thanks,
Al

I can post the files (have to look for them, i've just recently switched to Vista and couldn't get XBCD working yet), but i doubt they'll be of much use. I've first customized the XBCD settings heavily, and then started to change DOSBox' mapping. This means you'll need the same XBCD version i was using, the XBCD config file (i think XBCD profiles can be exported, but i'm not sure), and the DOSBox mapper file. The result would be my personal config, which you'd have to "learn". If you want to go that route just tell me, i'll upload the files.

The other option would be to enable you to create your own mapping (it's easy once you understand how the mapper is working). What is your problem with mapping? Your calibration problem can probably be solved by changing the ""timed" parameter in dosbox.conf. If you're still having trouble with calibration, try running the game with a fixed cycle count.

Addict,
thanks for the reply. I guess I should start by switching to XBCD driver, as I I've been using the MS default this far (and not being quite happy with it).

I managed to do some remapping Ok, it's really not an issue, but the calibration turned out tricky. Using

1[joystick]
2joysticktype=2axis
3timed=false
4autofire=false
5swap34=true
6buttonwrap=false

is the only option with my current setup (w. MS legacy driver that is) that works at all. Even with that, TIE in DosBOX .072 gets usually messed up with the calibration and there is remaining jitter. And what's more fun, just toggling the main axes seems to randomly trigger BUTTON1 (no explicit mapping according to Dosbox maper) which is not very nice.

I will try with XBCD and fixed cycles first. Thank you for the tip anyhow.

Al

Yeah, you should check out XBCD. Just make yourself familiar with it and post specific problems or questions once you're set. All i can say now is that i don't have any problems with the game. It doesn't loose calibration, and i can map every button and axis on the controller to my liking in DOSBox.

Quick return to the old issue as I finally got it all together:

I think there are some many potential gotchas in the process that I wrote I guide to help setting up this combination:

http://iki.fi/lassial/guides/computers/Play_T … hter_in_Windows

This page also links to an example configuration files for XBox360 controller using XBCD and DOSBox together, including custom mappings for both XBCD and DOSBox mapper.

aL