ACS and MilHUD, updated for 1.74

[Cmdr Wyvern]

Auto-Chaff: No new features or feature changes, works exactly as before. This fixes the method deprecation errors.
Get it here: http://www.box.net/shared/q60ghhz6lq

MilHUD-v3: Minor fixes, and one feature added. New feature is a precision mode indicator, useful for joystick pilots. Look at the compass/YPR cluster.
Get it here: http://www.box.net/shared/tob20xujtz

[JazHaz]

Neither of these two OXPs have a readme, Wyvern?!

[Cmdr Wyvern]

ReadMe:

Except for the one added dial to MilHUD, the functions are exactly the same as the old ones; just no errors under 1.74.
Delete the old ones, drop in the updated ones, carry on.

[caracal]

MilHUD-v3: Minor fixes, and one feature added. New feature is a precision mode indicator, useful for joystick pilots. Look at the compass/YPR cluster.

Oh thankyou thankyou thankyou! I asked whether this could be added back in 2008 when I first started playing 1.65. Never got an answer, but now have the feature! Is that selector (drawStickSensitivityIndicator) new to 1.74?

At any rate, thanks for adding it. And thanks for the OXP; I think the MilSpec HUD is superior, and if a new ship tries to replace it, I always put it back double-quick. Maintenance crews from Cemave to Sori know better than to mess with my HUD!

[Captain Patrick]

While MilHUD-v3 works fine for me under Oolite v1.74, MilHUD-v3.1 that I got from the above link seemingly does not load at all, and I'm presented with Oolite's default HUD. Latest.log includes:


[log.header]: Opening log for Oolite version 1.74 (PPC-32 test release) under Mac OS X Version 10.4.11 (Build 8S165) at 2010-06-21 23:02:26 -0700.
Machine type: PowerBook6,8, 1280 MiB memory, 1 x PowerPC G4 (7450) @ 1500 MHz.
Oolite options: procedural planet textures, docking clearance, wormhole scanner, target incoming missiles, spoken messages, JavaScript console support, Debug plug-in support, OXP verifier, localization tools, debug GraphViz support.
<snip>
[plist.parse.failed]: Failed to parse /Applications/Games f/Oolite f/Oolite (v1.74)/Oolite/AddOns/MilHUD-v3.1.oxp/Config/hud.plist as a property list.
XML parser error:
Unknown character '.' (0x2e) in <integer> on line 185
Old-style plist parser error:
Malformed data byte group at line 1; invalid hex
<snip>


Is this enough to show what's the matter?

[Commander McLane]

Unknown character '.' (0x2e) in <integer> on line 185

This is your information. Open the file hud.plist inside the Config folder inside Milhud.oxp (if you're on Windoze, do not use Notepad!) and browse to line 185 of that text file. There you will find a character which obviously cannot be parsed. My guess is a special character which would need to be masked.

[JazHaz]

Unknown character '.' (0x2e) in <integer> on line 185

This is your information. Open the file hud.plist inside the Config folder inside Milhud.oxp (if you're on Windoze, do not use Notepad!) and browse to line 185 of that text file. There you will find a character which obviously cannot be parsed. My guess is a special character which would need to be masked.

Here is the code (line 185 is the third line below):

Code: Select all

		<dict><!--stick sensitivity indicator-->
			<key>alpha</key>
			<integer>1.0</integer>

It's not a special character, more a syntax error. 1.0 is not an integer, it probably should be 1

[Captain Patrick]

It worked! Thanks!

[caracal]

Here is the code (line 185 is the third line below):

Code: Select all

		<dict><!--stick sensitivity indicator-->
			<key>alpha</key>
			<integer>1.0</integer>

It's not a special character, more a syntax error. 1.0 is not an integer, it probably should be 1

I should note, in case it matters to anyone, that the 1.0 works fine with trunk.

[Cmdr Wyvern]

Now that's interesting.

MilHUD v3.1 worked fine when tested on released 1.74 on XP, and gave no errors.

Not having access to a Mac, I couldn't test it on one. Interesting that the Mac port of Oolite choked on MilHUD 3.1 when the w32 and Linux ports are fine with it.
Computers...more temperamental than women, I swear!

[Svengali]

*sigh* but alpha is not an integer .-)

You can always take a look at the schemata - that gives you more infos:
"alpha" = $floatZeroToTwo;

Probably Oolite treat a 1 as 1.0 then...

[Cmdr Wyvern]

*sigh* but alpha is not an integer .-)

You're right.
On a closer look, it dawned on me that the troubled key should be <real> and not <integer>.
My bad.

Change it, and you should be good to go. I'll put up a fixed package later on today.

Note to self: Before futzing about with plists and scripts, drink some coffee.

EDIT: Fix applied, and package re-uploaded. Same link above.
Mac guys, please let me know if this works sans errors. TIA.

[Captain Patrick]

I downloaded and tried the "new v3.1", and the MilHUD shows up fine now.

Except I can't see where the "Stick Sensitivity Indicator" is supposed to be working. This sounds like a useful feature - can it be enabled & observed via the keyboard or mouse (that I have), or only with an appropriate joystick (that I don't have - yet)?

[Cmdr Wyvern]

I downloaded and tried the "new v3.1", and the MilHUD shows up fine now.

That's great news! No log errors then?

Except I can't see where the "Stick Sensitivity Indicator" is supposed to be working. This sounds like a useful feature - can it be enabled & observed via the keyboard or mouse (that I have), or only with an appropriate joystick (that I don't have - yet)?

It would be a small circular indicator situated just above the pitch bar and to the left of the yaw bar.
If you use a stick and precision mode, it's indeed useful. I'll assume that a stick is required. Now for some bad news: I've heard that Macs don't play well with joysticks, and force you to jump through some flaming hoops in order to use one. I can't say if that's true or not, but as I love my X52 and won't launch without it, I'de say that's suckage of a black hole order of magnitude (if true).

[JensAyton]

Here is the code (line 185 is the third line below):

Code: Select all

		<dict><!--stick sensitivity indicator-->
			<key>alpha</key>
			<integer>1.0</integer>

It's not a special character, more a syntax error. 1.0 is not an integer, it probably should be 1

I should note, in case it matters to anyone, that the 1.0 works fine with trunk.

It depends on the platform, not the Oolite version.

*sigh* but alpha is not an integer .-)

You can always take a look at the schemata - that gives you more infos:
"alpha" = $floatZeroToTwo;

Probably Oolite treat a 1 as 1.0 then...

Doesn’t matter. <integer> and <real> both become NSNumber internally (and, in fact, it would be OK to use <string> too).

I've heard that Macs don't play well with joysticks, and force you to jump through some flaming hoops in order to use one. I can't say if that's true or not

It is a vile calumny. Oolite for Mac OS X does not support joysticks.