Karelpatch

Members
  • Content Count

    26
  • Joined

  • Last visited

Community Reputation

0 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

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

Recent Profile Visitors

97 profile views
  1. Karelpatch

    Vertx DA62 has launched!

    I think that P3D models icing very bad. I installed a gauge called icev10 which simulates icing better (it builds up and it has real effects on the plane). So I can see when icing happens and it’s to be taken seriously like IRL. Edit: best way to create icing conditions is to load the Active Sky Icing scenario!
  2. Karelpatch

    Vertx DA62 has launched!

    Nope, it’s just saying that the plane is equipped (IRL) and that you can choose the fluid quantity in game. But it’s not saying that it is indeed modeled inside the game.
  3. Karelpatch

    Vertx DA62 has launched!

    Love this plane! Been hooked to it forever since I bought it. I have some strange issues with ILS approaches: sometimes I will loose the glideslope and suddenly plunge to the ground, having to stop AP ASAP. What could cause this? Otherwise, I really wish the mishandling of power would damage engines. I hope to see this in a next update. I have also a question about the de-icing: is the switch working or is it a dummy and is there a difference between normal and high in the in-game TKS efficiency?
  4. Karelpatch

    RNAV approach TRK not matching DTK

    Hi! I’ve posted on A2A forums about my issue with the autopilot disconnecting, and I got an interesting reply from the devs (see last answer): https://a2asimulations.com/forum/viewtopic.php?f=139&t=67295&p=511964#p511964 Apparently something must have changed between RealityXP gauges, P3D or Garmin’s trainer.
  5. Karelpatch

    RNAV approach TRK not matching DTK

    Will try!
  6. Karelpatch

    RNAV approach TRK not matching DTK

    Hi, I’m back and kind of losing my mind over 2 separate issues: - I tried to redo the RNAV approach and now for no apparent reason my autopilot (KFC 200) disconnects every time it reaches the FAF from IAF. And it happens on every airport I tried. I tried staying in NAV mode or APR mode, same issue, it doesn’t catch GS anymore and it disconnects and I am unable to select NAV nor APR afterwards. (Just crossed my mind: I guess I should select VLOC manually because I am too close to the FAF. That could be the issue. Will try.) - Second issue, certainly related to the initial topic: I created a direct route to a VOR. And of course, the course isn’t matching the line! Once more I have something like a 2 degrees offset. Completely different region (Europe). I checked the GTN magvar and it was correct compared to recent real life charts. Could it be that my P3D magnetic variations are not correct? Pictures illustrating what I am talking about: https://imgur.com/gallery/MTZ8Tgp
  7. Karelpatch

    RNAV approach TRK not matching DTK

    So, when I go into the Unit setup, I should see the current magvar on the button for the “Magnetic variation” option? I will definitely try everything this week. Really curious to see the cause of the issue.
  8. Karelpatch

    RNAV approach TRK not matching DTK

    This is where I found the databases informations: https://imgur.com/gallery/XCe6F5X
  9. Karelpatch

    RNAV approach TRK not matching DTK

    Ok, so I did some tests this morning but I was lacking time: I reloaded the same approach and I got the exact same behavior (change of track after the FAF to RW leg is activated and I catch the GS.) - I searched where the magvar was displayed on the Garmin. I only could find the one on the chart and I compared it with the most recent data and it shows the same magnetic variation. Is there a menu on the Garmin to display the magnetic variation? - I couldn’t find where to deactivate charts overlay? - When going through the device informations I discovered that I had corrup/unauthorized databases: Basemap and Safetaxi. Is it normal? Thanks!
  10. Karelpatch

    RNAV approach TRK not matching DTK

    You rock, thank you! It’s actually mostly curiosity for me at this point. I was wondering if I did something wrong in the way I setup my approach. Or maybe some settings I need to change. I haven’t had the time yet to try the GTN 750 in more than a few flights, nor to retry that specific flight. I definitely will. If I find I can’t reproduce the issue again or that it’s specific to this airport, this will add another layer of realism: never 100% rely on your avionics.
  11. Karelpatch

    RNAV approach TRK not matching DTK

    I’m going to try this when I have the time, ASAP. I’m curious: why would deactivating charts overlay change anything? About the magnetic variation: if this was the case, shouldn’t it cause an issue in many other cases? Also, weirdly enough, the previous 166 degrees leg from IAF to FAF was followed with no issues.
  12. Karelpatch

    RNAV approach TRK not matching DTK

    I have the latest airac data.
  13. Karelpatch

    RNAV approach TRK not matching DTK

    Yes, I posted here because I figured I could get more help. The A/P did exactly what was shown on the GTN: it flew away from DTK and TRK information seems accurate, as the course needle.
  14. Hi, I was flying the A2A Bonanza with GTN 750 and I loaded a vector approach to RW 17 on KTHV. As I reached the initial fix, I put my AP in approach mode. The plane aligned to the 166 degrees vector, the CDI was showing a nice full arrow and when I reached the FAF the AP catched the glideslope and started the descent.  But from that moment, I watched the TRK moving away from the 166 DTK by a few degrees as we were approaching. At runway level, the track was at 171 degrees, leaving the runway to my left.  What could have caused the plane to move away from the vector track? It was supposed to track the vector since it even did catch the glide slope. Is this about settings? Some relevant screen grabs of the track: https://imgur.com/gallery/b294ijK First picture, I am on 166 vector. Second one: I have reached FAF and slowly going off track (171 degrees on the picture.) The leg was activated with the countdown confirming 166 degrees.  Thanks!
  15. Karelpatch

    RNAV approach with GTN 750 and vector off track

    Will check. Thanks