Bridge Commander Central
BC Forums => BC Scripting => Topic started by: starfox1701 on May 26, 2008, 10:54:59 PM
-
Ok this is a simple question, does each model need its own hardpoint script? By this I mean if I have say 4 different Galaxy MkII models do I need 4 different scripts if I only want to use one model at a time or will one script work for all the models as long as they all have the same named .NIF?
-
Each model must have its own ship script, but they can all use the same hardpoint. The LC's Ambassador pack and Dr_McCoy's Constellation Pack are perfect examples.
-
For the best effect for most mods, separate ship file (in scripts/Ships) and a separate plugin entry (scripts/Custom/Ships, but you can share files resulting in multiple plugins per file, but each must be unique, in fact, unless you want to replace a ship you need unique names).
Hardpoints can be shared, in fact, you can even extend a hardpoint for use with another ship. ;)
It's used for the "hero" ships in BC.
-
But I don't have to change the script if I'm just changing the model like Replacing the SNS Galaxy with the DJ Galaxy. As long as the models are scaled and named the same the script will work fine? Also what do you mean by extending a hardpoint for use with another ship? Is that like having 2 ships using the same file at the same time?
-
The hardpoint script places the ships systems around the model. But since there are some differences from one model to another of the same shipclass (even if both are scaled correctly), some systems will be out of place if you just change the model (phaserarrays as example).
-
the DJ galaxy and the SNS for example are based on two completely different studio models, the SNS being based off the original ILM model designed for the pilot (as used in Generations) and the DJ is an amalgam, largely based on the model designed after season 3 by Greg Jein, there are some subtle differences, so the hardpoints are not quite compatible, but they could be modified to fit each other
-
So you pretty much need to take it on a case by case basis.
-
While that is true, it is also not hard to use the SNS Galaxy HP in conjunction with the DJ Galaxy model. As Aces_High pointed out, there will be differences by they can be adjusted very easily.
-
Ok, let's say, we have 4 ships, A, B, C and D.
A and C use hardponts 1, B uses 3 and D uses 2.
But 2 "extends" 1, and increases shield power.
And 3 "extends" 2 and adds an extra phaser array.
So, multiple ships can use the same hardpoint.
-
I know that method is used for the SNS Galaxy, but exactly how do you tell the extension to point to the parent hardpoint?
-
Like I said, Hero ships. ;)
Here are a couple of examples:
scripts/ships/Hardpoints/e2m0warbird.py
scripts/ships/Hardpoints/enterprise.py
scripts/ships/Hardpoints/geronimo.py
scripts/ships/Hardpoints/matankeldon.py
scripts/ships/Hardpoints/rankuf.py
scripts/ships/Hardpoints/biranustation.py
And those are just the generic ones, there are more (I believe) mission specific ones that are in the Maelstrom directory (or rather, subdirectories of that).
-
So it like the include command in Armada. It tells the game use script 1 except what is changed in script 2. Can you also point multiple scripts at the same model for things like minor veriants and refits?
-
The same model is always possible..
It's kinda like the include, except that this is all programming code.
You should see, hardpoints, models, textures, projectiles as resources, completely seperate stuff, that gets bound in the ship file (scripts/ships) to form a ship.
Then you have a ship plugin, in scripts/Custom/Ships/ that points to a ship file and makes it known in BC with extra info needed to do that.
-
You should see, hardpoints, models, textures, projectiles as resources, completely seperate stuff, that gets bound in the ship file (scripts/ships) to form a ship.
Making the hardpoint isn't too hard, but how to you create the scripts/ship.py that contains the model information from scratch. For example, the Antican fleet pack comes with models but no ship script or hp. I can use the MPE to create a hp but where do I begin with the ship.py?
-
I guess that if you know how to code the scripts then its just a mater of looking at the model and deciding whats a gun and so forth.
-
The ship script "simply" binds everything together, what you need to do is copy an existing one and fill in the blank spots (or rather, all the references that refer to the original use of the file).
-
That's easy enough, but what about the LOD info. There are different values for different ship scripts. For instance, here's one taken from a Constellation and CE Galaxy. Does this make a difference or can I use any ship script?
Constellation
# Create the LOD info
if (not App.g_kLODModelManager.Contains(pStats["Name"])):
# Params are: File Name, PickLeafSize, SwitchOut Distance,
# Surface Damage Res, Internal Damage Res, Burn Value, Hole Value,
# Search String for Glow, Search string for Specular, Suffix for specular
pLODModel = App.g_kLODModelManager.Create(pStats["Name"])
pLODModel.AddLOD(pStats["FilenameHigh"], 10, 120.0, 15.0, 15.0, 400, 900, "_glow", None, "_specular")
pLODModel.AddLOD(pStats["FilenameMed"], 10, 300.0, 15.0, 15.0, 400, 900, "_glow", None, "_specular")
pLODModel.AddLOD(pStats["FilenameLow"], 10, 800.0, 15.0, 30.0, 400, 900, "_glow", None, None)
CE Galaxy
# Create the LOD info
if (not App.g_kLODModelManager.Contains(pStats["Name"])):
# Params are: File Name, PickLeafSize, SwitchOut Distance,
# Surface Damage Res, Internal Damage Res, Burn Value, Hole Value,
# Search String for Glow, Search string for Specular, Suffix for specular
pLODModel = App.g_kLODModelManager.Create(pStats["Name"])
pLODModel.AddLOD(pStats["FilenameHigh"], 10, 200.0, 15.0, 15.0, 400, 900, "_glow", None, "_spec")
pLODModel.AddLOD(pStats["FilenameMed"], 10, 400.0, 15.0, 15.0, 400, 900, "_glow", None, "_spec")
pLODModel.AddLOD(pStats["FilenameLow"], 10, 800.0, 15.0, 30.0, 400, 900, "_glow", None, "_spec")
-
Not sure but I don't see why you need more than one script. Just because the detail of the model goes down doesn't mean she has any less systems or that they are in a diferent place.
-
You need to check if the model you want to integrate uses specular textures. If it does you need to adapt the "_specular" suffix to whatever suffix is used for these specular textures (e.g. "_spec").
The other parameters change the visible damage and how far this model is viewable ingame. If you would like to know which number changes a specific thing you need to read the comment above:
# Params are: File Name, PickLeafSize, SwitchOut Distance,
# Surface Damage Res, Internal Damage Res, Burn Value, Hole Value,
# Search String for Glow, Search string for Specular, Suffix for specular
I don't think there is an ultimate ship.py which is perfect for every model but there might be one which is at least acceptable for most ships.
-
Those options are there to optimize models for things like damage.
Some models are more complex than others, and can cause BC to crawl to a slow with the "right" damage (right as in, just right to cause BC to take the worst case senario for the damage generating algorithm). So tweaking those can in fact increase speed in BC.
-
I guess thats a trile and error thing.