XCLTM3

Appreciate the video and your suggestions, many thanks. I'll definitely give it a try again and see how it goes.

LOL ! I thought there was going to be a magical workaround.......

Please let me know what you are doing.......

I understand what you mean. I did look at the Lock mechanism but couldn't for the life of me get it to work. And since I don't have to use it for my other aircraft already mentioned..... But are you saying that from the captains perspective (left side of these dials), it is not possible in that entire real estate (complete left side of dials) to manoeuvre the mouse and manipulate between 2 arrows, one indicating clockwise and the other counter? eg - the whole 180 degree arc of the left side of the dials. The top arc 90 degrees would be for clockwise - the lower arc 90 degrees for counter clockwise. The specific arrow indicators appear inside each 90 degree arc.

Hope you good people don't mind my raising this here, as it seems some persons in the MSFS forums just aren't comprehending the issue. I recently got into the Kuro 787. And for the most part, really enjoy it. I believe it has great potential. (I am a seasoned PMDG pilot having flown all their commercial jets competently since FSX/P3D days and enjoy the Fenix A320 also). The issue with the Kuro, Horizon and Working Title/MS/Asobo 787 is this: Currently, on the B787 EFIS several of the dials can be manipulated by your mouse to turn either clockwise or anti-clockwise and provides an animated arrow signifying which direction you are engaging. This is extremely helpful/efficient and speedy, as I can left click and hold my mouse button to "speed up" the rotation of the dial to the desired setting in either direction. PMDG and other 3rd party devs already have this imperative feature incorporated into the MCP/EFIS and other dials on their respective aircraft. However, on the 787 MCP, the only dial that allows this is the Speed Bug dial. The Heading and Altitude bugs are largely incapable, which is extremely inconvenient. So at present, you can only engage either of those dials with the quick arrow in an anti-clockwise direction. Otherwise, it's mouse wheel scroll for clockwise which can be painfully slow and inefficient. To add insult, you "may" be able to locate an infinitesimal clockwise arrow on the heading dial, but you have to change your physical position in the cockpit in an attempt to find it if you ever find it at all?! So good luck finding it, and goodbye to immersion/convenience. Firstly, I did raise this issue with devs at Horizon on Discord (Toby C) who responded - “we can’t edit cockpit click spots, arrows, etc etc". Then I attempted to raise this at MSFS forums to see if they could provide any of the 3rd party devs with the appropriate permissions etc to address this issue.......well, I say no more. (see below link) https://forums.flightsimulator.com/t/boeing-787-all-variants-mcp-dials-ie-heading-altitude-require-further-refinement/628073 From a programming perspective, half of the work in the B787 has already been completed/incorporated as some dials have this full functionality whilst the Heading and Altitude dials currently have half the functionality and yet they are critical in their importance and use. It is not difficult or overly time consuming to add this feature to the dials. From an immersion perspective, the leading devs comprehend the importance. Asobo/MS..........well, they're not comprehending it. edit: it would seem now, that the dude giving me attitude in MSFS has removed his posts from mine.......LOL! I may put some screenies up of the conversation here......bet he didn't plan on that?

So that's what they've been up to for this duration.......no wonder. This will be big indeed.....

Nice touch! Just a bit too close to the mountain range.........white knuckles.

Hi Jack, I've been using FSLTL in conjunction with AI Ground & AI Flow, and it has performed above my expectations considering they are freeware. AI Ground and AI Flow enhance the AI capabilities -> they are available here: (not that I am involved in any way shape or form with these products) https://flightsim.to/file/42732/aiground https://flightsim.to/file/42731/aiflow Cheers!

I tested the A310 against the PMDG 737 - same airport/gate, time of day, conditions etc. PS: I did not bother downloading the upgraded texture pack (thankfully). The PMDG delivered 15+ FPS/Smoothness in comparison to the A310. This indicates more optimization work is required (at a minimum). Otherwise, it does have a lot of promise - very reminiscent of flying the Level D 767 (systems & displays) back in earlier iterations of FS.

The "hate" or "anger" being expressed all over social media platforms is a sad state of the times. Whether directed at PMDG or any other dev. And it's only becoming increasingly worse. Largely, it is mis-directed and out of all proportion. And from my observations, this pandemic has certainly exponentially blown the magnitude of modern day anger/stress levels right through the stratosphere and many are not coping and finding ways to vent albeit not so productively. As if modern day living wasn't stressful enough. Most of what I've seen in forums for MSFS are nothing more than "storms in tea-cups" but the fervour from many are way out of proportion and context....... for the reason pointed out above.

In terms of the EFB, why has Fenix and PMDG only opted for Navigraph? Why not let users choose their own source for charts etc? It's clear that there may be a monetary mutual benefit for all devs concerned......but consumer choice should also apply. I hope that both devs wake up (and any future devs).

Could be your hardware ie CPU handles the pressure with ease. My CPU is older than yours and OC'd. It isn't running high and handling MSFS quite well for the most part. I'm just lightly perplexed as to why some non-US PG cities are adversely impacting the US PG cities, at least on my rig (and some other users also).

I'm relatively new to this discovery. I've tried this (deleting PG cities other than US) and it definitely worked for me. What would be really interesting to know, is how many users are experiencing this phenomena. I hope Asobo/MS devote some time to resolving this so that the need to uninstall PG is no longer necessary.

Thanks for this info Fielder. I can say that the Aus PG is not creating an adverse issue on the US PG, at least on my end. I just tested this yesterday and confirmed it. I'm now seriously considering further testing to see if there are any other non-US PG areas that do not interfere with the US PG areas in an effort to isolate.