Aviator64

Members
  • Content Count

    21
  • Joined

  • Last visited

Community Reputation

0 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. Aviator64

    v1.2 STILL has issues...

    Yes, I have noticed that as well. When flying a GPS course the heading is always around 15 degrees to the left of the course track. At first I thought it was a crosswind correction, but flying it with all weather turned off (zero wind) did not make a difference. If you are zoomed out too far you can lose your VC clickspots. This is a common issue with VCs in FSX and not airplane specific. Try zooming in a little bit. I have to agree with you about the DA62 being just a pretty face, sadly. It is a visually stunning model, and the hand-flying characteristics are great. It is unfortunate that their glitchy G1000 makes the airplane unusable for any kind of serious IFR navigation.
  2. Aviator64

    Odd problem, ntice a few others have as well

    The installer and the ops center should always be run as administrator, are you doing this? Miles Oliver
  3. Aviator64

    v1.2 STILL has issues...

    I tried that and it works the same for me as you described. That still isn't acceptable, however! If the VNAV mode gave you any control over VS or IAS it wouldn't be so bad, but it does not. At least, I haven't found any way to do that. In order to get a proper climb rate I have to change to FLC mode which then breaks the waypoint sequencing again. Never mind the fact that you should be able to hand-fly any part (or all) of your flight plan with the autopilot disengaged, as you would in the case of an engine failure. It's hard to practice hand-flying a single-engine instrument approach when your waypoints don't sequence! There are MANY issues with the DA62's G1000. I hope they are working on a fix; as it stands now the airplane looks pretty but is not usable for serious IFR navigation. I would be happy to work with them to identify things that need fixing. Submitting support tickets feels like talking to the proverbial brick wall, however.
  4. The body of the support ticket I opened with Carenado: Found another significant and repeating bug with the DA62. When loading an approach, not all transitions are listed. Example: KMRY ILS RWY 10R - one I have flown numerous times in real life. On the PROC page, the only transition listed is SNS. ZEBED is also an IAF but is not listed as a transition. Also, the real-life Garmin always has "Vectors" as an available transition; your G1000 does not. If you choose the SNS transition (you have to, it's the only one listed) then the system tries to route you straight to ZEBED instead of SNS as it should. Furthermore, when you choose the procedure and select Load, it behaves as though you selected Activate and immediately routes you to the IAF. Selecting Load should not cause an immediate course change - that should not happen until you go back to the PROC page and activate the approach. Anyone else seen this? Any other real-life IFR pilots here?
  5. Aviator64

    A New TBM 930

    Mooney's single-engine M20 had an always-on wing leveler (called "Positive Control") starting back in 1965 🙂
  6. I just tried it again (from the same saved flight plan) and this time it worked. No idea what changed, but it seems happy now. Thanks, Oliver
  7. Aviator64

    v1.2 STILL has issues...

    I did a little more experimenting and found something interesting. If I create a super simple flight plan - just departure, destination, and a couple of enroute waypoints, then the waypoints do advance correctly. However, any waypoints loaded as part of a SID, STAR, or approach do not. And, it seems like once there has been a failure to advance then it never recovers, at least that is what I have seen. I updated my ticket with this new information, hopefully it will help.
  8. Aviator64

    v1.2 STILL has issues...

    They got back to me a little while ago and told me to uninstall/redownload/reinstall the product, which I did. The issue was not fixed. I have tried it with both the default Navigraph data that came with the airplane as well as the latest cycle. Makes no difference.
  9. Just updated my nav data to the latest cycle. The title bar of P2ATC shows the correct cycle, and all the SIDS/STARS/APPS are correct when creating a flight plan. The flight plan validates OK, and when I file it acts like it worked, but when I call for clearance I get "We don't have a flight plan on file". This is version 2.5.0.5_x64_R3. I have re-installed the Navigraph update, it does not appear to be a corrupted file. I am on the last day of my trial, so hopefully I can get the solution ASAP. Not going to buy the product if it doesn't work! Thanks, Oliver
  10. Aviator64

    v1.2 STILL has issues...

    They marked my support ticked as "Solved" without even posting a reply. Is it possible they released an update? I looked on their website and can't find any mention of one.
  11. Aviator64

    v1.2 STILL has issues...

    I have found a workaround - after you engage FLCH mode, if you turn the altitude select knob (just bump it up 100 feet and back again) it will engage ALTS mode.
  12. Aviator64

    PMDG account recovery

    Thanks, I will go and do that now.. I did not realize they were separate systems.
  13. Aviator64

    PMDG account recovery

    I am trying to access my account on PMDG's website. However, when I sign in it says I have to reset my password. That would be fine, except the email address I registered with years ago no longer exists, so I would never receive the reset instructions. I can't submit a support ticket because you have to be logged in to create one. Any advice would be welcome. Ideally someone from PMDG will see this and get in touch. Oliver
  14. Aviator64

    v1.2 STILL has issues...

    I just got the DA62 yesterday and I am experiencing this also. As a workaround you can bring up the FPL screen, use the FMS knob to scroll to the next waypoint, and press "Active Leg". We should not have to do this though - this is a major bug that they need to fix ASAP. Their TBM850 doesn't have this problem, it seems to be unique to the DA62. I will submit a bug report on their website and I suggest you do the same.
  15. OK thanks for clearing that up. Might be nice if it was stated in the manual - at least, doing a search for "acceleration" and "fast time" produced no results.