Checked in the scenario (and a few changes to the HAC drawing code).
There are 2 ways to do this; the ET type can be set in the mission file, or (since the ET is always a separate vessel), we can have different config files for the ET types ,e.g.This is just a suggestion, nothing else: How about configurable ET types in the mission file(s)? Currently we're flying SLWTs for all missions, when it would be appropriate to fly a LWT or a SWT.
ET:SSU_LWT
Makes sense. I guess that's the best way to go.There are 2 ways to do this; the ET type can be set in the mission file, or (since the ET is always a separate vessel), we can have different config files for the ET types ,e.g.
IMHO, the different config files would be better; any comments?Code:ET:SSU_LWT
Both. It's pretty easy to spot the different ET types, thanks to the foam and intertank stringer design.What are the differences between the different tank types; is it just mass, or are different meshes used as well?
Not yet, I'm working on a new base mesh.Do we have meshes for all 3 types?
Yes. Here's the main texture for the the new ET mesh, do you think you could make the different textures based on the photos above?Look's to me like it could be done with just texture.
Unpainted SWTs: STS-3, STS-4, STS-5If you can give me a list of a few missions with the different tanks, I could look up some pics asee some of the differences to go by.
Considering just how different the various ET types are, then I would guess so. Unless there's a way to apply a texture over another texture.Would it be useful to allow the ET mesh (or texture, if this is easier) to be specified in the scenario file? A default mesh (which would depend on the ET type) would be used if nothing is in the scenario file. Also, will the burnt ET texture change for different ET types?
It is. It's just used in an outside application.My mistake, I thought it was my Orbiter shuttle. :blush: