I'll take the offer, because I'm mightily confuzzzzzed...
I made the keymap with the Oolite keymapper, so it's in XML, but it doesn't work either...
keyconfig.plist problems with v1.65rc1
Moderators: winston, another_commander, Getafix
- Star Gazer
- ---- E L I T E ----
- Posts: 633
- Joined: Sat Aug 14, 2004 4:55 pm
- Location: North Norfolk, UK, (Average Agricultural, Feudal States,Tech Level 8)
Try this...
this was opened in SubEthaEdit:
this was opened in SubEthaEdit:
{
<integer>key_autodock</integer> = 68;
<integer>key_autopilot</integer> = 99;
<integer>key_cloaking_device</integer> = 48;
<integer>key_comms_log</integer> = 96;
<integer>key_contract_info</integer> = 63;
<integer>key_decrease_speed</integer> = 115;
<integer>key_docking_music</integer> = 115;
<integer>key_dump_cargo</integer> = 100;
<integer>key_ecm</integer> = 101;
<integer>key_emergency_hyperdrive</integer> = 72;
<integer>key_energy_bomb</integer> = 9;
<integer>key_fire_lasers</integer> = 97;
<integer>key_galactic_hyperspace</integer> = 103;
<integer>key_hyperspace</integer> = 104;
<integer>key_ident_system</integer> = 114;
<integer>key_increase_speed</integer> = 119;
<integer>key_inject_fuel</integer> = 105;
<integer>key_jumpdrive</integer> = 106;
<integer>key_launch_escapepod</integer> = 27;
<integer>key_launch_missile</integer> = 109;
<integer>key_map_dump</integer> = 33;
<integer>key_map_home</integer> = 302;
<integer>key_next_compass_mode</integer> = 92;
<integer>key_next_missile</integer> = 121;
<integer>key_pitch_back</integer> = 254;
<integer>key_pitch_forward</integer> = 255;
<integer>key_roll_left</integer> = 253;
<integer>key_roll_right</integer> = 252;
<integer>key_scanner_zoom</integer> = 122;
<integer>key_snapshot</integer> = 42;
<integer>key_target_missile</integer> = 116;
<integer>key_untarget_missile</integer> = 117;
}
Very funny, Scotty, now beam down my clothes...
- aegidian
- Master and Commander
- Posts: 1161
- Joined: Thu May 20, 2004 10:46 pm
- Location: London UK
- Contact:
No.Star Gazer wrote:Try this...{
<integer>key_autodock</integer> = 68;
....
You're mixing ASCII and XML plist formats - all that will happen is Oolite failing to parse it properly and dropping back to the defaults.
I've checked the documentation and there is no way to specify an integer in an ASCII plist instead these values are all treated as strings (which worked before v.165rc1, and works with the fix, but doesn't work for v1.65rc1).
- Star Gazer
- ---- E L I T E ----
- Posts: 633
- Joined: Sat Aug 14, 2004 4:55 pm
- Location: North Norfolk, UK, (Average Agricultural, Feudal States,Tech Level 8)
- Cmdr. Wombat
- Deadly
- Posts: 150
- Joined: Mon Jan 31, 2005 6:08 pm
- Location: Kentucky
- aegidian
- Master and Commander
- Posts: 1161
- Joined: Thu May 20, 2004 10:46 pm
- Location: London UK
- Contact:
A fairly simple procedure...
If you wish to convert it yourself there's a two stage process that will require either Property List Editor or the command line, and a text editor.
Stage 1 : convert the plist to xml.
Either load your keyconfig.plist into Property List Editor and immediately save it.
Or in Terminal.app's command line type plutil -convert xml1 then drag your file into terminal's window so that it's address appears after what you just typed, and press return.
Stage 2 : convert the strings to integers
Open your new xml keyconfig.plist in a texteditor, and replace every string with integer (a global search-and-replace). And save the result.
You should now have a working XML keyconfig.plist
Or you can wait for the release of v1.65 final - which has this problem licked.
Stage 1 : convert the plist to xml.
Either load your keyconfig.plist into Property List Editor and immediately save it.
Or in Terminal.app's command line type plutil -convert xml1 then drag your file into terminal's window so that it's address appears after what you just typed, and press return.
Stage 2 : convert the strings to integers
Open your new xml keyconfig.plist in a texteditor, and replace every string with integer (a global search-and-replace). And save the result.
You should now have a working XML keyconfig.plist
Or you can wait for the release of v1.65 final - which has this problem licked.
Here's a working keyconfig.plist using default controls:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<!-- File written by Oolite Keymapper by Cap'n Hack -->
<dict>
<key>key_roll_left</key>
<integer>253</integer>
<key>key_roll_right</key>
<integer>252</integer>
<key>key_pitch_forward</key>
<integer>255</integer>
<key>key_pitch_back</key>
<integer>254</integer>
<key>key_increase_speed</key>
<integer>119</integer>
<key>key_inject_fuel</key>
<integer>105</integer>
<key>key_decrease_speed</key>
<integer>115</integer>
<key>key_fire_lasers</key>
<integer>97</integer>
<key>key_ident_system</key>
<integer>114</integer>
<key>key_target_missile</key>
<integer>116</integer>
<key>key_next_missile</key>
<integer>121</integer>
<key>key_untarget_missile</key>
<integer>117</integer>
<key>key_launch_missile</key>
<integer>109</integer>
<key>key_ecm</key>
<integer>101</integer>
<key>key_launch_escapepod</key>
<integer>27</integer>
<key>key_energy_bomb</key>
<integer>9</integer>
<key>key_cloaking_device</key>
<integer>48</integer>
<key>key_galactic_hyperspace</key>
<integer>103</integer>
<key>key_hyperspace</key>
<integer>104</integer>
<key>key_jumpdrive</key>
<integer>106</integer>
<key>key_dump_cargo</key>
<integer>100</integer>
<key>key_autopilot</key>
<integer>99</integer>
<key>key_autodock</key>
<integer>68</integer>
<key>key_snapshot</key>
<integer>42</integer>
<key>key_docking_music</key>
<integer>115</integer>
<key>key_scanner_zoom</key>
<integer>122</integer>
<key>key_map_dump</key>
<integer>33</integer>
<key>key_map_home</key>
<integer>302</integer>
<key>key_contract_info</key>
<integer>63<integer>
<key>key_emergency_hyperdrive</key>
<integer>72</integer>
<key>key_comms_log</key>
<integer>96</integer>
<key>key_next_compass_mode</key>
<integer>92</integer>
</dict>
</plist>