Some Ship Setup Questions
-
the camera offset is relevant for the problem you have.
to the ship handling. how the parameters work exactly is not entirely cleared, startrader however managed to write a ship handling tutorial that works in almost every aspect on almost any ship.
-
Thanks for the replies folks!!
@ Thaddeus: I did have a recollection of those cameralines, but didn’t see them in my file. Stupid me: I broke the ShipArch.ini into separate xml-files, and the one where I was looking only contains non-player ships. So, none of them had these lines. Should have rememberd that :oops: Thanks for your code!! My CSV is complete now
@ Nort: Now the camera values are configured, it works fine.
@ Gisteron (& StarTrader): thanks!!
-
You’re very welcome, MH.
I did not do much work on the strafe_force and nudge_force values though.
One more thing to be aware of is the problem of collision rebounds - when a ship is hit by another one.
This reaction is affected by the inertia values in the .sur file as well as the drag and inertia in the shiparch.ini file.
In small ships it is not a real problem - but in big ships it can be a spinning nightmare!
-
StarTrader wrote:
In small ships it is not a real problem - but in big ships it can be a spinning nightmare!
:lol: I guess that is something I have to grow into.
Btw I when you give satellite (child archetypes to station) a spin value, and then in-game hit them with your playership, they sometimes tumble (fall over, that is). Kinda weird. I guess this is based on the same / a similar issue?
Too bad we can’t make a-game-within-the-game out of it: earn reputation by knocking straight the towers on base such-and-such.
Your tutorial is really straightforward, ST! Last time I delved into this was when Argh relased his toolkit. He did great things, but imho he had rather radical ideas about ship handling and how it should all be very different, while I wanted to stay as close to ‘vanilla FL’ as possible.
-
New Question!
These oddly named hardpoints, like HP_Turret_B2_01, HP_Turret_B3_01, HP_Turret_B3_02 etc. in the Bretonia gunboat, are they a different category than normally named hardpoints (like HP_Turret_01) in fighters and freighters? Are these hardpoints unfit for normal guns?
Or is it just a nickname that could be practically any string? Meaning I could just set them up like every other weapon hp.
I’m inclined to think it’s the second option; just want to be sure.
-
Second, they are just unique faction warship hardpoint naming that wasn’t taken further.
Look in the loadouts_special.ini file to confirm.
Of course those hardpoints must exist in the model .cmp
-
StarTrader wrote:
Second, they are just unique faction warship hardpoint naming that wasn’t taken further.Look in the loadouts_special.ini file to confirm.
Of course those hardpoints must exist in the model .cmp
Of course. But those existing HPs can be setup as any weapon HP, which is fine.
Thanks for the reply!
-
A shield question:
Does a shield work in a certain sphere around its HP? Or does it simply work for the entire ship it is attached too?
-
Yes, the shield_link = line specifies which shield bubble the ship will use.
I copied an existing one and resized it for my big ships, it works well.
I am not sure how the game does it but the entire ship is still covered even if the shield is not large enough to cover it.
I have put multiple shield hardpoints in very big models, trying to keep the ship covered in any case.
-
Thanks folks, very informative!
StarTrader wrote:
I have put multiple shield hardpoints in very big models, trying to keep the ship covered in any case.
Yeah I noticed people doin that years ago already… But if I understand it properly this isn’t really necessary. Unless one or more shields are being destroyed.
-
Moonhead wrote:
These oddly named hardpoints, like HP_Turret_B2_01, HP_Turret_B3_01, HP_Turret_B3_02 etc.[…]These HPs are named to fit the size if the turret mounts on the model, e.g. a turret using the br_turret03.cmp is meant to fit onto the HpTurret_B3_01. Other turret models might look too big or small. But is has no effect on the HP itself.
-
Quarks wrote:
Moonhead wrote:
These oddly named hardpoints, like HP_Turret_B2_01, HP_Turret_B3_01, HP_Turret_B3_02 etc.[…]These HPs are named to fit the size if the turret mounts on the model, e.g. a turret using the br_turret03.cmp is meant to fit onto the HpTurret_B3_01. Other turret models might look too big or small. But is has no effect on the HP itself.
Hmm… That might imply it would be best to make it a separate class… I want to make all guns buyable, but was planning to get rid of the level restrictions anyway, in order to give the cap ship guns a separate class. Maybe I should reserve more than one class for the cap ship guns.
-
I never studied the cap ship guns before. Now I did, I noticed they’re a bit of a mess… The model names I mean - they do not correspond very well to the archetype names in the equipment files.
Anyway, what I wanna do is, to get rid of the level-based weapon classes, and instead design a system more or less like:
hp_gun_special_1 = fighters, freighters (so, the vanilla playable ships)
hp_gun_special_2 = the largest fighters (and maybe the largest freighters too)
hp_gun_special_3 = armored transport, repair ships, lifters etc.
hp_gun_special_4 = trains, transports
hp_gun_special_5 = gunboats, destroyers
hp_gun_special_6 = cruisers and cap ships
And four more classes left for special cases. Of couse these could vary per ship, some ships being hybrids etc.
Of course, I can do whatever I want, but does the above outline make any sense? Or would it be more sensible to split the cap ship classes (or any other category) into more classes?
-
Yes this is fine.
I did a similar thing myself, but using 2 classes for each ship type (i.e. fighter can take class 1 and class 2), but your idea is better I think - then it makes sense to spread the weapon power and price within each class.
Make each more powerful weapon much more expensive than the lower one.
-
StarTrader wrote:
Yes this is fine.I did a similar thing myself, but using 2 classes for each ship type (i.e. fighter can take class 1 and class 2), but your idea is better I think - then it makes sense to spread the weapon power and price within each class.
Make each more powerful weapon much more expensive than the lower one.
Thanks for the feedback and for the advice. Yes I had that (the pricing) in mind.
I once decided that I should ‘find’ a formula for FL’s weapons, considering damage (both hull and shield) refire rate, velocity, range etc. which would render a price for a given gun (progressively, so that a heavier shot would cost relatively more than a lighter - the price for having a heavier gun). I came up with something, but it implied I would have to redesign the entire FL armory! Still, I’d think that would be ideal. But limited time and laziness will probably have me ending up with some inspired guesses for the guns’ prices.
-
Ok next issue (I’m thinking ahead - haven’t done the gun classes yet)
From StarTrader’s excellent tutorial:
always ensure that your ship’s type parameter is type = FIGHTER or type = FREIGHTER. Anything else (type = CAPITAL / CAPITOL / GUNSHIP / GUNBOAT / CRUISER) will make it roll in the opposite direction
I would say that this might cause some problems for cap ship encounters / formations, in which, if my memory serves me right, it is necessary to distinguish between the types of ships - if you wanna use them, that is. Like when you want to have a Bretonian battleship escorted by gunboats, you can’t have them all be fighter types.
So, how to overcome this? Should I simply make both a playable and a NPC copy separately of each cap ship archetype? Or is there a way to modify (or hack) the game
so that it uses the handling behavior of FIGHTERS or FREIGHTERS for all the ship types, so that I could still use e.g. type = GUNBOAT without making it unhandabke? -
That is not done in this way. The type = fighter / freighter in shiparch.ini is for handling only. Trust me.
The ship type for encounters is requested in the encounter that we name in a system zone, for example area_assault.ini :-
[EncounterFormation]
ship_by_class = 1, 1, sc_fighters<– here
pilot_job = assault_leader_job
make_class = wanderer
ship_by_class = 2, 3, sc_fighters, -1<– and here
pilot_job = assault_job
make_class = wanderer
formation_by_class = fightersThe above calls for (min=1, max=1) of type = sc_fighters whose pilot is set for assault_leader_job
plus (min=2, max=3) of type = sc_fighters,1 rank lower, whose pilot is set for assault_job(See pilot_population.ini for pilot_job types)…
In shipclasses.ini we find:-
[ShipClass]
nickname = sc_fighters<– this ship type class
member = fighter
member = elite_fighter
member = class_fighter<– includes this ship class
…And in npcships.ini we define all the ships a faction can use, according to type and difficulty, here is the Liberty Police Liberty Fighter (Patriot):-
[NPCShipArch]
nickname = li_p_li_fighter_d1-2 <– for Rank 1 and 2
loadout = li_p_li_fighter_loadout01
level = d2
ship_archetype = li_fighter<– can allocate a different ship here for these ranks
pilot = pilot_police_med
state_graph = FIGHTER
npc_class = lawful, class_fighter, d1, d2 <– here is our ship class for this ship[NPCShipArch]
nickname = li_p_li_fighter_d3<– for Rank 3 only
loadout = li_p_li_fighter_loadout01
level = d3
ship_archetype = li_fighter
pilot = pilot_police_hard
state_graph = FIGHTER
npc_class = lawful, class_fighter, d3 <– and for this one[NPCShipArch]
nickname = li_p_li_fighter_d4-19<– and for Ranks 4 to 19
loadout = li_p_li_fighter_loadout01
level = d4
ship_archetype = li_fighter
pilot = pilot_police_ace
state_graph = FIGHTER
npc_class = lawful, class_fighter, d4, d5, d6, d7, d8, d9, d10, d11, d12, d13, d14, d15, d16, d17, d18, d19 <– and for this ship tooWe can equally specify fighter for the above ships instead of class_fighter but the writers chose “class_fighter”.
These ships are selected for the faction in faction_prop.ini :-
[FactionProps]
affiliation = li_p_grp<– faction
legality = lawful
nickname_plurality = singular
msg_id_prefix = gcs_refer_faction_li_p
jump_preference = jumpgate
npc_ship = li_p_li_fighter_d1-2 <– Rank 1 and 2
npc_ship = li_p_li_fighter_d3 <– Rank 3
npc_ship = li_p_li_fighter_d4-19 <– Ranks 4-19
npc_ship = li_p_ge_armored_d2
npc_ship = li_p_ge_armored_d3
npc_ship = li_p_ge_armored_d4Remember the Rank is the difficulty you set in the "encounter = " in your system zone.
OK?
-
Thanks again for an excellent tutorial!
I guess I must have confused the type = line in ShipArch.ini with the state_graph = line in NPCShips.ini
I happily found the relevant files in a 2004/2005 mod project, in which I did have some succesful cap ship encounters. More luck than knowledge I guess, and possible copied from forum tutorials.
I see that, in the NPCShips.ini, I have classified the Liberty Dreadnought as a CRUISER… I also remember I did this because it wouldn’t work otherwise (CAPSHIP or whatever default there is). Weird, because I had it in a formation with some (real) cruisers, escorting it on both sides… And the only distinction I can see is the level. But we can’t have ships of differing levels in one encounter, can we? So, I must work it thru to see how I did it back then… Or try my luck again and copy the whole thing into my present mod and hunt down errors afterwards, but that migth be the road to disaster.
Anyway, your reply is saved to my INFO folder so I can take it to work, where internet is thin and distant, like sunlight on Sedna. I hope everything is quiet, so I can look into all this while being paid