4,400
edits
Presentation Recipe: Difference between revisions
Jump to navigation
Jump to search
m
Robot: Cosmetic changes
Martin.spott (talk | contribs) m (Add read-with-care notice) |
m (Robot: Cosmetic changes) |
||
| Line 1: | Line 1: | ||
This presentation recipe is intended to be very prescriptive about what you can do or demo. | This presentation recipe is intended to be very prescriptive about what you can do or demo. The presentation isn't so much a formal presentation, but what is needed to have [[FlightGear]] running in a booth. | ||
'''Note:''' From the perspective of somone who actually ''does'' public presentations of FlightGear, this list appears to have diverted into a rather unrelated feature wishlist. Therefore please read with care. | '''Note:''' From the perspective of somone who actually ''does'' public presentations of FlightGear, this list appears to have diverted into a rather unrelated feature wishlist. Therefore please read with care. | ||
As an alternative, check this [[ | As an alternative, check this [[FlightGear Expo Checklist]]. | ||
| Line 21: | Line 21: | ||
== Scenario == | == Scenario == | ||
The basic premise is that you don't want a demo to allow people to crash or involve a lot of time with people controlling the system rather than selling your wares. | The basic premise is that you don't want a demo to allow people to crash or involve a lot of time with people controlling the system rather than selling your wares. The basic premise is that the system can run unattended for a number of days without needing either a pilot or a technician on hand to babysit the system. | ||
Of course there will always be a Top Gun that walks past and wants to fly, the restart of the demo should be trivial as well... | Of course there will always be a Top Gun that walks past and wants to fly, the restart of the demo should be trivial as well... | ||
| Line 89: | Line 89: | ||
==== Prerecorded Flight Data ==== | ==== Prerecorded Flight Data ==== | ||
This is probably most important part. | This is probably most important part. Most people suck at flying aircraft with a mouse and keyboard, so having prerecorded data is must. Get your flight data from the [[Suggested Prerecorded Flights]] | ||
== Running the Demo == | == Running the Demo == | ||
| Line 103: | Line 103: | ||
=== User interaction === | === User interaction === | ||
The demo is on rails, the only thing that can be changed is the view by pressing "v". | The demo is on rails, the only thing that can be changed is the view by pressing "v". Right-clicking the mouse twice will allow you to adjust the view angle for the particular view that you want. | ||
== Tweaks == | == Tweaks == | ||
| Line 121: | Line 121: | ||
=== Preloading === | === Preloading === | ||
Since we are talking about multicore systems, one of those cores could at-risk pre-load the geometry and textures well before flightgear needs them. | Since we are talking about multicore systems, one of those cores could at-risk pre-load the geometry and textures well before flightgear needs them. This prevents the annoying stalls on the first pass through the recorded demo. | ||
=== Scripted Flights === | === Scripted Flights === | ||
| Line 129: | Line 129: | ||
=== More Traffic === | === More Traffic === | ||
Flying on your own is interesting, but having other things in the air is even better. | Flying on your own is interesting, but having other things in the air is even better. Having this recipe updated with extra links to data would be great. | ||
=== More Eyecandy === | === More Eyecandy === | ||
Without multiple monitors, FlightGear looks quite simplistic. | Without multiple monitors, FlightGear looks quite simplistic. Use of shaders and other visual touches would add to FlightGear's appeal. | ||
=== More Models === | === More Models === | ||