rhd75

Same problem here. Just received my MCP and I can't find the drivers so I can't get it working. I've emailed them, but annoyingly, it's Friday evening so I probably won't get a resolution until Monday. I'm baffled as to why this file is nowhere to be found, a year after the OP's post.

I wish to back away from my original post slightly because last night I installed the latest update, flew it for a few hours and, to tell the truth, the 172 is much better than I remember it. The changes to the aileron sensitivity at slow speed, and whatever else has been done, have obviously made a difference. I also came to realise that things such as the strength of the centering spring in my yoke probably make a big difference to how I perceive the control forces required compared to those in the real aircraft. However, I still find the real aircraft much easier to fly accurately, and the fact that A2A keep changing how the thing flies, dramatically, and now for the fourth or fifth time, suggests to me that they don't really know what they're doing. Anyway, I obviously got carried away so I apologize. As for my claimed accuracy on the 172, I stand by that, and I may at some time post a video, possibly in about a month when I have time to make one. Oh, and if this Dudley Henriques guy is such a piloting genius, how did he approve the original release of the 172 which truly was a joke in so many aspects? (No p-factor or torque, wheelies on landing until 5 knots, and a host of other unbelievable behaviours) Edited for typos and spelling.

If that was a question, I'm totally serious. I genuinely think the A2A 172 is atrocious, and I say that as a professional pilot of 1900 hours, ATPL, CPL(H), King Air type rating, close to 200 hours on 172's, and can land a real one to 3 inch accuracy laterally, and 10 feet fore/aft. Behaviour at slow speeds is totally wrong, especially in the flare with a crosswind, often stalls on takeoff when it shouldn't, way too much opposite aileron needed in turns, almost impossible to land mains first with full flaps, and don't like the flat screws on the panel and inadequate polygons in critical places either. Rip off price. Wish I could get a refund. Last A2A plane I will buy.

You'd be better off transferring the default 172 from FSX. It has a more realistic flight model, IMO.

Wasn't the metar you quoted a real world one that was simply downloaded by ASN? I would be surprised if ASN generated this idiosyncratic metar on its own.

Hello, I thought I would point out two differences I found between the Mindstar and the real G1000. They might seem small but I run into them quite frequently. Point 1 is that on the real G1000 I use, it's possibly to load a STAR and then edit the flight plan to remove some of the waypoints you have just loaded by highlighting the waypoint with the cursor and pressing the CLR followed by the ENT button for each one you want to delete. This is useful if ATC asks you to fly "the balance" of a STAR after a certain waypoint. For instance, flying from Abbotsford to Victoria, I often get asked to fly the balance of the APASS4 arrival from YYJ. I therefore like to load it on the ground, but delete all the points which come before YYJ. Pressing the CLR button on the Mindstar does not produce the expected result. It hides the flight plan pane and goes back to the main map, which is the action that should result when this button is held down. Point 2 is that after the enroute section of the flight plan, I'm pretty sure that the real G1000 automatically starts sequencing the waypoints in the Arrival or the Approach, so if the autopilot is on Nav mode, the plane will proceed from the last of the waypoints of the enroute section to the initial approach waypoint. The Mindstar G1000, on the other hand, does not start sequencing the approach unless the approach is first activated.

RS stands for Rosario and the 05 and 23 are the runways at Madeira. It's giving you the wind at these additional points.

Turbine Duke v2 is released, it seems! P3D version to follow.

If by this you are saying that the yellow horizontal pitch markers (the wings of the miniature airplane) are not level, I don't agree. I made a picture to illustrate this. Looking at the individual pixels, they are level with each other. The horizon line, on the other hand, appears to show about a 1 degree angle of bank, even though the autopilot was supposedly producing straight and level flight. https://www.dropbox.com/s/sgtlqz2htum65qn/MindstarPFD.png?dl=0

Glad to hear that you are tracking down the problem. Just wanted to add that, as a pilot and a strong believer in the use of home simulators by pilots, I am grateful for your fine product and am here to help you improve it. Please consider any future bug reports I make to be made in this spirit.

Richard Dahlman

Actually, the white horizon line is not perfectly level, it slopes down to the left. It is antialiased so it is hard to see. The sky pointer points exactly to the 0 degree marker on the roll scale, but the yellow "wings" of the "miniature airplane" are not parallel to the horizon.

I don't know how to upload a picture here. I have one already and I would be happy to post it. As for the tone of my posts, I don't know what you're referring to. I like your product and just want to get a few problems sorted out. Here is the screenshot: https://www.dropbox.com/s/j83q0fq9jx634cx/2014-11-23_18-59-27-194.bmp?dl=0

It appears that when the wings are level according to the bank indicator, the horizon on the PFD is sloping down to the left, as if the plane were in a very slight right turn. You can see this by clearing weather and putting the autopilot in heading mode. Could this be fixed?

I've been using the G1000 with the RealAir Duke, and for testing purposes up to now I've been using the Diamond DA42 style. Today, however, I tried creating a more appropriate version of the panels using the supplied configuration utility to edit the G1000.INI. Unfortunately, this utility doesn't seem to work too well. I tried to create a new Configuration Name called "Duke" and then assigned the "Beech Baron" style to it. Clicking apply produces a message, "The Beech Baron style is not available yet." However, I know it does exist because there's a Beech Baron with Mindstar G1000 already installed in P3D. I assume the Mindstar installer created this variant. Another problem is that selecting the Beech Baron style in the Configuration Utility grays out the Vmc and Vyse boxes. What's going on here? Looks like I will have to resort to editing the .INI manually. Update: I got the Beech Baron style working in the sim. Is there a way to edit the scale for the engine instruments to be appropriate for the Duke? (e.g. propeller RPM green arc from 2350 to 2900)

Just purchased the G1000 and was disappointed to find that I could not enter airways in the flight planner (the LD AIRWY softkey did not do anything). Was I doing something wrong, or does the Mindstar G1000 not have airways?