August 30, 20214 yr Sorry guys 😉 mostly I fly classic birds with classic gauges but started to test more MSFS. On my desk now is Cirrus SR22. I can't quite figure out how some default G1000 functions work. For example this GPS path (flight plan is active). I think this path (purple, GPS path) should be able to turn by knob, so that the lines intersect. I'm on the path almost perfectly right now but it shows 3 o'clock, not 12 - I cant use any knob here to rotate these purple lines (so something like on VOR gauge). I missed something or its a bug? I noticed also few bugs with autopilot also but this is different story.  Edited August 30, 20214 yr by YoYo Webmaster of yoyosims.pl.Win 10 64, i9 9900k, RTX 3090 24Gb, RAM32Gb, SSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5 [MSFS, P3Dv5, DCS, RoF, Condor, IL-2 CoD/BoX] VR fly only: HP Reverb G2
August 30, 20214 yr 38 minutes ago, YoYo said: Sorry guys 😉 mostly I fly classic birds with classic gauges but started to test more MSFS. On my desk now is Cirrus SR22. I can't quite figure out how some default G1000 functions work. For example this GPS path (flight plan is active). I think this path (purple, GPS path) should be able to turn by knob, so that the lines intersect. I'm on the path almost perfectly right now but it shows 3 o'clock, not 12 - I cant use any knob here to rotate these purple lines (so something like on VOR gauge). I missed something or its a bug? I noticed also few bugs with autopilot also but this is different story.  I'm not a huge technical flyer, but to me, tyour display is showing you flying to the heading (HDG button) rather than using the GPS which is the NAV button. You are spot on the heading, but if you swap that to pressing NAV, you should turn and follow the magenta line. If you want to fly to HDG and manually follow the magenta line, use the knob on the left marked HDG and turn it to match the magenta line and then correct for offset by changing the heading. Sorry if | am not understanding what you are trying to do here:)  Graham  Edited August 30, 20214 yr by Moria15 System specs...  CPU AMD5950, GPU AMD6900XT, ROG crosshair VIII Hero motherboard, Corsair 64 gig LPX 3600 mem, Air cooling on GPU,  Kraken x pump cooling on CPU. Samsung G7 curved 27" monitor at 2k resolution ULTRA default settings.
August 30, 20214 yr Author 3 minutes ago, Moria15 said: I'm not a huge technical flyer, but to me, tyour display is showing you flying to the heading (HDG button) rather than using the GPS which is the NAV button. You are spot on the heading, but if you swap that to pressing NAV, you should turn and follow the magenta line.  Graham  Thx Graham. In this situation, direct path for GPS it was course 120, as on HDG (here autopilot is on for 120 degrees, so my airport is straight ahead). Maybe here the path is fixed and cant be modified (I started to think) because I can see now the direction LDSB to TIME (top of the screen), not direct to direct airport (like for example in FSX/P3D). Strange. Webmaster of yoyosims.pl.Win 10 64, i9 9900k, RTX 3090 24Gb, RAM32Gb, SSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5 [MSFS, P3Dv5, DCS, RoF, Condor, IL-2 CoD/BoX] VR fly only: HP Reverb G2
August 30, 20214 yr 41 minutes ago, YoYo said: I think this path (purple, GPS path) should be able to turn by knob, so that the lines intersect. I'm on the path almost perfectly right now but it shows 3 o'clock, not 12 - I cant use any knob here to rotate these purple lines (so something like on VOR gauge).  You seem to be in heading mode;  since you're precisely on the heading that your heading bug is sent to, the flight director thinks you're exactly where you want to be.  If you switch your AP mode to NAV, and then make sure that the CDI is set to GPS, it should do what you expect. (You might want to turn to an intercept course for your track, first, to make it a bit smoother. It'd also be required, IRL, for nav to capture in some cases, though IIRC the stock G1000 doesn't care.)
August 30, 20214 yr Author As I noticed, the course here is always drawn as a "zig zag" (no direct line between airports), so maybe this. Thx, will try more. Edited August 30, 20214 yr by YoYo Webmaster of yoyosims.pl.Win 10 64, i9 9900k, RTX 3090 24Gb, RAM32Gb, SSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5 [MSFS, P3Dv5, DCS, RoF, Condor, IL-2 CoD/BoX] VR fly only: HP Reverb G2
August 30, 20214 yr 6 minutes ago, YoYo said: Maybe here the path is fixed and cant be modified (I started to think) because I can see now the direction LDSB to TIME (top of the screen), not direct to direct airport (like for example in FSX/P3D). Yeah, the TIME waypoint you have there is a sim-specific thing added in SU5 that really shouldn't show up in the G1000. (I believe its presence is a bug -- we explicitly exclude them in the NXi just to be safe). At this point, based on the distance and XTE, it looks like going to that waypoint is going to take you way out of your way. The best thing to do at this point, if you have free reign, is probably just to create a direct-to from your current location to your destination, that should give you a more direct course.
August 30, 20214 yr Author 31 minutes ago, kaosfere said: eah, the TIME waypoint you have there is a sim-specific thing added in SU5 that really shouldn't show up in the G1000. (I believe its presence is a bug -- we explicitly exclude them in the NXi just to be safe). At this point, based on the distance and XTE, it looks like going to that waypoint is going to take you way out of your way. The best thing to do at this point, if you have free reign, is probably just to create a direct-to from your current location to your destination, that should give you a more direct course. Now it ok, sorry its VR screen, thx for help! Webmaster of yoyosims.pl.Win 10 64, i9 9900k, RTX 3090 24Gb, RAM32Gb, SSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5 [MSFS, P3Dv5, DCS, RoF, Condor, IL-2 CoD/BoX] VR fly only: HP Reverb G2
Archived
This topic is now archived and is closed to further replies.