rec.autos.simulators

Direct Input uses the Windows joystick set up.

Generic is the Papy driver - you don't need a joystick set up at all within
Windows for this to work.

Cheers

Tony

If you're using a Voodoo II card, be sure you're using drivers that
work.  The latest set (I believe they're part of DirectX 6.1) do NOT
work with GPL (3dfx is addressing the issue).  Right click on
c:\windows\system\glide2x.dll, and select Version.  It should read 2.53
(2.54 is the (well, a) version that does not work; some older versions
also have problems).  Aside from video card driver issues, I can't
think of any other reason it might hang while calibrating.

Randy

We feel that our generic joystick reader is about as accurate and
efficient as you're going to get (though we do have to go through a VxD
call to get to it).  Personally, I use it whenever I can.  You should
be aware, however, that our generic joystick reader disables interrupts
while reading the device(s).  This can have ramifications if you're
also using any devices that require time-critical interrupt processing.
 A modem connected to a serial port can fall into this category.  The
default Windows 16550 FIFO settings are tuned for efficient CPU
utilization, but they require more timely interrupt processing.  If
you're going to use the generic joystick driver while using your modem,
you should adjust these settings.  I set both sliders to the first
notch from the leftmost position.

 (Note: It is my understanding that DirectInput will also disable
interrupts when it reads analog devices if you uncheck the "Poll with
interrupts enabled" checkbox in the Advanced page of your Game
Controllers control panel).

Randy

I use the ACM card in both DOS and Windows.  It does require that you
have totally disabled your soundcard's gameport and may require changing
the I/O settings from the default for the ACM card.  Check out
Thrustmaster's ACM troubleshooting guide at
http://www.thrustmaster.com/support/rcs_acm/index.html

--
**************************** Michael E. Carver *************************
     Upside out, or inside down...False alarm the only game in town.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=<[ /./.  [-  < ]>=-=-=-=-=-=-=-=-=-=-=-=-=-=

% We feel that our generic joystick reader is about as accurate and
% efficient as you're going to get (though we do have to go through a VxD
% call to get to it).  Personally, I use it whenever I can.  You should
% be aware, however, that our generic joystick reader disables interrupts
% while reading the device(s).  This can have ramifications if you're
% also using any devices that require time-critical interrupt processing.
%  A modem connected to a serial port can fall into this category.  The
% default Windows 16550 FIFO settings are tuned for efficient CPU
% utilization, but they require more timely interrupt processing.  If
% you're going to use the generic joystick driver while using your modem,
% you should adjust these settings.  I set both sliders to the first
% notch from the leftmost position.

%  (Note: It is my understanding that DirectInput will also disable
% interrupts when it reads analog devices if you uncheck the "Poll with
% interrupts enabled" checkbox in the Advanced page of your Game
% Controllers control panel).

% Randy

--
**************************** Michael E. Carver *************************
     Upside out, or inside down...False alarm the only game in town.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=<[ /./.  [-  < ]>=-=-=-=-=-=-=-=-=-=-=-=-=-=

Your milage may vary, but I find the generic input to be more precise
than using direct.  This will depend on the quality of your gamecard and
controlling device.  There may also be some conflict when playing online
with a serial modem and using generic.  However, I never saw any
problems.  When switching between generic and direct, you may also find
that you will need to play with the linear/non-linear settings.

--
**************************** Michael E. Carver *************************
     Upside out, or inside down...False alarm the only game in town.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=<[ /./.  [-  < ]>=-=-=-=-=-=-=-=-=-=-=-=-=-=

The only reason that I can imagine for it locking is that there's are
conflicting game controller devices in your system.  If you have both a
game card, and a joystick port on a sound card, be sure you've
completely disabled the one you don't want to use.  It's entirely
possible that if there are two conflicting devices that sometimes the
two will squelch each other, confusing the bejesus out of the game.
When you select the generic joystick driver in GPL (toggling from
DirectInput), we poll all axes with a fairly large timeout value.  We
figure that any axis that doesn't respond before that timeout expires
just isn't there, and we no longer try to read it from then on.  If we
get a spurious signal from one of the game cards just before we'd
timeout an axis that doesn't have a potentiometer attached to it, then
we will try to read that axis every game loop.  Our timeout is probably
high enough that, from then on, we spend virtually all the CPU time
polling the non-existent axis.  In effect, this locks the system.

I'm not sure about driver versions for a Voodoo 1 (maybe Eric knows and
can comment on this?)

Randy