Okay, I've been having issues with KDEN and finally got them straight. All my approaches now have transitions so I can request GPS/RNAV and not get stuck with the vectors nonsense. Somehow this was lost with a 3rd party AFCAD that had some errors in it. All is good on the AFCAD front.So, in testing the approaches to make sure I can select the transition in the ATC menu, I've been using GA aircraft. My plane tonight was the Dreamfleet B58, going from KSBS to KDEN.Both flights gave me a different runway and both approaches in the Reality XP went awry. The first one seemed to follow the GPS towards the IAF, however, I was not in line with the runway at all. It was the LIPPS fix for runway 8. So, I tried another flight and was given 16R. I selected the SAKIC fix in the ATC menu and headed directly there. The problem? Once I crossed the SAKIC fix, the GPS started to bank to the right away from the JETSN fix inline with the runway. My only option was to switch off GPS mode and NAV, turn on HDG, and bank back towards the LOC intercept, which I had tuned in. I've never encountered this unless a hold was in the GPS and needed to be removed. There were no holds, except after the missed approach at BREWS. I double checked both times and my GPS had not switched to VLOC or SUSP. The GPS/NAV switch was still in GPS mode. My AP was still in NAV. WTH?? This is making my transition intercept with the GPS impossible. This is usually the point where I turn off the GPS and NAV and fly manually using ILS or visual. Kinda hard to do when the AP decides to "get lost".You can see me passing by SAKIC, then turning away from the airport. It has to be something with the Garmin because the AFCAD is fine and all works there, plus the two or exclusive. The Garmin made the SAKIC fix and JETSN was just below on the map there, so it's not anything funny with the AFCAD or navigational database in FS9. The ILS approaches are right on according to the charts and the IAFs/FAFs match up.

Nevermind I guess. I just flew this exact route with the only difference being that I selected the GPS/RNAV approach into 16R instead of the ILS in the RXP 530. Same waypoints so it doesn't matter how I tell ATC versus what I fly. It worked fine this time. Still would like to know why it went crazy last night.

I'll try the same approach tomorrow with the same equipment. See if I can't reproduce it.That'll teach ya' to make sure the GPS switches to "VLOC" like it's supposed to! :( Imagine that happening in the soup--in real life.