HELP WITH fs2002 2004 NO JOYSTICK

[Ron Buchwald]

Help with fs 2002 and 2004

Hi Pete. I must have been under a rock for awhile but............

I"ll start with all the stuff you need to know.

1) opt. sys. is win 98 se

2) fsuipc ver is 2.96

3) wideserver ver is 5.408

4) FS Comm ver is 1.00.0057

5) flight sim ver are FS2000,FS2002,FS2004

6) Epic USB Epicenter ver is 0.1.1.50

7) Project Magenta full boeing package (But this does not come into play.)

8) 5 AMD(1.7 gig) PCs

I understand that FS2004 works only with your payware FSUIPC and Widesever ver.

so maybe problems with FS2004 are not the same as for FS2002. or our they?.

I am not using TCP/IP and this is not the problem anyway. Here is the Problem

No problem with anything using "FS2000" However when I upgraded to FS2002 and same for FS2004, I can not get any of the analogs to work. When I start FS2002 or FS2004 the view spins out of control and no joystick functions work. I don't know about any button functions cause I blow up form spinning around so much. In my FS2000 cfg. file it does not list any joystick axis and all work ok. I noted in the FS2004 cfg. file (after I found it)

that it list 1 set of joystk axis. which are not maped the way my hardware is. With this said I ask. does FS2002 need your payware as well as FS2004 or is there somthing else going

on. I could swear that at one time I had FS2002 working but can not do it now.

I had thought and works for FS2000, that by talking thru EPICINFO or FS COMM you were bypassing the windows game controler. and you need not edit the FSXXXX config files. after I started using FS COMM I never saw the game controler screen nor the FS config file. I don't feel this is an FS Comm problem as It Just talks to FSUIPC.

Bottom line: All worked well with FS2000, networked with 5 PCs Wideserver and client,FSUIPC and FS Comm but NOT with FS 2002 or FS 2004.

SO Pete What do you think? If you need more info let me know. Thankyou.

PS. I don't mind paying For FSUIPC but I did not think it was needed for FS 2002.

Grounded and blue, yours truly Ron Buchwald.

E_mail tvron321@aol.com

[Pete Dowson]

2) fsuipc ver is 2.96

3) wideserver ver is 5.408

These are both very old. The last completely free versions (not suitable for FS2004) were 2.975 and 5.5 respectively.

so maybe problems with FS2004 are not the same as for FS2002. or our they?.

Since you can't use those versions on FS2004 at all (they won't even run!), if you are getting similar problems on FS2002 and FS2004 they are evidently nothing to do with my modules, but let's see ...

No problem with anything using "FS2000" However when I upgraded to FS2002 and same for FS2004, I can not get any of the analogs to work.

Your "analogues" are joysticks and throttles? Calibrate them in Windows and assign them correctly in the Options-Settings-Assignments section of FS. This is the same sort of process as it was in FS2000. But you may want to add "stick_sensitivity_mode=0" to the [Controls] section of the FS CFG file. This makes FS2002 and FS2004 treat the analogue inputs more like they were in FS2000.

In my FS2000 cfg. file it does not list any joystick axis and all work ok.

I don't know how that works -- FS2000 always listed the joystick assignments, nice and cleanly with proper Joystick identifications. Since FS2002 FS has used Direct Input (part of DirectX) for joysticks, and this, in my opinion, messed things up somewhat. The Joysticks are then identified by complex "GUID" strings of numbers and letters.

With this said I ask. does FS2002 need your payware as well as FS2004 or is there somthing else going

No, but FSUIPC and WideFS are absolutely nothing to do with this -- you need to get FS to recognise your joysticks with no add-ons or add-ins anyway. Why do you think my modules are involved?

I do note you listed "FS Comm" and "Epic USB Epicenter" amongst your add-ons. Is FS Comm an EPIC driver for FS, and does it use FSUIPC or does it do things differently? It isn't one of my programs -- in fact I note that you don't use any of my EPIC related programs anyway.

Perhaps your problems are related to EPIC? Do you have any analogues connected through that, and are they being mapped to normal joystick controls or processed by your own programming in EPL? If the former then you still need the Windows calibrations and FS assignments correctly sorted. If the latter then it sounds like a question for FS Comm. Certainly, if FS comm uses FSUIPC then for FS2004 you'd need FSUIPC 3, not 2. If it doesn't, then perhaps you need an FS2002 version for FS2002 and an FS2004 version for FS2004.

I had thought and works for FS2000, that by talking thru EPICINFO or FS COMM you were bypassing the windows game controler.

Certainly that isn't true for EPICINFO, which is primarily an OUTPUT module -- it only provided some POV/Soft axis inputs AFTER FS2002 came out, precisely because proper radio control was impossible using POVs through Direct Input -- POVs were used in FS2000 quite happily, as any value could be used. Direct Input destroyed that, only "proper" POV values were accepted. That's why I added such things to EPICINFO. It has NEVER had any axis type input facilities, they are always between EPIC and Windows to sort out.

I have no idea what "FS COMM" does. Sorry.

Regards,

Pete