|
|
| Line 1: |
Line 1: |
| | Adjusting the 'Adjust View Distance' |
|
| |
|
| [['''Beginner's Shortcut to setting up FlightGear communication: FGcom''']]
| | I have a little different taste than others especially when it comes to the Point of View (POV) of the cockpit. Where most pilots like to fly with a POV of 70- 80, I like to use 120. However, there is one problem with this, using a POV @ 120 causes the cockpit to look very very far away, making it almost impossible to see the instruments, unless of course you zoom it back up to a POV of 80. |
| | But you can fly using a POV @ 120 with no problem by adjusting the 'Adjust View Distance' from the 'View' menu. Simply click the dial on the 'Forward/backward' and stop where you like. For some planes, this works very well, for others, it's a disaster. |
|
| |
|
| These instructions are meant for Windows XP sp2. If you are like me, then you probably let Flightgear install into your local drive and into program files by default.
| | The issue: The Adjust View Distance dial is over-sensitive, if I want a view distance of '0', i would click on '0' but because it's so sensitive, I always over-shoot the '0' mark and always hit '1.0m' or '-0.9m'. The difference in view is dramatic and can be a major flying issue. |
|
| |
|
| 1. Download fgcom from this link: http://emmerich-j.de/FGFS
| | The solution: The problem is that the dial has a minimum of (-100) to a maximum of (100). The range of it is too large. We need to change the range to a smaller workable range, a good minimum and maximum is (-5m) to (5m). You could change it to (-1m) to (1m) if you wanted to. Where to change these variables? Go to Flightgear/data/GUI/dialog/pilot_offset. In the minimum and maximum field type in the new numbers, (-5m) and (5m) for Left and right, Up and Down, and Forward and Backwards. Save and quit. If you want the Adjust View Distance even more specific, decrease the range, so a good range would be (-1m) to (1m). |
|
| |
|
| 2. Save the file into your Flightgear folder in program files. Extract the files into the same Flightgear Folder.
| | So, if the cockpit is too close or too far, but you don't want to change the POV, using the adjust view distance is a good way to solve the problem. Just make sure that the Adjust View Distance range is calibrated to your likings. I use (-1m) to (1m) to get the distance just right. |
|
| |
|
| 3. Now, the tricky part: Open a Command window by going to [Start] then click [Run]. Type 'cmd' and press ok.
| | If you have any questions feel free to contact me via email. |
|
| |
|
| A black command window will appear and if everything is by default should say something like (Zexe is my username):
| | -Zexe |
|
| |
| C:\Documents and Settings\Zexe>
| |
| | |
| 4. We need to change the path. So type (by the way, 'cd' equals change directory) :
| |
| | |
| C:\Documents and Settings\Zexe>cd c:\program files\flightgear
| |
| | |
| 5. Press [Enter]
| |
| | |
| 6. Now it should read:
| |
| | |
| C:\Program Files\Flightgear>
| |
| | |
| 7. For the finale, type:
| |
| | |
| C:\Program Files\Flightgear>fgcom -sfgcom.flightgear.org.uk
| |
| | |
| 8. Press [Enter]
| |
| and fgcom will start. Keep the black window open.
| |
| | |
| 9. You must now configure the settings from Flightgear. So, open Flightgear the application and please refer to
| |
| http://wiki.flightgear.org/index.php/FGCOM . Look at 6) Input/Output, and basically copy what is there.
| |
| | |
| 10. By the way, [Space] is the default key to speak through.
| |
| | |
| 11. Once all is swell, close the Advanced box and make sure the [Show command line] box shows what you edited, then click run. If you are lucky, you will hear some people on FGcom.
| |
| | |
| ***Some planes already use the [Space] function for other things***You must configure your keybindings if you want to use Fgcom and the plane together.***
| |
| | |
| | |
| | |
| | |
| | |
| | |
| Configuring keyboard binding for Fgcom [Spacebar]
| |
| | |
| Backup your files before editing them.
| |
| These instructions are meant for Windows XP sp2. My Flightgear folder is in C:\program files.
| |
| | |
| Reason to change keybinding [Space] to a different key: Some planes already have a default function using the [Space] bar. Example planes would be the Dave's hangar planes and the hovercraft Bluebird, Pressing [Space] in these planes causes
| |
| other functions to occur and neutralizes the Fgcom function. So it is imperative to change the keybinding if you would like to utilize Fgcom on these planes.
| |
| | |
| How to change the keybindings: Go to Program files and open the Flightgear folder. Then open the Data folder. Continue by opening keyboard.xml. Use Wordpad as your editing application.
| |
| c:\program files\flightgear\data\keyboard.xml
| |
| | |
| | |
| Background information: Most of the information can be found already on wiki flightgear. But this is just to reiterate how the keyboard configuration works.
| |
| | |
| <key n="43">
| |
| <name>+</name>
| |
| | |
| 43 is tied to [ + ]. They are bonded to each other. They cannot be seperated. If you input <key n="44"> with <name>+</name>, this key configuration will fail. Rule of thumb, when copying and pasting, be sure to copy and paste the number and the symbol together as a couple.
| |
| | |
| Press Ctrl + F to open the Find box. Type 'space' and locate the keybinding for 'Push to Talk'. Now you know where the keybinding is to talk. We must find a different and hopefully useless keybinding to substitute. Since I hate the Warp function in Flightgear, we'll use this. So search for Warp:
| |
| | |
| <key n="87">
| |
| <name>W</name>
| |
| <desc>Decrease warp</desc>
| |
| <binding>
| |
| <command>property-adjust</command>
| |
| <property>/sim/time/warp</property>
| |
| <step type="int">-60</step>
| |
| </binding>
| |
| </key>
| |
| | |
| Copy : - <key n="87"> <name>W</name>
| |
| | |
| Paste over- <key n="43"> ***Note***This number 43 responds to a different key, So please ignore it.
| |
| <name>Space</name>
| |
| <desc>PTT - Push To Talk (via VoIP)</desc>
| |
| <binding>
| |
| <command>nasal</command>
| |
| <script>space(1, modifiers.getValue())</script>
| |
| </binding>
| |
| <mod-up>
| |
| <binding>
| |
| <command>nasal</command>
| |
| <script>space(0, modifiers.getValue())</script>
| |
| </binding>
| |
| </mod-up>
| |
| <mod-shift>
| |
| <binding>
| |
| <command>nasal</command>
| |
| <script>space(1, modifiers.getValue())</script>
| |
| </binding>
| |
| <mod-up>
| |
| <binding>
| |
| <command>nasal</command>
| |
| <script>space(0, modifiers.getValue())</script>
| |
| </binding>
| |
| </mod-up>
| |
| </mod-shift>
| |
| </key>
| |
| | |
| Result should look like:
| |
| | |
| <key n="87">
| |
| <name>W</name>
| |
| <desc>PTT - Push To Talk (via VoIP)</desc>
| |
| <binding>
| |
| <command>nasal</command>
| |
| <script>space(1, modifiers.getValue())</script>
| |
| </binding>
| |
| <mod-up>
| |
| <binding>
| |
| <command>nasal</command>
| |
| <script>space(0, modifiers.getValue())</script>
| |
| </binding>
| |
| </mod-up>
| |
| <mod-shift>
| |
| <binding>
| |
| <command>nasal</command>
| |
| <script>space(1, modifiers.getValue())</script>
| |
| </binding>
| |
| <mod-up>
| |
| <binding>
| |
| <command>nasal</command>
| |
| <script>space(0, modifiers.getValue())</script>
| |
| </binding>
| |
| </mod-up>
| |
| </mod-shift>
| |
| </key>
| |
| | |
| Go back to the original <key n="87">
| |
| <name>W</name>
| |
| Change the number to something over 350 or delete the function:
| |
| | |
| <key n="87">
| |
| <name>W</name>
| |
| <desc>Decrease warp</desc>
| |
| <binding>
| |
| <command>property-adjust</command>
| |
| <property>/sim/time/warp</property>
| |
| <step type="int">-60</step>
| |
| </binding>
| |
| </key>
| |
| | |
| Save file and quit and test Flightgear Fgcom with the new configured key.
| |