Free Allegiance Forums

I am fooling around with input1.mdl, trying t get Allegiance to recognize joy 0 z axis. As an experiment, could someone who has ANY joystick with joy 0 z axis mapped to the game throttle please copy the bottom section of text from their input1.mdl file here for comparison? Mine looks like:

numericValuesNew =
[
(0, 0),
(0, 1),
(0, 3),
(0, 2),
(0, 4),
(-1, 0)
];

The line "(0,2)," is the culprit with the x45.

My input file is identical with an X52Pro. I believe it uses the Z-axis, but I didn't look too closely since it works as-is.

As an alternative... *LINK*

This article lists two options and I've had success with both.

FlingPu wrote:QUOTE (FlingPu @ May 24 2007, 01:19 AM) My input file is identical with an X52Pro. I believe it uses the Z-axis, but I didn't look too closely since it works as-is.

As an alternative... *LINK*

This article lists two options and I've had success with both.

Where can I get this X52Pro input file? Could you copy the bottom section from your input1.mdl here for me to see?

I looked at those two other options that you linked to, but #1 is not what I want, and #2...well, I'm just concerned about whether that hacked driver might mess up my controls for other games that work perfectly fine at the moment. I may try it, but it's a last resort.

Thanks!

x52 works fine with Alleg. The x45 doesn't. There are some topics somewhere in here about it and some links to try and get it to work. Alas I haven't tried it myself, too lazy, and have wound up using one of the knobs for speed for the past however many years now.

If you get it to work please tell me. And as simple as possible!

GibGezr wrote:QUOTE (GibGezr @ May 24 2007, 02:22 PM) Where can I get this X52Pro input file? Could you copy the bottom section from your input1.mdl here for me to see?

I looked at those two other options that you linked to, but #1 is not what I want, and #2...well, I'm just concerned about whether that hacked driver might mess up my controls for other games that work perfectly fine at the moment. I may try it, but it's a last resort.

Thanks!

There are other games?! /blink.gif" style="vertical-align:middle" emoid=":o" border="0" alt="blink.gif" />

Hmm, the last time I checked, it was (0,2), now it's (0,7). Weird. I think when I use the training room for testing, it remaps my keys. Anyway, I mistyped my last post...I have an X52Pro and it's settings were identical to what you posted now they're not. /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />

Here's the comparison of the default settings and my current setting...

Default setting: After setting the in-game throttle setting with the X52Pro: There are no other changes since I use a profiler to map the buttons to default keys.

I previously used the X45. I tried the Option #1, and didn't like it. I tried option #2 and used that until the joystick snapped, was repaired, broke again, lost some buttons, and it's now retired.

Hmmm.

Fiddling with input1.mdl didn't get me anywhere, so I opted for option #2...but AFTER I uninstall the Saitek drivers, I find that http://xdprofile.freebirdswing.org/ is down

I did manage to get Dhauzimmer's Drivers from a google cache link to an ftp, but the profiler isn't there.

Anyone know of an archive for Dhauzimmer's stuff?

Well, option #2 is looking worse and worse:
Even after NukeUSB'ing the old drivers, Windows won't let me install Dhauzimmer's drivers. It claims they are outdated. Windows XP seems to have a default set of drivers for it that, while not the latest, are new enough that it likes them better than Dhauzimmer's, and it won't believe me when I tell it I want to install Dhauzimmer's drivers.

<sigh>

I'm actually considering looking at the source code and seeing how the joystick setup is done under DX. While I am fluent in C++ (and old school DirectX), I'm not sure if it's worth the pain. I bet it doesn't even like compiling under the version of Visual Studio I have installed...

I remember this headache. The newest driver may pertain to the Human Interface Device which is the left thumb mouse on the joystick. Not a big deal. If the Saitek drivers are lurking somewhere you may need to do some extra uninstallation. Here are some things I did, but I'm not sure if they're necessary...

1. While the Saitek drivers were installed, I noted the USB ids and the driver filenames.
2. Uninstalled the drivers.
3. Searched the registry for the files, USB ids, and "saitek"... deleted.
4. Searched the hard drive for those files, and anyfile with "saitek" in the name... deleted.

I remember something was locked and I needed the correct order of deleting and rebooting.

I'm not a driver expert by any means so these steps are probably overkill.