2
edits
Howto:Multi-computing FlightGear: Difference between revisions
Jump to navigation
Jump to search
m
→Minor typos and grammar
m (Robot: Cosmetic changes) |
|||
| Line 28: | Line 28: | ||
== Main Dish: The Master Machine == | == Main Dish: The Master Machine == | ||
I decided to make my most powerful computer to become a master for FlightGear. It's name is "leader" with IP 192.168.1.10, it runs on Ubuntu Lucid x64 and comes with a neat NVidia GTX260 and 5.1 sound output. This will be my: | I decided to make my most powerful computer to become a master for FlightGear. It's name is "leader" with IP 192.168.1.10, it runs on Ubuntu Lucid x64 and comes with a neat NVidia GTX260 and 5.1 sound output. This will be my: | ||
* Data sending instance (more of this later) | * Data-sending instance (more of this later) | ||
* Scenery presenter | * Scenery presenter | ||
* Joystick / Yokes / Controller input | * Joystick / Yokes / Controller input | ||
| Line 72: | Line 72: | ||
* "enable-panel" does exactly what it says: it's enabling the instrument panel. That's what we want here | * "enable-panel" does exactly what it says: it's enabling the instrument panel. That's what we want here | ||
* "disable-hud" will remove the heads up display. We have this on "leader". Here it's just not needed | * "disable-hud" will remove the heads up display. We have this on "leader". Here it's just not needed | ||
* "disable-sound" does also what it says. No need for it on the slave. | * "disable-sound" does also what it says. No need for it on the slave. You have sound on "leader", don't you? | ||
* "prop:/..." deactivates parts in the rendering chain which we don't need here. These features are running on "leader" and there they do what they should do | * "prop:/..." deactivates parts in the rendering chain which we don't need here. These features are running on "leader" and there they do what they should do | ||
== | == Dessert: Performance == | ||
I came up with the idea of using multiple (old) computers I collected during the last years because I hated the idea of having PCs dusting around without using them. As I like the idea of giving them a new mission it's sometimes somewhat tricky to gain the necessary performance depending on the hardware | I came up with the idea of using multiple (old) computers I collected during the last years because I hated the idea of having PCs dusting around without using them. As I like the idea of giving them a new mission it's sometimes somewhat tricky to gain the necessary performance depending on the hardware; so I try to get as much performance out of the old machines as possible. I don't see any needs for fancy eye candy on a PC whose job it is just to bring an instrument panel to the screen.<br /> | ||
So what can we do to gain more power? | So what can we do to gain more power? | ||
* First: turn on "View -Display Options - Show Frame Rate" to get a feeling for settings that will help overall performance, and observe if the frame rate stalls, raises or drops after defining a new setting | * First: turn on "View -Display Options - Show Frame Rate" to get a feeling for settings that will help overall performance, and observe if the frame rate stalls, raises or drops after defining a new setting | ||
* Step by step turn off all rendering options either in the main window or via command line options | * Step-by-step turn off all rendering options either in the main window or via command line options | ||
* Set in the command line "--prop:/sim/rendering/camera-group/zfar=x", where x is a small value (e.g. 1 to 100) | * Set in the command line "--prop:/sim/rendering/camera-group/zfar=x", where x is a small value (e.g. 1 to 100) | ||
* Don't provide the path to fg-scenery. Loading may take longer now and in the window you may only see water around you but this nothing to worry about | * Don't provide the path to fg-scenery. Loading may take longer now and in the window you may only see water around you but this nothing to worry about | ||
| Line 87: | Line 87: | ||
Now you have a fancy system interacting with each other. You may now proceed to configure [[Howto: Configure camera view windows|multiple views and monitors]] so so can define side views, top windows, single instruments, [[Complex Glass Cockpit Avionics|glass cockpit avionics]] and and and... | Now you have a fancy system interacting with each other. You may now proceed to configure [[Howto: Configure camera view windows|multiple views and monitors]] so so can define side views, top windows, single instruments, [[Complex Glass Cockpit Avionics|glass cockpit avionics]] and and and... | ||
== Reflux: | == Reflux: Dos, Don'ts and Despair == | ||
* Until now I was only able to use the 2D panel of the default aircraft Cessna 172 independent of what aircraft I start with. In times of 3D cockpits it seems not very easy to find fresh 2D panels. | * Until now I was only able to use the 2D panel of the default aircraft Cessna 172 independent of what aircraft I start with. In times of 3D cockpits it seems not very easy to find fresh 2D panels. | ||
<br /> | <br /> | ||