[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4280: ob_start(): output handler 'ob_gzhandler' conflicts with 'zlib output compression'
Oolite Bulletins • Imperial Courier V2.0
Page 1 of 7

Imperial Courier V2.0

Posted: Wed May 02, 2007 9:16 am
by Selezen
At last, you may cry...

I've been procrastinating too long about this, so here it is. I haven't yet had a chance to reposition the views and the laser origin (far too busy at work and home), so would some kind chap have a look at this and let me know the changes to make please?

Download it here

Note that this is BETA software, tested on my own machine but nowhere else. Once it's tested and done I'll upload the final version to the Wiki.

Enjoy!

Posted: Wed May 02, 2007 11:38 am
by Star Gazer
Damn!! I'm at work!! I'm going to have to try and be patient until 17:45... ...arrrrggghhhh...!!! :evil:

Posted: Wed May 02, 2007 1:44 pm
by LittleBear
Not working today, so took one out for a spin.

The laser settings for the Forward, Aft Starboard & port are fine. The external view laser is a bit too low (its correct for the left / right position, but is coming up below the nose).

One tiny suggestion: Maybe name the ship in Shipyard.plist icour-player as this means those of us who already own the old version get a straight swap for the new one rather than having to wait for the new one to come up for sale in the Shipyard.

Like the rotating engines! 8)

Posted: Thu May 03, 2007 9:28 am
by Selezen
Either that or just modify your save game and change the name of the ship there...

;-)

Posted: Thu May 03, 2007 3:32 pm
by pescenaufrago
Woha!
Eventually a new courier!
I've downloaded the file, Im going to test it tonight !
Bye,
M

Posted: Sun May 06, 2007 6:12 pm
by Captain Hesperus
Here's the view out the starboard window.
Image
Now, I don't claim to be an expert, but this looks a little low down. I'd have expected the nacelles to not be visible through the side views due to the angle at which the pylons are in relation to the cockpit views.

And as LB said, the lasers are spot on! I'm plugging Kraits and Sidewinders at 20+km with great accuracy.
Image
And as previouly stated, the external view shows the laser coming out several metres below the cockpit. Meh, no-one's perfect, she's still a great ship!

One anomaly though, I locked onto a Mussurana and when I damaged it and it WFI'd off the scanners, my STE still had a lock even though it was 28km away! Weird....

Captain Hesperus

Posted: Sun May 06, 2007 8:21 pm
by Commander McLane
Captain Hesperus wrote:One anomaly though, I locked onto a Mussurana and when I damaged it and it WFI'd off the scanners, my STE still had a lock even though it was 28km away! Weird....

Captain Hesperus
I've experienced that before, unfortunately I don't recall the circumstances. But IIRC it didn't work with all ships, only some OXP ships.

Posted: Sun May 06, 2007 9:39 pm
by Commander McLane
@ Selezen: The laser positions were too low even in the original version. I changed them for my commander.

The new Imperial Courier is almost three times as big as its predecessor, so my values don't work. I suggest the following view positions and weapon positions. One remark: from the design of the ship it's not too clear where the port and starboard weapon mountings are located, so this is really just a suggestion. I'm happy to get feedback.

Code: Select all

		<key>view_position_aft</key>
		<string>0.0 20.0 -31.0</string>
		<key>view_position_forward</key>
		<string>0.0 13.6 54.11</string>
		<key>view_position_port</key>
		<string>-13.74 15.0 17.6</string>
		<key>view_position_starboard</key>
		<string>13.74 15.0 17.6</string>
		<key>weapon_position_aft</key>
		<string>0.0 8.17 -20</string>
		<key>weapon_position_forward</key>
		<string>0.0 9.4 60.0</string>
		<key>weapon_position_port</key>
		<string>-12.0 9.7 18.0</string>
		<key>weapon_position_starboard</key>
		<string>12.0 9.7 18.0</string>
This part of code is meant for the player version. However the weapon positions should also be copied to the NPC.

Personally I'm not pleased with the external views (there is also the miscounting of having number 3 two times). So I suggest these, which have also the up and down view:

