Ok, thanks!
I suspected it but why is it available with the basic tbm? ![]()
NEXRAD is displayed at all ranges below the selected maximum.
It was probably an oversight. There’s a lot of nonprototypical features in the vanilla avionics.
Because Asobo does not seem to understand the basics of aeronautics sometimes … ISA deviation is also wrong on both the default and modded G3000.
@aznricepuff I’ve made some observations on the G3000, or should I say, G5000, as I haven’t yet tried other planes like the TBM930, but only G5000 planes like the Longitude. I notice that the flight path marker has two issues, actually 3:
-
It is too small compared to real life.
-
Sometimes it gets partially or totally hidden behind the terrain or something depending on your pitch or attitude. Is there a way to bring it to the front so it never gets obscured by any other portion of the terrain or whatever on the PFD?
-
While on approach, it kinda confuses the pilot (me) because although I’m sure that I’m maintaining a -3.00 degree glideslope, it’s always at less than -2.5 degrees, give or take around -2.00.
Also, the greens (engine parameters, etc) on the MFD and on the annunciator bar of the PFD are too dark. Should be the same shade as the VOR and LOC bars, and the FPM. They should all be the same shade of green and that shade is the ILS green shade. Take a look at the pics, on the MFD the greens are brighter and there are no white outer circles. It’s all green and thicker, and the pointers originate from the center, if you look at the photo taken from inside the real life Longitude.
This is what we have now:
Compare with these two pics from the IRL Longitude G5000. First the PFD. Notice that:
-
The attitude indicator is white and not yellow, also notice the shape.
-
Look at the AoA indicator, and you will notice that the default position is on 0.2, and that is at the bottom, as there are no negative degrees in AoA, so the bottom is 0.2, the center is 0.6 (green dot indicates where you should be for a good approach speed) and the red extreme is 1.0. But on the sim AoA indicator, my guess is that Asobo mistook the center carat as the default position, giving the false impression that AoA could go negative! So in the sim, the center (tick mark) is 0.0 and the red is 1.0, and the lower extreme is probably -1.0 which is useless.
-
Notice the shade of green on the green arrow on the annunciator bar on top
Now the MFD. Notice the following:
-
The engine gauges. They’re brighter green and have no white outer circle. Rather they’re just green and thick, and the pointers originate from the center.
-
You can also see other things like the gear indicator (it’s green and “DN” when down, but white and “UP” when up).
-
The flaps symbol. Notice how thin the wing cross section is compared to the sim, and the indicator has positions. Also the trims with their green zones.
I don’t know if these are possible to modify in the working title mod but I believe brightening the greens are possible:
Can someone please tell me how to access the split screen in the G3000 in teh TBM930 in 0.4.0. I can’t find it.
Thank you!
On the Longitude A/C ,this may have been brought up before but I have noticed that if you set the V speeds on the centre GPS panels, they are not reflected in the capt side panel. e.g if you set a V1 of 100Ks in the centre, the side panel V1 indication is blank. Any Ideas.
Just want to check if this is still a known problem that if I select an approach via the PROG Page and activate it/ or select a direct to the TBM turns around suddenly and make a 180 to a complete other direction?
The problem still exist.
Ok thx for the reply!
Hello!
In this new and actual G3000 Mod, I loose significantly my FPS after about 1 hour of flight time!
In the last mod, i didn’t have this problem. I have about 50 FPS and after a while it drops to 33 FPS.
Thats not a normal behaviour. In the external view, I get about 65 FPS
The same thing happens to me! The framerate gradually diminishes from 42FPS to around 20FPS depending on how long I’ve Bern flying.
this must be a bug ![]()
… with the RTX 3090 and the I-9 10900 OC and 64 GB RAM - its a shame ![]()
@DiBarkis and here we go again with the previous version 0.3.4 =)
I’ve just raised that issue at the Working Title’s issues page on Github. Hopefully they’ll address it.
I also got a reply from one of the modders saying that they’re aware of this issue, and that he is in fact debugging it right now.
thanks dor the info! hope they will fix it soon ![]()
yes same for me, before making such change in the flight plan select HDG->make your change and go back in FMS navigation.








