Business is shut down for the virus, my engine is at DA for service so I can’t practice, and this forum is quiet. So it’s time for thinking and a question.
I’m moving up from Basic to Sportsman this year. One difference is Sportsman introduces snaps. Just one in the Known and I suspect no more than that the Unknown. They're limited to positive, exactly one full rotation, and on horizontal lines. So they’re simple and few.
Snaps of course need different control deflections than normal precision flight. For learning snaps at this level, do people find it best to start programming snap conditions right from the start, or have a single condition for precision+snaps and hold off on the programming til later?
For upper categories with more/difficult/varied snaps, conditions based on stick positions are a godsend. For just starting to learn snaps, I'd be concerned that when a snap doesn’t go well, it could be difficult to know whether it's caused by poor technique (most likely!) or a programming/deflection problem (almost as likely!). That would seem to make isolating the right fix more difficult.
The other option would be to use a single condition for everything, with deflections needed for snaps, then dial them way back with expo to smooth the response for precision. The problem there is you’re limiting the stick travel you can use for precision flight. That seems like a bad idea for a few reasons.
Here’s what I’m thinking to start. Set up snap rates on a physical switch so I always know exactly what's active. Turn it on to practice snaps. Flip it back to precision condition to practice everything that isn’t a snap. Once my snaps are consistent, move the snap rates to a logical condition. Then if my snaps suddenly become more of a freak show than they already are, it’s probably the programming.
Any advice or thoughts?
I’m moving up from Basic to Sportsman this year. One difference is Sportsman introduces snaps. Just one in the Known and I suspect no more than that the Unknown. They're limited to positive, exactly one full rotation, and on horizontal lines. So they’re simple and few.
Snaps of course need different control deflections than normal precision flight. For learning snaps at this level, do people find it best to start programming snap conditions right from the start, or have a single condition for precision+snaps and hold off on the programming til later?
For upper categories with more/difficult/varied snaps, conditions based on stick positions are a godsend. For just starting to learn snaps, I'd be concerned that when a snap doesn’t go well, it could be difficult to know whether it's caused by poor technique (most likely!) or a programming/deflection problem (almost as likely!). That would seem to make isolating the right fix more difficult.
The other option would be to use a single condition for everything, with deflections needed for snaps, then dial them way back with expo to smooth the response for precision. The problem there is you’re limiting the stick travel you can use for precision flight. That seems like a bad idea for a few reasons.
Here’s what I’m thinking to start. Set up snap rates on a physical switch so I always know exactly what's active. Turn it on to practice snaps. Flip it back to precision condition to practice everything that isn’t a snap. Once my snaps are consistent, move the snap rates to a logical condition. Then if my snaps suddenly become more of a freak show than they already are, it’s probably the programming.
Any advice or thoughts?
Comment