Starlancer Ship Packs
-
A little while ago i released the Alliance fighter ship pack which to be fair had already been done by others but i released it anyway. Soon after, i released the Coalition fighter ship pack.
Now surs are not that difficult to do anymore with two excellent sur making utilities around by LS and Smackbolzen so doing surs isn’t an issue.
I had a little dig through the SL textures and models again and came across the Alliance 45th SQN textures which are different from those already released by others and myself and these are for the Alliance fighters only. Was thinking if these would be of interest to anyone.
-
I would be, dunno what I’d do with them, but I would like to see them. Havent played Starlancer in years. Not since my joystick gave up the ghost.
-
course, they were the flying Tigers werent they. forgotten that. nice work. are you going to release another pack with these in? plus maybe the chinese fighters?
-
Been going through these, forgot how many there were. Think i’m going to do a combined ship pack of all the Starlancer fighters, Alliance, Coalition and the 45th Tigers. That way all the models will be in one place if people want to use them. All ships will have surs and icons. Might even do some scripts so people can just drop in the ships they want to use.
Right, here’s the first two that have bugged me from day one. These models were never complete, needing the right torpedo loadouts to go with the ship models.
It goes without saying that both these ships were designed badly from the start, as technically neither can fire a torpedo without blowing themselves up, the Kamov is a prime example. Not only should it not be able to launch a torpedo, the Kamov thoughtfully has an engine pod right over the two bottom warheads so if you somehow manage to not blow yourself up during launch, chances are you haven’t even got that far as the warheads will have been cooked by the engines lol
ALLIANCE HADES BOMBER
COALITION KAMOV BOMBER
-
I remember that the Kamov had animated torpedo tubes, they came out like a big “X” and launched from that position. I think the torp tubes on the Hades came out horizontally
-
-
They are on the large side can’t argue with that. The thing with the Galahad torpedoes is that in SL, when you view the ship database in ITAC, the torps are different for the Galahad. I’ve looked through all the models and i can’t find the one that’s shown in the database, can’t even find the texture for it. There are other models listed in ITAC that have different textures to those in game and i suspect that the ITAC interface was written first and then the ship textures and munitions textures were modified prior to release. The Galahad is the predecessor to the Hades bomber anyway, so no biggie from my point of view that they have the same torp mounted.
-
So ITAC = Big fail!? LOL!
Edit : I’ve just seen that in ITAC Kamov and Galahad torps are the same. But are totaly different ingame so the ingame is better and ITAC is only a database, what is the importance of the torpedoes texture?
-
The importance of the torpedo texture is pretty obvious, so the right texture goes on the correct torpedo. As it turns out i can only find two torpedo models in SL, one for the Alliance and one for the Coalition so i guess those will have to do.
Now for something different. On the above Galahad image, there are two torpedo slots. After thinking about things for a while, i came up with the idea of offering the ship for sale without the torpedoes, instead you would buy these as a torp launcher, that way the ship would look as it should plus you could fire the torps. Here lies the problem.
What i want to happen is this, having made a torp launcher look the same as the torpedo itself, i want the launcher to destroy itself when you fire the torp, simulating the fact the torp has left the ship so it doesn’t just hang there. It’s all working apart from the fact the torp launcher is still there after i fire the torp so it looks like the torp is still mounted.
Here’s my code for the launcher,
hit_pts = 0
explosion_resistance = 0
debris_type = debris_normal
parent_impulse = 0
child_impulse = 0
volume = 0
mass = 10
hp_gun_type = hp_gun_special_4
damage_per_fire = 100
power_usage = 0
refire_delay = 0
muzzle_velocity = 10
toughness = 0
projectile_archetype = galahad_torpedo_ammo
dry_fire_sound = fire_dry
separation_explosion = sever_debris
auto_turret = false
turn_rate = 0
lootable = false
LODranges = 0, 5000What i was hoping for was the damage_per_fire section to work, but it doesn’t seem to be doing what it should. This is why i set the hitpoints for the launcher to 0 thinking that the launcher will damage itself on firing, thereby destroying itself but its not doing it.
Anyone have any suggestions?
-
i’ve never tested damage_per_fire, but if i remember correctly explosion_resistance is actually a damage multiplier. so setting it to 0 is doing the opposite of what you want to achieve, making it indestructible. not sure about this, but give it a try.
-
Thx Rimshot. Tried that but still no joy. I set the numbers like this after your post,
hit_pts = 1
explosion_resistance = 1
debris_type = debris_normal
parent_impulse = 20
child_impulse = 80
volume = 0
mass = 10
hp_gun_type = hp_gun_special_4
damage_per_fire = 100They still sit there after i fire the things when they should be blowing up lol
-
found this post by adoxa: http://the-starport.net/freelancer/forum/viewtopic.php?post_id=37810#forumpost37810
-
sigh, thanks again for that, seems it’s disabled in the code somewhere. GRRRRRR :-x
I was expecting that line to do damage to the weapon as well, but seems that isn’t happening. Nvm, have to wait for adoxa then. It’s a shame as if it did work, you could have single shot weapons like i’m trying to do here.
-
Attached is the plugin for working damage_per_fire. As usual, testing has been minimal (I didn’t try MP, but it should work). If it works okay, I’ll put it on my site (along with the source). Install to dacom.ini (SP) or dacomsrv.ini (MP); requires and assumes 1.1.
-
adoxa wrote:
Attached is the plugin for working damage_per_fire. As usual, testing has been minimal (I didn’t try MP, but it should work). If it works okay, I’ll put it on my site (along with the source). Install to dacom.ini (SP) or dacomsrv.ini (MP); requires and assumes 1.1.been wanting this for years. what sort of scale do you use? is it percentage based (0.01) or individual hit_pts based (1026)?