Jump to content
The simFlight Network Forums

Ron Buchwald

Members
  • Posts

    62
  • Joined

  • Last visited

Everything posted by Ron Buchwald

  1. Hi all, I have the EPIC USB system and full GC. I want to respond to ATC calls in FS 2002. Yes the keyboard keys 1-9 work. I want to use a key pad i built to respond. IE send a 1, 2, ect... to Fs 2002. I can't find any offsets to send to however. Yes EPIC supports "KEYHITS" but only in latest ver. This would require my to re-write some 2600 lines of my EPL code as R&R has change the syntex again. I long ago lost the keybd. splitter cable. Any ideas?. Can FS 2002 be told to re assing the keys used when responding? I use FS COMMUNICTOR as well, any thing there that might help?.. I am at a loss.. Thanks.. Ron. :cry: Post Reply
  2. 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
  3. Hi all. How do any of you start-up all your computers for a simm?. I have 4 pc's with epic and PM. now that the monitors are in the pannels, it is very hard to start all the programs cause I can not see all the screens. some of the windows are masked by the pannel, and runnig around with a kbd and mouse is not working. If there is a program that you can start-up all the pc and then run the software on each from the main pc or sever what is it?. I tried the fsuipc start-up pgm but it wants to start the networked pc pgm on the server not on the networked pc. Any help?. thanks. Ron.
  4. Has any one gotton the rudder trim to work? I am trying to use FS COMM ver. 1.0.57 that has the FLOAT64 int routine built in but I don't see how to write the code in epic epl. I want to use an analog pot to set the trim. I don't know how to send an nqw value from an analog. What is a FLOAT64 number anyway? The offset for the trim is "2EC0" I can send to the trim in FS INTERROGATE but not thru epic. Any help. Ron. :?:
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.