Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Juergen2

  • Rank

Profile Information

  • Gender
  • Location
    Tampa, Florida

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi, The problem was that I had conflicting assignments in P3D and FSUIPC. I reset FSUIPC to default and copied/pasted the additional button assignments from the previous FSUIPC.ini. Now everything works NORMAL. Thanks for help Juergen Mader
  2. Hi, I have a problem with FSUIPC in P3Dv4.5 and Aerosoft Airbus aircraft. When FSUIPC is loaded, the X and Y axis of my side stick will not reach the end positions and re-center and behave somewhat erratic. If I set the add-on.xml to .off, so FSUIPC does not get loaded and I perform the flight control check both axis behave normal with smooth movement and re-center. Initially I thought I had to run my side stick thru FSUIPC, but decided against it and set it up directly in P3Dv4. So now I don't know if there are any entries in the FSUIPC.ini that affect these 2 axis and affect t
  3. Hi Pete, As for ChasePlane it provides hatswitch movements N-E-S-W as well as NE-SE-SW-NW by itself, HOWEVER only for 1(one) controller. Since many of us have 2 controllers (yoke and side stick) I always have to have both controllers available during a flight ( one for ChasePlane and one for aircraft; space problem). So with mapping the hat switches of both units through FSUIPC as keyboard button presses to ChasePlane, I now only need 1 (one) controller for a flight. I now got the key-presses to work in ALL direction (N-E-S-W as well as the 4 diagonal movements). The only thing
  4. Hi Thomas, Well I overstated my ability I guess, since I can NOT figure out why my Diagonal Pan's don't work. I have 2 controllers, R2(Alpha Flight Yoke) and R3 (Airbus Side Stick) and I programmed R3 to include diagonal movement. I know the hat switch is capable of it, since it shows up in FSUIPC as button 33, 35, 37 and 39. These are my button definitions: 0=R2,32,K68,10 -{Key press: ctl+D}- 1=R2,34,K72,10 -{Key press: ctl+H}- 2=R2,36,K75,10 -{Key press: ctl+K}- 3=R2,38,K70,10 -{Key press: ctl+F}- 4=R3,32,K68,10 -{Key press: ctl+D}- 5=R3,34,K
  5. Thomas, Thanks very much. With the typo I just doubted myself, but I completely understand now how to program the 2 controllers. Until my next problem Brgds Juergen
  6. Hi Pete, Thanks for clarification; I just wanted to make sure I understand the logic. I know now how to program the hat switch properly. As for the diagonal movement in ChasePlane - you certainly can move diagonal w/o problems. My problem is that it does not recognize 2 different joysticks (for me Alpha Flight Yoke for Boeing and ThrusMaster side stick for Airbus). Each one of these controllers has a hat switch, which I can program in FSUIPC to send the correct commands to ChasePlane. Hope that makes sense Again Thank you and Thomas for help Juergen Mader
  7. Hi Thomas, Thanks for speedy reply. I am pretty sure I understand, however why does your button 35 (diagonal right - down) have the same definitions as button 33 (diagonal right - up)? Here it would seem like the view would go diagonal right-up? Thanks for clarification Juergen Mader
  8. Hi Thomas, I believe my light bulb went of: I have enclosed a brief Excel sheet documenting what I believe is happening to get the diagonal movement of the hat switch working. Again if you could take a look at it and let me know if I am correct, I would appreciate it Brgds Juergen Mader Location: KTPA FSUIPC Assignment.xlsx
  9. Thomas, That's what I thought. I do understand the programming of the flight controls buttons. But here I am in particular interested in the hat switch, since that is the button that I use in ChasePlane to look around in the virtual cockpit. In his video he programmed the tilt up & down and pan left / right (= P0/P180/P270/P90 in ChasePlane) with Ctrl+T/G/F/H. However, what I don't understand is the "diagonal" movement programming he talks about, where he edits the .ini file to have 2 buttons working at the same time, e.g. P0 & P90 should be a 45 degree diagonal movement. If you l
  10. Thanks Thomas, that's it. I was wondering if you could do me another favor and look at that video where the guy shows his .ini file (approx. 3:19 min). I assume the l/h numbers are generated when you assign buttons in FSUIPC. So these numerical values on the left are buttons/switches assigned in FSUIPC and written to the .ini file? Thanks for your help Juergen Mader
  11. Hi, 1. Some background: In order to make the flight experience more realistic I have (or will have) flight controls for Boeing aircraft (from Honeycomb - Yoke and Throttle Quadrant) as well as for Airbus aircraft (from ThrustMaster - Sidestick and Throttle Quadrant). Now the problem arises that ChasePlane (camera utility program) only recognizes one control unit to assign buttons to; so at the moment I use a ThrustMaster joystick to control views (inside / outside) and a hat switch for pan. If I fly a Boeing aircraft I use that joystick/side stick to control ChasePlane and a Hone
  12. Hi, Sorry for premature post. I deleted my scenery.cfg and had P3D rebuilt it. Loaded a flight and exited P3D. Started MakeRwys 4.90 and it started and ran with no problem. Sorry
  13. Hi, I just update my MakeRwys 4.8.73 with version 4.90. I place the .exe in the root folder of my P3Dv4.5.14.34689 and executed it. I am now getting an error: "Failed to make all of the data files. Failed to make FStarRCRWS file!" The file does not execute but the error shows immediately. Thanks for suggestions and help
  14. Hi John, No problem. Also your reply went to my spam folder, so I saw it very late. In the meantime I figured out the problem: I checked my scenery folder and found some erroneous entry at the end of the list. After I deleted the entry, makerwys (v4.871) ran w/o problem. Thanks for reply Juergen Mader P.S. Also upgraded to version 4.873
  15. Sorry, forgot to sign Brgds Juergen Mader
  • 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.