then i’m lucky to not fly irl today. I can remember bad SW inside MAX with more fatal accidents.
Also my mentioned problem flight,
it can be easy bypassed with quick set heading nav instead of NAV with gps/fms option. Then hit Direct to NIT and all is working till landing Therefore is clear to me that if (screenshot my from nxi sfter delete sid) garmin continue as fpl shows then no problem. If you look carefully, FPL shows correct actual state but screen not.
Update due not good topic rule to wait for some other posts prior write another after 3. I think this is very important topic so maybe Mods can change this rule.
just another problem but same as previously with departure from LZPP in GTN750 topic. I don’t think so is GTN750 problem because it use WTT system. My Seneca is parking as on picture. After set departure rwy01 (LZKZ) it set this nonsence departure track, not rwy01 straight ahead to first dep fix as need to be, this is also problem that I reported at GTN750 topic with C172 with NXi. Just tip, in case I’m on rwy 01 start point and then set departure, it looks then ok so this is bug also. Everytime it depends to actual aircraft heading for dep initial heading what is wrong.
This is just because you’re parked and the initial runway point doesn’t come with a heading, by definition. This will resolve itself when you turn the right way on the runway.
nothing did ok when I turned to runway, all stay same and after dep and I set AP, my aircraft was driffted away left to catch that teardrop nonsence. As I said previously, if I put my aircraft to runway point and then define SID, all is ok so this is bug. Set of correct SID doesn’t need to be depended to actual aircraft heading or parking position, it need to be simply defined from init point of runway to runway heading and next dep fix. Look at picture, this is if I set SID at runway and is correct:
As I expected, did uninstall WTT G1000 NXi and set stock Asobo system and all is as need to be working heh no my parking and heading my aircraft depended, SID is defined correctly:
Guys pls, you need look deeply to this because we don’t have chance then fly correctly with WTT system, especially NXi here. I’ll do tests with WTT G3000 and TMB930 now to have hope final look where the problem is.
HMMMM on other side it looks to me now that points are swapped, look to your defined point of start at my previous screenshots and this from Asobo stock G1000. At Asobo red line started from end of runway01 what is different to yours. Simply therefore i expected that teardrop maybe defined wrongly because defined oposite start runway point at your WTT G1000 Nxi??? Then logically if points are swapped then some calculated procedure turn is set and that is your not correct SID definition, isn’t it?
heh now looks to me that NXi and G3000 from WTT are prepared with different programmer They don’t use same nav code (I expect maybe same system here as basic principle) so this is then definitelly WTT G1000 NXi problem. Am I right with that my idea about swapped rwy point? This looks like that I was right, or?
thnx for that, really now I’m totaly out of reality what was working with what system but with today findings with WTG3000 and strange turn defined after delete arrival points it can be very true, same I saw on stock G1000 long time ago.
Update: yes I remember an very old topic with strange defined arrival procedure from one woman’s topic/post? Yes, like drunk whiskey 2 arrival zig zag thnx for your info and hope for quick solutions.
Please let me know if this belongs in a separate thread or anything, but I have a question regarding behavior of the various of the G1000 NXI’s knobs in terms of the rate of adjustments to the target heading, altitude, airspeed, or vertical speed.
When using an external input device such as the Honeycomb Bravo, people seem to have inconsistent experiences with the speed of changes made – either they see a flat speed per click, and feel it is too slow, or (like me), they see a 10x acceleration spike after a few clicks and find this too aggressive.
There’s a separate thread on this topic, but I don’t think there’s much anybody can do to progress it because it seems to be a one-size-fits-all acceleration system that applies to every input through the PLUS and MINUS bindings, when presumably every simulated device might have a different input system that behaves differently.
So my question is: how does the actual G1000 NXi behave with respect to scaling the rate/count of knob-turning events into output degrees/100s-of-feet/knots? And will that be supported realistically in the sim?
The real G1000 has no knob acceleration at all. The ALT knob is a dual concentric knob where the outer knob is increments of 1000 and the inner knob is increments of 100. This is already supported by the sim: external software can send an increment amount with the INC and DEC key events to get a flat increment with no acceleration.
However, the Bravo doesn’t have a dual concentric knob, so I don’t really see how it could simulate the G1000 alt knob behavior.
Sorry for being off-topic, but I have “solved” it with SPAD.neXt. There are several ways to achieve this, but my solution is an acceleration button on the yoke.
Not in any detail, because this is not the thread for that.
But I have configured SPAD.neXt in such a way that when I hold down a button on my Alpha yoke, and turn the Bravo knob in ALT mode, it will work in 1000-feet increments. If you own SPAD.neXt and have learned how to use its most basic features, this one is trivial.
SPAD.neXt is just one of several products that can do this and much more for your flight control hardware.
Can confirm, I use this approach with spad.next and my Virpil cm3 throttle such that when I push in a knob while rotating it, it does the larger increment/decrement, and simply twisting it without pressing does the smaller one.
I use this for altitude but also my com frequencies Ava a similar approach to binding the g1000 MFD knob. Works really well except occasional instances where I accidentally let up on the knob press.
Ok so i’m not sure the name of the terminology (does it show with the title?)
But basically i was wondering if there was a way with the current G1000 Working Title to show the arc indicator on the centre screen that shows where you will be when your desired descent altitude has been achieved? I’ve seen it before on videos but never been able to put it on myself.
Therefore is clear to me that if (screenshot my from nxi sfter delete sid) garmin continue as fpl shows then no problem. If you look carefully, FPL shows correct actual state but screen not.
but with today findings with WTG3000 and strange turn defined after delete arrival points it can be very true, same I saw on stock G1000 long time ago.
