After the patch 1.9.5, the avionics dimmer no longer controls the G1000 in the C172. Anyone else seeing this?
RESOLVED: Not sure which fixed this, but I updated to 3.1 version of the mod (from 3.1 Pre 1&2) and rebooted.. Now it is working as expected. Thanks for a great mod!
1 Like
Ok. Iāve downloaded and unzipped the file in Windows. Do I just copy the entire contents of the file into the community file then it should work?
Thanks.
Your Community folder should look something like this (depending on what all you installed):
Inside your āworkingtitle-g1000ā folder you should have a manifest file and SimObjects folder and other stuff.
Thanks for your speedy reply. Does the contents have to be in a file titled āworkingtitle-g1000ā within the community folder?
no, but thatās the name it has alrady.
Are there any plans to have the G1000 remember the inset setting for the PFD like it does for the wind setting? I prefer the PFD inset off, but have to do this each flight.
It seems that certain people (like me) require some sort of order in their lives. So it is 100% ok to change the master folder name. I use this protocol U_workingtitle-g1000 where U_ = Utility, S_ = Scenery, A_ = Aircraft etc but I leave the big boys intact ie Gaya, Carenado, ORBX etc
1 Like
I ended up creating a folder and put everything in the folder and now itās working. It apparently needs to be in a folder, not having all the files sitting openly in the community folder.
Thanks again.
Just make sure that for instance when using this G1000 mod and the G36 aircraft mod, you donāt use your U_ and A_ prefixes for them since the G36 mod needs to be loaded after the G1000 (your U_ and A_ prefixes would do it the other way).
Most mods are fine in random order, but some have dependencies like that and renaming the default names provided by the mods will cause issues.
1 Like
Good point! Iām not using the G36 mod currently but I may in the future so thanks for the heads up.
1 Like
I use numbering with the 100s meaning series or groups of mods.
000 - 100 = game/UI fixes
100 - 200 = mods with larger scope (the Garmin mods mostly)
200 - 300 = specific aircraft mods
For example:
001 - No Tool Tips
101 - Working Title G1000
125 - Working Title G3000
201 - G36
225 - TBM 930
250 - DA62X
etc, etc
This makes things pretty easy to rearrange if Iām figuring out conflicts. I donāt use liveries or other types of mods but the numbering scheme can be easily expanded to accommodate those.
Hey folks, been busy for a few days, sorry. Let me get caught up.
0.3.0 did. 0.3.1 fixes that, it can be downloaded at the top of the thread.
Probably. Iāll add an issue for it for the next major release.
Almost certainly, and ditto.
This should work fine with any twin engine that has the G1000. Have you found otherwise?
Very easily done. Added to the wishlist.
You might find it easier to just use the MSFS Addon Linker. Doing development I swap a lot of mods in and out and itās a lifesaver. You can keep all your mods in any structure you wish and it takes care of linking everything you have active into the Community directory. I have, for example, broken the livery megapack into folders for each plane and can toggle and entire planeās worth of liveries on and off with one click. Similarly I put my scenery into folders by geographic area and can enable and disable them just as eaisly.
3 Likes
Oh awesome, thank you
Hello,
When i use the workingtitle-g3000, and the workingtittle-g1000 i have a strange bug: i canāt cold start any plane equiped with a g1000. The Rpm doesnāt kick in, the oild presure never riseā¦Even CTRL-E wonāt start the engine.
Any idea ?
I havenāt change any name.
i weirdly had the same thing happen, i went to fly the c152 and it would not kick over, very weird.
Update to the new G3000 version. There was a conflict bug that rendered G1000 inoperable. It has since been resolved.
1 Like
Noticed today this combination (latest v0.3.1 installed):
Standing on the ground at UUMB and tuned into NAV1 the ILS of UUWW RWY06.
Top left shows an ident of the ILS but BRG1 at the bottom shows NO DATA. Shouldnāt it at least show the ident? Or is that display to be expected while on the ground (and far off the ILS glideslope)?
Lots of places you canāt pick up the VOR or ILS on the ground. ILS is pretty narrow beam too.
Unfortunatly even with the 3.1 and [g3000-v0.2.0-pre2] the bug is still presentā¦
But would you still pick up the ident? Or is that taken from the database instead?