Haha. Some of the underlying logic for this was already included by Asobo in the sim and was already in use with the airliners. And their original code references heading, for example:
if (this.bRotateWithAirplane && !this.isDisplayingWeatherRadar()) {
var compass = SimVar.GetSimVarValue("PLANE HEADING DEGREES TRUE", "degree")
var roundedCompass = fastToFixed(compass, 3);
transform = "rotate(" + -roundedCompass + "deg)";
}
We just made more stuff use that. But I suppose you are technically correct ā which as we all know is the best kind of correct. It is indeed heading-up, not track-up. This is something we can make more canonically correct since it is, indeed, correct.
Iām having an issue where none of my screens show any display. This is in conjunction with the G36 mod v5 release. Iām fairly certain the avionics are live, as I can contact ATC through the sim dropdown menu. Only things in my Community folder are these mods, as any liveries are still out from yesterdayās patch. I had no issue running the G1000 mod v2 prior to the patch, and have made no changes in my sim since the patch.
When I put the G1000 file in my community folder, I am told the file names(s) would be too long for the destination folder.
AttitudeIndicator
It also errors with another file
Did you try removing the mods and see if the base game works for you? Then just add the G1000 mod and see if it works. Then youāll know which mod might cause the issue.
Also I guess you checked the brightness of your displays already?
Is there a difference if you start cold&dark and start everything up manually?
Does it happen if you fly without any other traffic?
You have to help here on the troubleshooting since seemingly most people are not affected by this issue.
Indeed, Iām the only one I found with this issue, so I knew it was on my end. Was off trying a few things, and traced the issue to a Windows update this morning that seemingly killed my ability to add either mod correctly to the Community folder due to a Path Too Long error. Changing the registry for LongPathEnabled (or whatever that tag was called) didnāt work, presumably because I have MSFS on an external SSD, so I had to move the mods over to the Community folder with Powershell, which worked. Everything is working well now, both mods are remarkable!
Now to research why Windows is trying to give me gray hair before my timeā¦
The Powershell thing, sure. Just follow the instructions on this webpage: https://helpdeskgeek.com/how-to/how-to-fix-filename-is-too-long-issue-in-windows/
I extracted the modās zip to a folder on the same drive as my sim install, then opened up both that location and the Community folder in Windows Explorer, so I could easily copy the long folder location into Powershell, and I could see the folder arrive in the Community folder and check it right away for completeness.
In my case, in Powershell I navigated to where I put the unzipped mod, E:\MSFS_addons. Then typed āCopy-Item workingtitle-g1000 -Destination E:\WpSystem\ (etc etc, etc) \Community -Recurseā (no quotations in powershell, though).
See my post above Picka, sounds like you have a similar problem. I assume you installed to a different drive like I did but only specified a drive letter, not a folder. Makes for a ridiculously long location chain. Iām contemplating a fresh install, but I really donāt want toā¦
Just go to C:User/AppData/Local/Packages/microsoft.fligh(and a giant name)/Localcache/packages and will be able to paste or extract. if you use shorter patch of some other disk will get this error in some files, or just hack the registry
If i have this mod installed i lose the synthetic vision that comes in the standard King Air. I end up with the brown/blue synthetic vision off look of the g1000. i canāt find any way to turn synthetic vision back on through any menus in the king air, as i wouldnāt expect there to be since this is a g1000 mod.