Code: Select all

		<key>custom_views</key>
		<array>
			<dict>
				<key>view_description</key>
				<string>External View 1</string>
				<key>view_position</key>
				<string>0.0 30.0 -200.0</string>
				<key>view_orientation</key>
				<string>1.0 0.0 0.0 0.0</string>
				<key>weapon_facing</key>
				<string>FORWARD</string>
			</dict>
			<dict>
				<key>view_description</key>
				<string>External View 2</string>
				<key>view_position</key>
				<string>141.42 30.0 -141.42</string>
				<key>view_orientation</key>
				<string>0.9239 0.0 0.3827 0.0</string>
				<key>weapon_facing</key>
				<string>FORWARD</string>
			</dict>
			<dict>
				<key>view_description</key>
				<string>External View 3</string>
				<key>view_position</key>
				<string>200.0 30.0 0.0</string>
				<key>view_orientation</key>
				<string>0.7071 0.0 0.7071 0.0</string>
				<key>weapon_facing</key>
				<string>FORWARD</string>
			</dict>
			<dict>
				<key>view_description</key>
				<string>External View 4</string>
				<key>view_position</key>
				<string>141.42 30.0 141.42</string>
				<key>view_orientation</key>
				<string>0.3827 0.0 0.9239 0.0</string>
				<key>weapon_facing</key>
				<string>FORWARD</string>
			</dict>
			<dict>
				<key>view_description</key>
				<string>External View 5</string>
				<key>view_position</key>
				<string>0.0 30.0 200.0</string>
				<key>view_orientation</key>
				<string>0.0 0.0 1.0 0.0</string>
				<key>weapon_facing</key>
				<string>FORWARD</string>
			</dict>
			<dict>
				<key>view_description</key>
				<string>External View 6</string>
				<key>view_position</key>
				<string>-141.42 30.0 141.42</string>
				<key>view_orientation</key>
				<string>0.3827 0.0 -0.9239 0.0</string>
				<key>weapon_facing</key>
				<string>FORWARD</string>
			</dict>
			<dict>
				<key>view_description</key>
				<string>External View 7</string>
				<key>view_position</key>
				<string>-200.0 30.0 0.0</string>
				<key>view_orientation</key>
				<string>0.7071 0.0 -0.7071 0.0</string>
				<key>weapon_facing</key>
				<string>FORWARD</string>
			</dict>
			<dict>
				<key>view_description</key>
				<string>External View 8</string>
				<key>view_position</key>
				<string>-141.42 30.0 -141.42</string>
				<key>view_orientation</key>
				<string>0.9239 0.0 -0.3827 0.0</string>
				<key>weapon_facing</key>
				<string>FORWARD</string>
			</dict>
			<dict>
				<key>view_description</key>
				<string>Down View</string>
				<key>view_position</key>
				<string>0.0 210.0 0.0</string>
				<key>view_orientation</key>
				<string>-0.7071 0.7071 0.0 0.0</string>
				<key>weapon_facing</key>
				<string>FORWARD</string>
			</dict>
			<dict>
				<key>view_description</key>
				<string>Up View</string>
				<key>view_position</key>
				<string>0.0 -210.0 0.0</string>
				<key>view_orientation</key>
				<string>0.0 0.0 0.7071 0.7071</string>
				<key>weapon_facing</key>
				<string>FORWARD</string>
			</dict>
		</array>
Finally two questions: Why doesn't the NPC version have a scoop? And what about fuel injectors? I think a ship like this as a pirate definitively needs them.

Posted: Sun May 06, 2007 10:23 pm
by JensAyton
This might be a good time to point out something I wasn’t aware of until I noticed it in the code a few weeks ago: fuel scoops and injectors can be set as a probability (in the range 0 to 1, e.g. <real>0.5</real> for 50% probability) instead of <true/> or <false/>. This applies to: has_ecm, has_scoop, has_escape_pod, has_energy_bomb, has_fuel_injection, has_cloaking_device, has_military_jammer, has_shield_booster, has_shield_enhancer, unpiloted and fragment_chance (a new value in 1.69, specifying the chances of wreckage chunks being generated -- or rather, the chance of them not being supressed -- with a default of 0.9).

Posted: Sun May 06, 2007 10:26 pm
by Commander McLane
Well, that's all accurately explained in the wiki (except the new stuff, of course). See the document on shipdata.plist.

Posted: Sun May 06, 2007 10:50 pm
by JensAyton
I’d say that it is not, in fact, accurately explained in the wiki, since it appears to only be mentioned regarding has_ecm. Besides, people don’t look at the documentation. This is a well known fact. :-)

Posted: Mon May 07, 2007 9:56 am
by Uncle Reno
Ahruman wrote:has_military_jammer
What's that?

Posted: Mon May 07, 2007 11:23 am
by LittleBear
Think it jams the Cloak. (IE they can still see you cloaked!). If you look in the native equipment.plist there are a few items of equipment set at tech level 99. Guess they were intended for a mission or somthing that was never implemented. I ought to have used them in Assassins, but I didn't know about them when I wrote it, so I disabled the players cloak with script when a ship with a cloak-jammer is present!

If you set an OXP station's tech-level to 99 (eg a edit the shipdata for the Black Monk Monastary to set it to equivilant_tech_level 99 and then dock at one), then the items come up for sale and you can buy them. I don't know though if the code to make them do anything is part of Oolite though.

Posted: Mon May 07, 2007 3:28 pm
by JensAyton
*pokes code* The military jammer is a complement to the cloak, not a countermeasure. It makes a ship invisible to scanners, except to ships with a military scanner filter (who see it as a purple/orange flashing thing). has_military_scanner_filter seems to have fallen out of that list, it’s also a “fuzzy boolean”. The corresponding player equipment key is EQ_MILITARY_SCANNER_FILTER (and for has_military_jammer, EQ_MILITARY_JAMMER).

Neither are available for normal purchase or through any built-in missions. No built-in ships use them.

Posted: Mon May 07, 2007 4:37 pm
by LittleBear
Just out of interest, if in shipdata an NPC was set to:-

Code: Select all

<key>has_military_scanner_filter</key>
<real>1.0</real>
Would that mean the ship would see the player (or for that matter a non-player entry cloaked ship) even if the player / non-player ship was cloaked?