Jump to content

grazzmaster

Frozen-Inactivity
  • Content Count

    5
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

9 Neutral

Flight Sim Profile

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

Recent Profile Visitors

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

  1. I concur. I've noticed stutter around S50 Auburn Muni, just south of KSEA. It's persistent around the Tacoma, Auburn and Renton area...maybe north of Seattle as well, but I don't fly north of Seattle as often. I seem to recall it being somewhat less stuttery around the city of Seattle and north of Seattle. I have tried just about everything, but it seems it is something that's affecting the default/vanilla sim. I have a fast PC (i7@5.1G, SSDs, OC'd Titan XP GPU...everything runs cool, fast and stable). I've downloaded the highest res data from ASOBO and created a large Manual Cache area around the Puget Sound, from Everett to Olympia to the Cascade foothills to the Hood Canal. I've tried it with no mods and with mods...still the same stutters. My sim doesn't CTD, but it does stutter in the area. It stutters almost constantly south of KSEA...every 5-10 seconds it will stutter from brief stutters to longer second-or-two stutters. I currently run Drzewiecki Seattle Landmarks, ILLUMINATORS - TACOMA NIGHT LIGHT ENHANCED MSFS, and ORBX KTIW. I have not noticed a reduction/increase in the amount of stutters with or without any of these mods. I thought I'd give my 2 cents since this is my hometown and it's superstuttery (that's a word...I just made it up lol)
  2. I couldn't find a complete list of available key commands, only lists of default commands, so I created one using the sim's in-game key command menu as a reference. I did this by hand, so I can't guarantee there are no typos ;). It should be pretty accurate though. https://docs.google.com/spreadsheets/d/1oa9MTE7uvwXwY_qu4ds7YASO5c0Hpt9uLOYlwJlJtyE/edit?usp=sharing
  3. Thanks Bert! I have figured out a work around: I use a text editor to manually edit the user.wpt file located in C:\ProgramData\Garmin\Trainers\Databases\FPLN\. There are two user.wpt files, and only one of them provides updates across all the GTN models - the user.wpt file in C:\ProgramData\Reality XP\Common\GtnTrainer\flightplans\FPLN does *NOT* provide updates to all the GTN models. Here are the 5 waypoints in the file by default: FISH01,STATELAKE,39.1353,-95.1388 FISH02,EASTPERRYLAKE,39.1502,-95.3924 FISH03,WESTPERRYLAKE,39.1502,-95.4515 FISH04,CLINTONLAKE,38.922,-95.4081 DUCK01,NWPERRY,39.2825,-95.4984 DUCK02,WINCHESTER,39.3016,-95.3208 I added: MHRR,RUS RUS I,14.7142,-84.4544 Results: when I update user waypoints in any of the GTN devices, it now pulls MHRR and any future User Defined Waypoints across! Good news: I can create User Defined Waypoints that can be uploaded to all GTN devices. Bad news: I have to use a text editor to manually create the entries.
  4. Update/Correction: It appears that the GTN 750 is now sharing User Defined Waypoints across aircraft, including the Carenado C207's included GTN 750, however the GTN 750, 725, 650, 635 and 625 do not share a common User Defined Waypoint database. One question remains: Is it possible to have a common User Defined Waypoint database for all GTN models?
  5. I have referred to the GTN 750/650 manual and still have some questions. I will try to explain the situation as clearly as I can. I am recovering from a hard drive crash. I have a new replacement Windows/Programs (C) drive and a separate (D) drive for X-Plane. I had Reality XP installed on my C drive and had to reinstall Reality XP (GTN 750 and 650) when the drive failed, but lost all of my previously saved User Defined Waypoints since they were apparently saved on my C drive. My X-Plane (D) drive is working fine and I was able to resume X-Plane without having to re-install much. I am in the process of recreating the User Defined Waypoints and have noticed a few issues that were not present prior to my hard drive crash. Main issue: prior to my hard drive crash, I was able to access my User Defined Waypoints in all aircraft using an RXP GTN 750, 725, 650, 635 or 625, regardless of whether the aircraft came with the GTN 750 included or not (example: Carenado C207 v1.2). Now it seems that the Carenado's GTN 750, the RXP GTN 750-625 all have separate User Defined Waypoints databases. I have imported the "starter pack" waypoints from C:\ProgramData\RealityXP\Common\GtnTrainer\ into C:\ProgramData\Garmin\Trainers\Databases\FPLN\user.wpt and these 5 starter waypoints are available to import into each device, but the User Defined Waypoints created are only available to the device that created them. This is frustrating because prior to my drive crashing, I was able to access small airports that I had added and their User Defined Waypoints, regardless of aircraft or GTN device. I have a few hundred real-world airstrips in South America that I am re-adding User Defined Waypoints for. Creating and maintaining separate databases for each device is not the ideal situation, especially since it was working well prior to re-installing Reality XP GTNs. I am familiar with my file structure and where most things are located, but I am unable to locate or determine how these devices shared a common User Defined Waypoint database. Any help is greatly appreciated! Thanks :) Windows 10, X-Plane 11.33r2 SW Version 6.50.1 TRNG (same for Carenado's), Reality XP: 2.5.16 (same for Carenado's)
×
×
  • Create New...