Jump to content

spc4529

Members
  • Content Count

    13
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

12 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

452 profile views
  1. Thanks for the reply. It's good to know that I'm not the only one who has seen this. Your observation is very interesting. With respect to Glenn's suggestion to "bug report" it, I'll consider it. I'm in the process of updating my XBOX Live account(s) and will probably wait until after that completes.
  2. I have discovered three airports which, when any one of them is added to the flight plan between the departure and arrival points, will cause the following malfunctions in Glass Cockpit Instruments: 1. Airspeed, Altitude, Heading and Bank indicators are frozen. (i.e they show no change of data) 2. The map doesn't move in the "moving map" displays. In addition, for any aircraft flying this flight plan, the "VFR MAP" invoked via the "Tools" menu will have no moving map and no zoom capability. The offending airports I've found (there are probably others) are: KPMD (Palmdale California) KRMG (Rome Georgia) KBOI (Boise Idaho) I am running MSFS Ver 1.26.5.0 (SU9 & WU10) on a Windows 10 machine. I have nothing in my Community folder. All my flights use default planes and MSFS created flight plans. A simple test can be run as follows: Plane: Cessna Grand Caravan Flight plan: Departure - KSLC (Salt LakeCity, Utah) Arrival - KSEA (Seattle - Tacoma, Washington) Add in between - KBOI (Boise, Idaho) Type - VFR or IFR (Either type will exhibit the odd behavior) Fly the route and notice the non functional glass instruments and VFR MAP. I was wondering if anyone else has experienced the same oddity?
  3. The OP specifically stated he was using the MSFS Steam version. In that case, the controller profiles are NOT stored in the "MS cloud". Rather they are stored in the following location: "...\Steam\userdata\[your user id]\1250410\remote" and are named "inputprofile_xxxxxxxxxx". They are XML files that are viewable in Notepad. They are also backed up automatically in the "Steam Cloud" if the following Steam setup conditions are set: 1. Open your Steam client. Open its Settings by pressing the Steam button present at the top left corner of the window and selecting the Settings option. 2. Open the Cloud tab present on the left side of the screen. Check if the option “Enable Steam Cloud synchronization for the applications which support it” is checked. 3. Next click on the Library tab present at the top side of the Steam client. Here all of your games will be listed. 4. Right-click on the game (MSFS) and select Properties. Then navigate to the General tab. 5. Here in the middle of the window, under "STEAM CLOUD" make sure the "Keep games saves in the Steam Cloud for Microsoft Flight Simulator" is checked. This will insure that the profiles will be stored in the Steam Cloud and carry over to a complete re-installation. In addition, to be absolutely sure, one can backup the following directory: "...\Steam\userdata\[your user id]\1250410" and restore it after re-installation if the Steam Cloud backup doesn't work. And finally, if all else fails, after re-installation, one could create "dummy" profiles, exit MSFS, go to "...\Steam\userdata\[your user id]\1250410\remote" and use notepad to replace the content of the dummy profiles with the backup files' contents.
  4. Actually, the bindings are also stored in files on your system. See the following: https://www.avsim.com/forums/topic/590418-print-controller-assignments/
  5. Are you sometimes plugging in your controller AFTER you start MSFS? I discovered early on that doing so will cause your customized controller preset to be reset to the default state. The only way to prevent this is to make sure your controller is plugged in to the system BEFORE you start MSFS. I had not tested this in a long time but just now re-verified this is still the case on my system running MSFS Ver. 1.17.3.0.
  6. MSFS "Profile" file locations for Steam install. After installing MSFS via Steam, the "Options" and "Personalized Controls" profiles are stored in the following location: ...\Steam\userdata\[your user number]\1250410\remote Any personalized "Controller" profiles are stored in "inputprofile_xxxxxxxxxx" files. They are XML files which can be edited using a text editor like notepad. In each file, near the top, will be the name you gave it when you created it in MSFS. For reference, the "Default" controller files are located in: ...\Steam\steamapps\common\MicrosoftFlightSimulator\Input I don't know the file locations for a MS Store installation but you might try searching for "inputprofile*" files.
  7. OK, One more thing you might try is deleting your overall "Profile" file and let the Sim re-build it from scratch. The file is "....\Steam\userdata\<your Steam user number>\1250410\remote\profile_00" After deleting it, the sim will lead you through the initial setup screens you saw the very first time you ran it.
  8. Here is one more suggestion I gleaned from https://www.flightsimulator.com/known-issues/ Find your "UserCfg.opt" file (typically located in C:\Users\<UserName>\AppData\Roaming\Microsoft Flight Simulator). Open the file in notepad and verify that InstalledPackagesPath is set to the path where your packages are installed. Note: This is typically the last line in the file (e.g. InstalledPackagesPath "C:\Users\<UserName>\AppData\Roaming\Microsoft Flight Simulator\Packages") If not correct, edit the path and save the file then try starting the sim again.
  9. If you install MSFS via Steam, the controller profiles are located in: ...\Steam\userdata\[your Steam user number]\1250410\remote I don't know where they are located for a MS Store install but you could search for their names: Any personalized "Controller" profiles are stored in "inputprofile_xxxxxxxxxx" files (search for "inputprofile_ *"). They are XML files which can be edited using a text editor like notepad. In each file, near the top, will be the name you gave it when you created it in MSFS.
  10. Every time I exit MSFS by using the "Quit to Desktop" function from the Main menu, a "FlightSimulator.exe.[some number].dmp" file is created in C:\Users\[user name]\AppData\Local\CrashDumps. An accompanying "FlightSimulator.exe" Application Error is recorded in Event Viewer. This occurs in both "Windowed" and "Full Screen" mode. When in "Windowed" mode, if I exit MSFS using the upper right "X" (Close window) button, no application error occurs and no ".dmp" file is created. So, check your "C:\Users\[user name]\AppData\Local\CrashDumps" directory for these .dmp files. You may want to clean them out. And, before it gets asked, this is still happening after installing Patch #1 (1.7.14.0 - 9/2/2020). MSFS installed via Steam on a Windows 10 version 2004 system: i7-8700k @ 4.3 GHz 32 GB DDR4 RAM @ 3200 MHz 1070ti w 8GB VRAM 1920x1200 monitor.
  11. When you turn on "Developer" mode, it creates a very narrow black "Menu" bar at the top of the MSFS screen. When I first switched Developer mode on, I didn't immediately notice the bar and, like you, assumed it didn't do anything. In that Menu bar are various tabs, one of which is labeled "Options" and underneath that is a "Display FPS" option. When you turn that on you'll see that it is not the cause of the "Little Green Number". I agree with aktorsyl, that the number "looks a lot like Steam's fps counter. In the wrong place and doing weird things". You can turn off the Steam counter by: Exit MSFS; Maximize the Steam window and, in the upper left hand corner select "Steam >> Settings"; Then select "In Game" and set the "In-game FPS counter" to "Off". "OK" the "Settings" dialog; exit and restart Steam: and then restart MSFS. If the green number hasn't gone away, I'm stumped.
  12. I bought and installed MSFS via Steam and I do not have the "...\Microsoft.FlightSimulator_8wekyb3d8bbwe" folder either. I DO have a \Users\"Your ID"\AppData\Roaming\Microsoft Flight Simulator\ folder, under which all the packages (~100GB) are stored. The reason for not having a "...\Microsoft.FlightSimulator_8wekyb3d8bbwe" is it's one of the differences between installing from Steam and installing from the Microsoft Store. The MS Store installation will have it and the Steam will not have it nor does the Steam installation need it.
  13. First of all, the following info only applies to a Steam installation of MSFS. I don't know the file locations for a MS Store installation. After installing MSFS via Steam, the "Options" and "Personalized Controls" profiles are stored in the following location: ...\Steam\userdata\[your user number]\1250410\remote The "Options" file is named "Profile_00" and is a binary file. Deleting it will cause MSFS to rebuild it from scratch on the next startup. You could build several profiles by renaming them after being built. Then just copy the one you want to "Profile_00" before the next startup. Any personalized "Controller" profiles are stored in "inputprofile_xxxxxxxxxx" files. They are XML files which can be edited using a text editor like notepad. In each file, near the top, will be the name you gave it when you created it in MSFS. For reference, the "Default" controller files are located in: ...\Steam\steamapps\common\MicrosoftFlightSimulator\Input Also located in the "...\Steam\userdata\[your user number]\1250410\remote" directory are two files named "kh_logbook" and "datausage" which are binary.
×
×
  • Create New...