Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About Mike777

  • Rank

Profile Information

  • Gender
  • Location
  1. Hi Pete, FS2020 has broken up aircraft.cfg into several files The ... Effectiveness = entries are in flight_model.cfg. However for the 787 and some other "premium" aircraft these files are hidden and apparently considered proprietary -- no doubt because PMDG & Quality Wings are dying to use their tunings (??!! 🙂). I thought more about your comments on the control issue -- perhaps you might consider adding flatter slopes to FSUIPC. If the flattest is now 15, maybe up to 20 or even 25. Fielder: I've found that you can set up a controller profile with only buttons assig
  2. Pete, thanks for your thoughtful response. But it is exactly a greater ratio of movement of the joystick to movement of control surface that I need (mainly elevators & ailerons)! I find the airliners to be way too sensitive on pitch, even with the most flat FSUIPC curve. If you haven't already, try flying the ASOBO 747-8 (there's a stock flight setup for landing at JFK 31L) -- I would really appreciate your input on that aircraft and other native MSFS airliners. Mike
  3. Hi Thomas, thanks for the tip! It certainly does work, and has the desired effect of reducing the overall effectiveness of the elevators and ailerons. John, it may sound odd, but with my venerable Microsoft Sidewinder joystick and the oversensitivity of flight surfaces, especially in the ASOBO 748 and 78X, I don't need the full range of motion for ailerons and elevators. I never had this problem in FSX (using FSUIPC), but then again I almost never used default aircraft. Almost always PMDG 777, 744 and 8, 737, QW 787. Mike
  4. Hi John & Pete, I suggest a new function, overall sensitivity for each axis. Several of the aircraft are overly sensitive, especially on Pitch and Roll. I have experimented with the curves/slopes you provide (and those now available in MSFS2020) but I have been unable to obtain satisfactory results. You provide settings that allow me to make a given axis MORE sensitive - for example -16383 elevator output at a joystick input of -12000. But I would like to be able to set Joystick elevator INPUT to 16383, with a joystick elevator output of 12000, that is joystick has LESS effect
  5. Hi, Pete, Thanks for your response. I am hoping you might give me some insight as to how to fix this problem. The PMDG 777 and NGX have not changed for quite awhile. I didn't fly the Level-D much in my original Steam setup, but in my FSX Box setup I flew it a great deal. Never saw frequent long pauses owing to Autosave or anything else on any of these aircraft (I flew the 777 and NGX a great deal in Steam when it was part of a dual install). There is now an update for the Level-D but I am not using it since it is for Windows 10 and/or P3D. The problem appears to have started --
  6. Hi Peter, I have been using registered FSUIPC and particularly Autosave for years with advanced aircraft with no problems other than occasional micropauses (so I increased the time between saves to 300 seconds). For the last week or so I have had many long pauses that appear to accompany autosaves (by looking at the time on the saved file during a pause). This is happening with the PMDG 737/NGX, PMDG 777, and Level-D 767. Toward the end of the flight the pauses seem to become longer. I know you discourage using Autosave with these aircraft, but I have been flying them for a long
  7. Hi, Gaétan, I am assuming that you are running FSC on the same machine as FSX:SE. When you look at the FSC Database Manager window, after you select your FSX:SE path in the window on the left, is the correct scenery.cfg path showing in the window on the right? The path should be something like C:\ProgramData\Microsoft\FSX. You can check by navigating to that folder and finding the scenery.cfg file there. Make sure that it has the correct scenery.cfg file. (Note that there are several scenery.cfg files in various places in FSX, but only one is used. The correct location is explain
  8. Hi Geoff and everyone, FSC should work on a Windows 8 machine w FSX:SE if that is the only version of FSX on the computer (and there is nothing left in the registry from an install of FSX:MS-Box version). In that case FSX:SE uses the same folder and file names as FSX:MS (and AFAIK all the folders are same in Windows 8 as in Windows 7). It is only with a dual FSX:MS and FSX:SE on the same computer that FS Commander won't find all the correct folders and files. Mike
  9. Hi, Volker, I have FSC 9.6 working with FSX Steam version. I have a dual install of FSX:MS (Microsoft boxed version) and FSX:SE (Steam version). This causes Steam to install using different names for some folders, including the all-important C:\ProgramData\Microsoft\FSX . Steam names it ....FSX-SE. However there are some workarounds that make FSC work. 1) rename/backup the scenery.cfg file in C:\ProgramData\Microsoft\FSX and then copy the scenery.cfg file from C:\ProgramData\Microsoft\FSX-SE to C:\ProgramData\Microsoft\FSX. After runing FSCDBManager, remove the scenery.cfg fi
  • 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.