I’m on X Box and in the beta (currently 1.4.12.0). While on 1.4.11.0, I had to completely reinstall and start over from scratch. I usually just delete the reserved space but this issue (a settings issue forced ToolTips to be ON with no way of turning them OFF) – this issue forced me to delete my cloud profile.
The G1000 changed when I did this and I don’t at all understand why or how. For a very long time now the MFD has looked like this:
Whatever changes were made did not take effect for me until I did this complete reinstall. I’m posting this in the hopes that it helps somebody somewhere – or maybe all of us if Asobo/MS can figure out why changes made are not actually being imposed. The cache is preventing the new version from taking hold completely. What my profile had to do with this I have no idea but I’ve deleted the reserved space on my X Box a number of times and always kept that same default G1000 look. (MFD circle instead of arc and North up vs Track up)
of course it is possible these changes were made at the same time I reinstalled…hmmm…
I’m aware that settings like ‘North Up’ or ‘Track Up’ can be selected in the menu system but this isn’t about what can be selected. Its about the default installation.
I’m a person who changes as few settings as possible when a program is in a beta state because I know things may change, may not work right, and will make bugs harder for me to identify. Both pics show ‘the default G1000’ appearance. The two pics show different ‘default G1000’ appearances. This means the code is different.
The code changed but that code change never made it to my machine. Why?
Thats what this is about. I would think that, in order for a program to work properly and as intended, the current baseline code that the developers are working on should be the same baseline code that exists on our machines but yet that is not the case in this instance which means that it may not be the case in other instances.
This is the basic reasoning behind complete reinstalls. Sometimes code gets stored in a cache and, although its supposed to get wiped out and replaced during an update, it doesn’t always succeed.
My experience is just a small example of how the updating process may not be perfect and may explain the bad performance some people experience.
Its also possible the code got updated at the same time I performed my complete reinstall. Another possibility is that this particular code was seen as irrelevant and so the older appearance was left alone but I personally would rather have the latest intended version of code to make certain that Im on the same page as the developers as it were. It might be nothing but I thought I should report it just in case.
Does the G1000 have state saving? I’m not sure it does but that would explain why a remove, and reinstall would make no difference. You would have to remove the state saving data as well.
I’m on X Box and I deleted both the Reserved Space and my cloud profile which should have (and apparently did) remove all traces that FS2024 had ever been installed anywhere. I can’t imagine an addon that could have affected this. I only have airports and planes and Im on XBox which limits the addon capability.
Does the G1000 MFD look like the first pic or the second for you guys? Notice the circle around the plane icon versus the arc above it.
I just figure a new version of the G1000 came out but I didnt have it until I did the complete reinstall. Who knows how many others may also have older bits of code. I probably shouldn’t have said anything.
One thing though for any X Box users who may have the sim on more than one device – apparently you have to delete the cloud profile from the other devices before trying to delete your ‘home’ profile. it will just backup from your other device.
I’ll check tonight, but also be aware that the plane matters as some planes have different G1000’s in them. There are multiple versions of it, and I think there are still some that are not WT. I may have that last part wrong though.
That looks like the default G1000 172 though, unless I am mistaken, so should be easy to test.
The first time I decided to try the C172 G1000 I found it had to be the ‘Cargo’ version so thats what I was flying in the upper pic. I’m not sure what version is default right now but it has a "Euphoria Travels’ livery and thats where I saw the ‘new’ G1000. It may be that that G1000 has always existed but I just never saw it…Ill have to go see if there is still a ‘Cargo’ version with G1000 and what it looks like. I thought that Cargo version was the only one with a G1000 but I guess I was wrong. That may be it entirely…just different aircraft versions.
Deleting your cloud save will revert your saved G1000 settings, as that is where they are stored. Settings that are saved between sessions in the real unit are likewise saved between sessions in the sim unit. Each tail number and plane combination has unique saved settings.
If you get in one plane where you have changed the settings now, and then get in another plane where you have yet to, your settings on power-on will be different between the two aircraft, as expected.
There has been no code mixup during your reinstall, nor are there multiple versions of the 2024 G1000 NXi avionics running in SU2.
Some planes have heavily tweaked ones, but I guess you mean the base code by WT, and it’s up to developers to customise or not. Look at the SR22 for example. It has features the 172 G1000 does not.
After reinstallation of the sim, I made some changes to the G1000 settings in the plane that Asobo chose as the default (C172 G1000 non Cargo with Euphoria Travels livery - on my machine). Last night I started the Cargo version for the first time (since reinstall) and was surprised to see it had the ‘new’ G1000. It also had settings I had changed in the first (default) aircraft. I assume this is because all of my planes use the default assigned tail number.
If I change any planes tail number, I create a new set of settings that are ‘default’? So, if @hobanagerik changes the tail number on his Cargo version then he will see the new default G1000 that I see?
I really appreciate your input here because I could not figure out what my cloud save would have to do with anything.
I think you might be getting hung up on this “new” G1000 thing. What you are seeing is a different set of default MFD settings for some reason.
If that is the case, and there is some state saving at work here, then this can be on a plane per plane basis, but may also be per livery. Though that last part I’m not sure of.
In fact, you could test this yourself. When you spawn in, and you see the MFD is in either track up, or course up, change the MFD map to North Up. Confirm that this is the case. Now end the flight. Respawn with exactly the same configuration. If state saving is working you will see the MFD in North Up mode as you left it. If it has reverted, then state saving isn’t working, and something else is at work.
Not ‘hung up’ at all The ‘for some reason’ was explained by @Bishop398 .
I was actually expecting you might want to test the theory by changing the tail number on your Cargo version which should create a ‘new’ set of the latest default settings. All I mean by ‘new’ is the most recent container for settings.
I never made any customisations to my G1000, so what I saw in my image was default. I don’t know why, and have no reason to believe, that would ever change no matter what livery/variant or tail number I spawn in. As far as I am aware the default has always been North Up. So it makes me wonder why yours wasn’t.
On the PC version that are a series of per plane folders which hold some state saving information. One of the files is actually called “state.cfg”, and for most devs. the only thing this contains are the values for the Hobbs meter(s). Some devs make use of this file to store other information though, so if any plane does store or change this information, that would be the place to work.
A2A to is slightly differently, and have a database located elsewhere with their state information, but I believe that also has some information for other planes too, though their contents I don’t remember, nor the format, nor indeed if that even exists in 2024. The last time I looked in that location was in 2020.
I’ll let you know what I find.
It would be worth you running that test I mentioned. Changing the MFD map to the way you want, end the flight, then start it again without changing anything else to see if it remembers.
As mentioned previously, the state saving for the G1000 is in the cloud save and not in any particular user accessible files.
Not exactly. The G1000 has a set of default settings baked in. If it doesn’t find a particular saved setting key/value pair (a key being, for example, "G1000 map orientation for tail number N2713F’) then it will just load with the default baked in setting. If the user changes this setting in the avionics, then it will write “G1000 map orientation for tail number N2713F” to the cloud save, so it can be used next time the avionics load.
Well, we are WT. But, aside from I think the FSR500, which has a forked version of the G1000, all of the tweaked versions run the same exact code; instead that same code loads aircraft specific plugins that run any additional features on top.
So maybe their answer is that they changed it somehow, perhaps by accident, and doesn’t remember. I don’t ever remember spawning into a plane then seeing the MFD in anything other than North Up.
Doesn’t a local copy of that get pulled down into the “wgs” folder? I didn’t think to check there to be honest.
The ‘for some reason’ was explained by 
But, aside from I think the FSR500, which has a forked version of the G1000, all of the tweaked versions run the same exact code; instead that same code loads aircraft specific plugins that run any additional features on top.