Replacement of the basic ship set - building a dream team.

[JensAyton]

Another solution which should allow ships in a given system to produce different numbers of pods is:

Code: Select all

      <key>death_actions</key> 
      <array>    
         <dict> 
            <key>conditions</key> 
            <array> 
               <string>d100_number greaterthan 30</string> 
            </array> 
            <key>do</key> 
            <array> 
               <string>spawn: escape-capsule 3</string> 
            </array>  
         </dict> 
         <dict> 
            <key>conditions</key> 
            <array> 
               <string>d100_number greaterthan 50</string> 
            </array> 
            <key>do</key> 
            <array> 
               <string>spawn: escape-capsule 3</string> 
            </array>  
         </dict> 
         <dict> 
            <key>conditions</key> 
            <array> 
               <string>d100_number greaterthan 90</string> 
            </array> 
            <key>do</key> 
            <array> 
               <string>spawn: escape-capsule 3</string> 
            </array>  
         </dict> 
      </array>

[Commander McLane]

I am generally a little reluctant to use pseudoFixedD100_number. That is mainly, because you never know which other scripts use them at the same time. If a couple of scripts use a pseudoFixedD100_number in the same system they all would finally work with one single number only. Perhaps that wouldn't even be bad, but it just doesn't seem to be a clean solution, from a programmer's point of view.

Fortunately pseudoFixedD100_numbers don't need to be used. You can easily replace them. All you need to do is to store the initial d100_number in a variable. That's a good time to use a local_ variable. (I have used this method in Anarchies.oxp to display different mission screens, depending on whose MultiPassed ID you just bought.)

It's only a small modification to LittleBear's script:

Code: Select all

<key>death_actions</key>
	<array>
		<string>set: local_escapePod_number [d100_number]</string>
		<dict>
			<key>conditions</key>
			<array>
				<string>"local_escapePod_number greaterthan 30"</string>
			</array>
			<key>do</key>
			<array>
				<string>spawn: escape-capsule 3</string>
			</array>
		</dict>
		<dict>
			<key>conditions</key>
			<array>
				<string>"local_escapePod_number greaterthan 40"</string>
			</array>
			<key>do</key>
			<array>
				<string>spawn: escape-capsule 1</string>
			</array>
		</dict>

(repeat for >50, >60, >70, >80, >90)

		<string>reset: local_escapePod_number</string>
	</array>

[Selezen]

Hey dudes - since learning about this I've been beavering away on a bit of an idea for a slightly more details Krait, and this is the result:



I've been experimenting with some texturing ideas based on the look of some of the works around the net (and here) and this is the result. It's my first attempt at trying to model scratches and exposed bare metal.

If it passes muster as a 'dream team' candidate then I'll try and finish it up and package it...

[ramon]

Oh very nice. Welcome to the dream team I'd say.

One little thing I'd personally like to see is some work done on the cockpit area, I'm not a fan of the flat textured cockpit.

Talking of textures though, I really like what you've done. Not over the top in any way.

I've actually bought a texture pack (only £29) because I think texturing is a lot harder than modelling and, well, I want them to look as good as Griff's.

[Uncle Reno]

I agree with Ramon, it does look very nice.

[Wolfwood]

Looks good to me!

[Captain Hesperus]

Ooh, ooh! Do the Python next!

Okay, yeah. I'm a Python groupie.

Captain Hesperus

[Selezen]

One little thing I'd personally like to see is some work done on the cockpit area, I'm not a fan of the flat textured cockpit.

Cockpits are a bugger to do well. It's about as 3D as I can make it without some serious remodelling. It's recessed and has a pseudo 3D texture (which doesn't show up well on the sample).

Thanks for the feedback though. I might tweak the cockpit look a little before final release.

I had to do a bit of tweaking - my face count came in at 540, just above the 512 limit, so I've had to remove a bit of the engine detail. Doesn't detract from it any though.

Now I just need to find a computer to run Oolite on to test and place the laser and exhausts.

[Cmdr. Maegil]

One little thing I'd personally like to see is some work done on the cockpit area, I'm not a fan of the flat textured cockpit.

That's because the cockpit window blast shield is down...

[ramon]

It's recessed and has a pseudo 3D texture (which doesn't show up well on the sample).

Recessed is good enough, that's all I really meant, it just didn't look like that from the image so, my bad

[TGHC]

I hereby award Selezen with a Gold Star that he can attach to the Krait, in recognition of Texturing that is above and beyond the norm.

Absobloodylutely stunning, well done matey. Who needs itinerent CG artists when we have our own resident wizards.

Everyday in everyway, Oolite is gradually morphing into EliteIV.

[Cmdr. Maegil]

Everyday in everyway, Oolite is gradually morphing into EliteIV.

SSSssshhhhhhht! Don't say that aloud or DB may sue...

[ramon]

Does anybody know the width x hight x depth measurements of a Cargo Pod?

[Selezen]

Ooh, ooh! Do the Python next!

Hmm...I was going to do the Adder next. Mind you, the Python could be fun. Or maybe I should do the Imperial Courier. And the TOGY...

Thanks for the comments, guys.

[jonnycuba]

Very nice Mr Selezen!