>>2667381Not that guy (I'm
>>2667305 ) but few consumer cameras are able to shoot continuously for a prolonged period of time. Before the images are transcribed from the sensor to card, they're put in a buffer and said buffer's capacity is obviously limited. The faster you shoot (and the bigger the files are — you're better off shooting raw, the largest possible files which allow for better postprocessing — or you could be lazy and trust your camera to process the colors), the quicker the buffer fills up, leaving you unable to shoot at all until the buffer empties a little.
Sure, there are some intense moments during the group flying you wouldn't want to miss where such burst ability would come in handy but most of the time you won't need more than, say, 3 fps. My camera can do 6 but I usually set it on 3 or 4, occasionally flipping to 6 but I can sustain that rate for only 2-4 seconds anyway (my main SD card is 80 MB/s). Bear in mind, on more advanced bodies it takes one flick of a finger to switch between modes but on cheaper ones you'll probably have to go to menu or just get used to shooting in small controlled bursts. A few times leaving the camera in 3 or 4 fps mode cost me a picture though. Picrelated is one of such moments missed by milliseconds (pls no bully for 3000 px wide, it's still smaller than 1 MB, otherwise I would have shrunk it).
As for the shutter speed, on a bright day you'll be shooting at 1/500 or faster anyway (except for when you'll want to blur the props or rotors a little).
Also, make sure you understand how metering works. Say, if it's set to average then it's going to meter the whole frame which will be >90% of light blue sky or white clouds and <10% of a considerably darker aircraft hull against it — especially when against the sun — and will set the value to average of that, making the aircraft severely underexposed. This can be fixed in postprocessing to a degree when shooting raw but it won't do the image any favors.
