i had this exact thing happen to me as well. Are you running the Working Title Garmin mods?
Yes i am. Switched to the newest version .4 today and no issues so far!
I love this new Working Title G3000 v0.4.0 beta! The colors are now much closer to reality than before although especially the terrain. I still have these negatives though:
- The sky is still too dark.
- The fpm is still too small
- The greens on the engine gauges & numbers, and the green fonts on the annunciator bar are still too dark (should be the same color as the NAV1/2/ILS green or the fpm)
1 Like
Splitscreen is nice too
A little help please!
Where can i download the Working Title G3000 v0.4.0 Beta?
The version i have currently is g3000-v0.3.4
Best Regards
on their discord, section garmin
Is there any reference to the best climbing speeds, VS, and cruising altitudes with this mod? Thanks?
Depending on the runway altitude, air temp., fuel% ,payload, headwinds.
Normally, to prevent rocketed climb and then overspeed (>250KIAs) at early1500ft above ground, once after take off, hold throttle = 70~75% with VS=3300, that it would speed up slowly, until 233~246 KIAS, and tweak VS in cloud layers. I arm A/T at 238KIAS and set VS=1300 from FL100 to FL380 cruise at mach 0.83.
thought it was 250kt until 10 000ā , than 270kt until about FL300 to switch M0.76(around 435TAS IIRC) for the rest of the climb
1 Like
Thanks - this is more accurate and realistic to IRL and works best with the mod. Could also go with 250 to 10k, 300KIAS to wherever intercept approx 435 TAS and then maintain 435 TAS to cruise altitude (410, 430, 450). Mod is optimized for most accuracy in cruise at FL430. IRL the ac can high speed climb from FL300 to cruise altitude at about M0.8 (458 TAS). The mod wonāt do this as well as Iād like. Itās a complicated answer why, but will just say itās a compromise between cruise performance (target fuel burn and N1) and climb performance and solely as a result of some of the underlying Asobo turbine modeling.
Good stuff, thanks friends!
When I arrive to the approax zone, the white track mark and the waypints in the flightplan disappear. Whats wrong? I was in a rnav approach
Seems to be a bug in the G 3000 mod I think
1 Like
its a bug with the G3000. download Working Title beta 0.4 to fix it
Quick update on this oneā¦with the latest beta version of the WT G3000 my workaround doesnāt work around anymore. 
Hi, at FL390 my maximum N1 is 90% and N2 is 76% (although full throttle). Are these values normal? Seems a bit lowā¦
I had it already and it happens too
Latest update must corrupt 1.51? Noticed when selecting NAV the aircraft starts circling then crashes! Replace update 1.51 and aircraft is working as designed.
Yeah, I knew something was off immediately after having to us 40% N1 to start my taxi roll. Reinstalling 1.51. If I donāt reply, consider the matter fixed on my end.
All:
There was a āsmallā Asobo update today - at least that affected me. The patch notes indicated changes were made to Longitude. However, the default version 0.1.54 of Longitude didnāt change wrt to the Dec. 22 version. I didnāt see any effect on my modification project - it worked as expected and none of the default Longitude files were updated (saw no date changes on the default files). I did take the extra step to remove my mod, removed the default longitude, and then reinstalled default to see if perhaps I missed something. Nope - default is still at version 0.1.54 - same as from Dec. 22. As I mentioned already, the patch notes suggested changes were made to Longitude, but if so, I didnāt see anything notable in the behavior of the default. Still saw that issue with Nav hold where the a/c was rocking back and forth unable to hold the course line. Still same old issues with the a/c modeling as I saw on Dec. 22 as well as the improvements Asobo made. Maybe some of you are seeing something different - if so, iād like to know in case I need to post update instructions or possibly an updated installer.
3 Likes