Oolite Bulletins

CmdrLUke wrote:

It is quite a reasonable assumption that a ball turret could be a laser turret with a "ball mounting" that can swivel, yes?

onno256 wrote:

Since 1.77 came out, I've started a new savegame, though it is tougher, it is do-able

Eric Walch wrote:

You do need the new subentity definitions though:

Code: Select all

			{
				"subentity_key" = "bweed-falcon-turret";
				type = "ball_turret";
				position = (0.0, 6.5, -9.5);
				orientation = (0.25, 0.75, 0, 0);
				"weapon_range" = 7500;
			},
			{
				"subentity_key" = "bweed-falcon-turret";
				type = "ball_turret";
				position = (0.0, -6, -9.5);
				orientation = (0.25, -0.75, 0, 0);
				"weapon_range" = 7500;
			},

	<key>subentities</key>
		<array>
			<string>bweed-falcon-player_turret 0.0 6.5 -9.5 0.25 0.75 0.0 0</string>
			<string>bweed-falcon-player_turret 0.0 -6 -9.5 0.25 -0.75 0.0 0</string>
		</array>

<snip>

	<key>bweed-falcon-player_turret</key>
	<dict>
		<key>ai_type</key>
		<string>nullAI.plist</string>
		<key>energy_recharge_rate</key>
		<real>5</real>
		<key>laser_color</key>
		<string>magentaColor</string>
		<key>max_energy</key>
		<real>200</real>
		<key>model</key>
		<string>bweed-falcon-turret.dat</string>
		<key>name</key>
		<string>bweed-falcon-turret</string>
		<key>roles</key>
		<string>bweed-falcon-turret</string>
		<key>setup_actions</key>
		<array>
			<string>initialiseTurret</string>
		</array>
		<key>smooth</key>
		<true/>
		<key>thrust</key>
		<real>1</real>
		<key>weapon_energy</key>
		<real>10</real>
		<key>weapon_range</key>
		<real>7500</real>
		<key>fire_rate</key>
		<real>0.25</real>
	</dict>

another_commander wrote:

One thing to remember (and I did not make it clear earlier, sorry about that) is that the distance checked for the turrets to start firing is not the same as the one displayed on the distance indicator on the HUD. The distance indicator shows distance to the bounding box edges where collision detection occurs, not distance to the center of the entity. This can be misleading when using just the HUD to judge distances. I did another test and documented it with screenshots, which I hereby present.
<snip>
I hope the above explains how and why it works as expected and why the distances can be sometimes misjudged. I have not tested what happens if the turret weapon range is set to the theoretical 7500m maximum but I believe Eric covered this already in his earlier post. Still, if there are unclarified points, feel free to ask.

mandoman wrote:

onno256 wrote:

Since 1.77 came out, I've started a new savegame, though it is tougher, it is do-able

This sounded like a good idea, so I'm trying it. It has to be one of the hardest things for a person who has played the game, and become proficient with all it's weapons, and defenses. However, after three trips, from Lave to Leesti, Leesti to Diso, and back to Leesti, I have only been assaulted once. I thought I was dead meat, but GalCops actually came to my rescue. Man, that Cobra 3 is slow without injectors, and such.

Diziet Sma wrote:

Just to be clear, since the Falcon shipdata.plist is in the old style, with the turret and subentities defined separately, what changes do I need to make where? This is the relevant sections as I have them currently.. and would it pay for me to convert the plist to the new style before changing things?

Code: Select all

	<key>subentities</key>
		<array>
			<string>bweed-falcon-player_turret 0.0 6.5 -9.5 0.25 0.75 0.0 0</string>
			<string>bweed-falcon-player_turret 0.0 -6 -9.5 0.25 -0.75 0.0 0</string>
		</array>

<snip>

			<dict>
				<key>subentity_key</key>
				<string>bweed-falcon-turret</string>
				<key>type</key>
				<string>ball_turret</string>
				<key>position</key>
				<array>
					<string>0.0</string>
					<string>6.5</string>
					<string>-9.5</string>
				</array>
				<key>orientation</key>
				<array>
					<string>0.25</string>
					<string>0.75</string>
					<string>0</string>
					<string>0</string>
				</array>
			</dict>
			<dict>
				<key>subentity_key</key>
				<string>bweed-falcon-turret</string>
				<key>type</key>
				<string>ball_turret</string>
				<key>position</key>
				<array>
					<string>0.0</string>
					<string>-6</string>
					<string>-9.5</string>
				</array>
				<key>orientation</key>
				<array>
					<string>0.25</string>
					<string>-0.75</string>
					<string>0</string>
					<string>0</string>
				</array>
			</dict>

Eric Walch wrote:

I don't know why everybody keeps using the XML format as the old text format is much more readable when using text editors for plists.

Alextended wrote:

Still having stick drifting issues, will editable deadzones every be added in the options?

Alextended wrote:

Still having stick drifting issues, will editable deadzones every be added in the options?

Alextended wrote:

Still having stick drifting issues, will editable deadzones every be added in the options?

another_commander wrote:

once the current feature freeze has been lifted.

Diziet Sma wrote:

another_commander wrote:

once the current feature freeze has been lifted.

Speaking of which, is there a rough time-frame for when that might happen, yet?