It has already been fixed, they have released an update. Unfortunately it requires a modification to the plane’s panel.xml, if i understand correctly. They haven’t been very clear about what the modification consists of, exactly.
Corrected to: “I didn’t understand their explanation of the modification.”
It would have been a much better use of a comment if instead of trying to be snarky you would have explained what needs to be done to get the mod working correctly, since apparently you had no trouble understanding it.
ARGH, said the man that now has several G1000 MFD mods to update.
What a shame, the WTEngineDisplay solution was so elegant, allowing to add MFD elements without having to modify the panel.xml file. You’re not making our lifes easier Asobo, you know that ?
Well, thanks to the WT team for quickly releasing G1000 v0.3.5, at last for now we have a solution.
Anyway … Week-end plans changed from “Spitfire flying” to “XML editing then Spitfire flying”.
I have just discovered a terrible bug with the Garmin G1000, if you fly really near nord pole, in my case extreme nord of Greenland directed to Alert airport, the map is totally bugged and first the GPS plane position go away from planned route, later decreasing the distance from the geographic nord the plane remains stuck in a random position on the map. This affect only the cockpit MFD map, the AP GPS heading continue to work!
Allow me to add one thing. It’s a small update that simplify the pilot job when fly between US and Europe (or the rest of the world). In the real G1000 PFD there is an option to change the altimeter and BARO settings units. Please, add this also in the MSFS. Thanks
-No Vectors to final.
-Activating the approach with a transition will not navigate to the IAF but rather will make a wide turn into the FAF.
-Unable to properly activate legs.
-No hold or PT functionality at all
-Tons of missing fixes and approaches.
-No VNAV
I don’t know what the hell is going on with the ARIAC cycles, you think I wouldn’t need to pay for Navigraph to at least have the GPS in game have correct waypoints in the database.
Unfortunately, none of the mentioned issues are addressed by that mod, but there’s reason to expect that they will be in the next couple of sim updates.
That’s an underlying NavData issue and/or airport BGL (missing/incorrect runways which means proper SiDs/STARs/IAPs can’t be assigned), not a NavUnit issue.
They’re all interrelated, which is what WT is fixing in SU5 and 6.
I mean, this should be basic functionality. I fly volunteer SAR in real life, and we use a lot of user waypoints and lat/long (disasters often don’t have the common courtesy of happening at an established airport or VOR). Would love to get onto Flight Simulator to practice, but, without these, my ability to do that is seriously hampered.
Back last September, finding your own house in the sim was all the rage. This information on how to do it was posted in the forum. Would this do what you want?
Take your coordinates from Bing or Google maps, which will be in this format 7.123456, - 6.654321
Go to the Flight Sim map and type the coordinates into the search box on the left, then click the box below and you will get a custom point on the map!
Doesn’t help that much, unfortunately. I can see using that to force the point into the GPS, then building the remainder of the flight plan in the GPS once the sim’s started up. That works if it’s a single point…but doesn’t solve the problem if multiple user waypoints are needed in the flight plan.
Sorry, I thought you just wanted to fly to a custom point (perhaps where the incident was.)
To join several custom points into a flight plan I use LittleNavMap. You can set a series of custom points with coordinates or just by clicking on the LNM map appending each one to your developing route.
Checkout the WT CJ4. It already has the functionality for creating a FPL with user defined waypoints, using longitude / latitude or Point Bearing Distance referencing.