Cool, I'm gonna take some cool shots.
BTW, why don't we provide some more attractive media on the website.
How about some short movies like seahawk taking off from Nimitz?
Two aircraft passing by in MP session also would be very attractive to users.
On Dec 14, 2007, at 9:43 PM, Melchior FRANZ wrote:
> For a new release, especially one with version number 1.0, we
> should provide some new screenshots for the website. Normally,
> Curt would ask for that, but as he is/was away for a few days,
> I start with this reminder. Screenshots should ...
> - use maximum quality (antialiasing!)
> - disable gui parts (menu/frame rate counter, unless that's what
> you want to demonstrate, of course)
> - ideally (but not necessarily) show something that is new in this
> release: one of the aircraft shipped in the default package for
> the first time, or a new feature (or at least something that is
> in context with a new feature, so that a subscription text can
> explain the feature)
> Please don't just make random snapshots of random flights, but
> aim for a good view angle, appropriate weather effects (not only
> default weather, unless that's the most appropriate :-), ideal
> sun angle (shadow angle -> self-shadowing), etc. Look at some
> of the last screenshots, most of which were quite good.
> The contents of a screenshot shouldn't be (totally) cheated. That
> is: one should be able to see the same scene with a default fgfs
> if the weather, daytime etc. is the same (and one has a graphics
> card good enough for real-time antialiasing). But some "cheating" is
> acceptable, if it follows this principle. It's OK to use terrain/objects
> that aren't in the default tiles (e.g. using KNID is fine), as
> long as that's available from Jon's ObjectDB. It's *not* OK to show,
> for example, a Jeep in a Hercules, as this isn't something we can
> do with a flyable Hercules.
> Unfortunately, my FX5500 isn't good enough for live antialiasing,
> so I use an acceptable cheating method: from a local key binding
> (Meta-d) I call a function dump_aircraft_snapshot() that saves
> a snapshot, similar to what ac_state.nas does. This allows me to
> make a normal ("aliasing") flight with my target aircraft. When I
> found a nice situation, I pause fgfs, then press the snapshot key,
> and get a snapshot file, e.g ~/.fgfs/snapshot-KNID-A-10-1.xml
> (automatically inserting the nearest airport and aircraft, as well
> as an index number that prevents overwriting old files).
> Now I turn on full anti-aliasing, and run fgfs again with
> $ fgfs --aircraft=ufo ~/.fgfs/snapshot-KNID-A-10-1.xml
> And now the A-10 hangs there like it did in the prior run, and
> I can use the UFO to find a good viewing angle, good sun angle,
> good weather etc. With full antialiasing that's still sluggish,
> but workable.
> Here's the result of a quick test with the A-10 near KNID. It
> isn't spectacular, but you can see that there's full antialiasing
> and still a nice shadow effect. This would have been quite hard
> (though possible!) with a real A-10 flight.
> http://members.aon.at/mfranz/a10.jpg [32.9 kB]
> SF.Net email is sponsored by:
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services
> for just about anything Open Source.
> Flightgear-devel mailing list