Aviator64

Members
  • Content Count

    28
  • 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

    G1000 issue

    You are not doing anything wrong. This is a known bug: Carenado is well aware of it but have yet to issue an update to fix it.
  2. Aviator64

    310R CTD on load

    Further to the above - the reallight and trueglass installers that come with the 310 update the dll files, but do not update the shader files that were previously installed along with the airbus. There is clearly some incompatibility. Removing the reallight and trueglass subdirectories from the P3D\gauges directory and then re-running the installer resulted in a clean install and fixed the CTD issue. I need to do some testing and see if the trueglass effects still work in the airbus.
  3. Aviator64

    310R CTD on load

    OK, I found the culprit. It was the trueglass and reallight that were installed along with the 310. In fact, after installing the 310, loading my Aerosoft Airbus Pro also caused a CTD. Removing both the RealLight.dll and TrueGlass.dll files (found in the P3D gauges folder) fixed both airplanes.
  4. Aviator64

    310R CTD on load

    Just installed the 310 Redux on P3D 4.3. Can't even load the airplane, it crashes the sim immediately. All instructions for installation (run as admin, AV disabled, etc) were followed. I load P3D with a default flight using the stock Baron, all good - then load the 310 and the sim goes "not responding" for a few seconds followed by CTD. Any thoughts would be appreciated.
  5. Aviator64

    Vertx DA62 DME/ADF

    Press the PFD soft key, the on the next menu press DME, that will make the DME readout appear next to your HSI. On that same menu the BRG soft keys will cycle through the ADF and RMI pointers on your HSI.
  6. Aviator64

    690B MOD v5.0

    Is this mod in the file library somewhere? I tried PM'ing the author but got an error message that he "could not receive messages".. thanks
  7. I opened a support ticket with Carenado concering the apparent inability to load and save flight plans. This was their response: Greetings, Since this AC uses a Navigraph Database Flight Plan importing is not available. Regards Carenado. There is a certain useful word that can be conveniently disguised as a cough. Considering that the PMDG 737NGX, the Aerosoft CRJ700, and numerous others use Navigraph data and can easily load flight plans created with an external program, I have a hard time accepting this "explanation". It is so disappointing - their DA62 is beautifully modeled, and has great flying characteristics. It is just such a shame that their G1000 is so haphazardly programmed; not just this but all the other issues mentioned in this forum. More bugs than an ant farm. I hope Carenado reads this forum. They are not getting any more of my money until they fix the DA62.
  8. 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.
  9. 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
  10. 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.
  11. 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?
  12. Aviator64

    A New TBM 930

    Mooney's single-engine M20 had an always-on wing leveler (called "Positive Control") starting back in 1965 🙂
  13. 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
  14. 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.
  15. 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.