NathanKell

The way StretchyTanks works is by applying a scale transform to a fixed model. That means you can only scale, not warp, the tank. To get what you're asking for (what many people have asked about upthread) you need to change all the stretching code to use a method like DYJ does in Procedural Wings, where the model is transformed by bones. I've contemplated, at times, trying to make a new procedural tank mod of my own using that method, but (a) it's a lot of work and ( pWings has a pretty restrictive license.

I've been waiting since my partner in crime is at present sick. Apologies for the confusion. I haven't yet installed B9, so didn't know about that bug. Thanks for the catch!

It's not gas fed directly into the tank, it's gas fed into a bladder that expands from the top of the tank and pushes the fuel down, IIRC.

If you want things to be hard, just decrease engine thrust and Isp. The Isp is way too high anyway for non-hydrolox rockets.

ChestBurster is updating MFS Configs, but posted an in-progress update a couple pages back: https://www.dropbox.com/s/uzwjptwcd09nhke/MFS%20Configs%20V1.6%20WIP.zip Said it included KOSMOS. And I'm sure it includes the 100, that was put in a long time ago.

The Early Satellites By the time the Kritish joined the space age, the Kerbicans and Kermans had put a number of satellites in orbit. Kerman Satellites Program: Vör Programm Mission Control: Reichsraumfahrtamt (Imperial Spaceflight Office) / Reichsnachrichtendienst (Imperial Intelligence Agency) Administered By: RRA, RND, Reichsverteidigungamt (Ministry of Defense) Launch Vehicle: Langschiff-B Launch Site: Sternburg Raumhafen SR-4C, Deutsch-Ostafrika Objective: Signal Relay / SIGINT Intended Orbit: Kerbostationary Equatorial Outcome: Success Background: The Kermans' first attempt at kerbostationary satellites, and the first use of Launch Complex 4 at the Sternburg spaceport, the Vör program, like the later Kritish Prosperabimus, served a dual function. They were signal relay satellites, designed to receive and retransmit radio signals from a fixed area on Kerbin. They were used to test KEO relay of civilian and military traffic, but could also be tasked by the RND to "listen in" and retransmit other traffic. For this purpose they were equipped with a cold-gas RCS/OMS for plane changes and dish attitude changes. Vör satellite atop Langschiff-B/b launcher. Note small hypergolic upper stage atop Wallarmbrust booster. This is the "breit" version with a large fairing, and the upper stage inside the fairing. Vör satellite in Kerbostationary Equatorial Orbit (2,868.8 x 2,868.75km at 0.1 degrees) Mission: Halo 1-4 Program: Halo Programm Mission Control: Reichsraumfahrtamt (Imperial Spaceflight Office) Administered By: RRA, RVgA Launch Vehicle: Langschiff-C with custom orbital maneuvers bus Launch Site: Sternburg Raumhafen SR-6A, Deutsch-Ostafrika Objective: Signal Relay Intended Orbit: Medium Kerbin Outcome: Success Background: The Halo satellites were the medium-orbit counterpart to the Vör satellites. They were designed as a relay constellation (a halo) 250km up. Not only would they relay signals ground-to-ground, but they could also obviate an expensive ground relay network for communication with other Kerman satellites. They were designed to be launched four at a time on a special bus, which would carry them to an orbit of 250 x 102km. It deployed one satellite each orbit, and the satellite then circularized at 250km. When all satellites were deployed, the bus fired its thrusters one more time to deorbit itself. The bus used the same E5R thrusters as the Langschiff-B's standard hypergolic upper stage; however, they were mounted outboard so as not to damage the satellites. Halo was the first launch of the Wallarmbrust-C repurposed for launch vehicle use as the Langschiff-C, and it was necessary given the large mass of four satellites and their bus. Halo 1-4 in fairing atop Langschiff-C. Bus with tank, thrusters, antennae, and guidance ring can be seen at top. Halo 3 in orbit with its omnidirectional antenna, two high gain antennae, and solar panels deployed. Mission: Struve 1 Program: Struve Programm Mission Control: Reichsraumfahrtamt (Imperial Spaceflight Office) Administered By: RRA Launch Vehicle: Langschiff-B with no upper stage Launch Site: Sternburg Raumhafen SR-4B, Deutsch-Ostafrika Objective: Kerbodesy, kerbin science Intended Orbit: Low Kerbin, Polar Outcome: Success Background: Named after the famous Struve family of astronomers, the first satellite to bear the name was related to the progenitor of that family: Friedrich Georg Wilhelm von Struve. While that Struve was more known for his work on double stars, he also gave his name to an early effort in kerbodesy (the measurement of Kerbin), the Struve Kerbodetic Arc, a set of survey stations to accurately measure Kerbin's radius. Given that the chancellor was a great admirer of the radical democrat and proto-socialist Gustav von Struve (later Gustav Struve), that too must have had an affect on the RRA's naming process. Struve 1 carried highly sensitive equipment to measure Kerbin's gravitational field, as well as a radar system to determine the height of ground above sea level to compare with the gravity measurement. Later analysis of the data allowed scientists to also predict concentrations of various resources, given the change in density. Struve 1 atop Langschiff-B launcher with no upper stage. Struve 1 used onboard RCS propellant to circularize. Struve 1 in its 105x105km 86 degree polar orbit. Kerbican Satellites Mission: Helios 1 Program: Helios Program Mission Control: Kerbican Space Agency Administered By: KSA Launch Vehicle: Koddard III Launch Site: CSC LC-3, Union of Kerbican States Objective: Extra-Kerbin probe / solar observation Intended Orbit: Kerbolocentric Outcome: Success Background: The Helios 1 probe was the first kerbal-made object intended for extra-Kerbin orbit (Mond 3 was the first to achieve escape velocity, but by then communication had ceased). After the failure of Meton 1 and 2, KSA decided it needed more information on the space at and beyond high Kerbin orbit. In particular, it appeared that radiation damage was the cause of the guidance failure on Meton 2. Additionally, scientists had been clamoring for more investigation of Kerbol, and the Koddard III launch vehicle, capable of placing a satellite in KEO, was also capable of placing a smaller satellite and small solid upper stage in LKO, whereupon the kick stage would fire, giving the satellite an escape trajectory. Helios 1 was another Explorer-derived satellite, this time featuring eight solar panels, double the batteries, and a small high-gain directional antenna. The sensor package was designed to detect radiation and, once free of Kerbin's interference (and before the satellite was out of communication range) to make observations of Kerbol. Helios 1 and solid kick stage in fairing atop Koddard III LV. The kick stage is little more than a shortened K-II solid booster with vacuum-optimized nozzle, and as such quite reliable. Kick stage firing to place Helios 1 on escape trajectory. Kerbin recedes into the distance as Helios 1 begins the first half of its mission. Note dish pointed at Oracle II-1. Mission: NavSat 1B Program: NavSat Program Mission Control: Kerbican Space Agency Administered By: KSA / Kerbican Union Navy Launch Vehicle: Koddard IIb Launch Site: CSC LC-3, Union of Kerbican States Objective: Navigational satellite Intended Orbit: Low Kerbin, 45 degree inclination Outcome: Success Background: The KU Navy had long sought improved means of navigation for their ships, sponsoring many projects over the years. With the dawn of the space age, satellites seemed an obvious means to derive navigational fixes. Already partnering with KSA on Project Aquarius, the Navy found it easy to request some KSA launch vehicles and KSA experience to help in developing their satellites. Given its potential to revolutionize civilian nautical navigation as well, the NavSat program found enthusiastic backing at KSA, and indeed throughout the administration. NavSat 1 was scheduled for launch on the first Koddard IIb. The Koddard IIb LV used the new Attica upper stage, derived from the improved K-Ib used on the Koddard III. Sadly that first launch failed, taking a NavSat (later named 1A) with it, but the followup launch, NavSat 1B, succeeded admirably, and the satellite was thereafter known as just NavSat 1. NavSat 1 was launched at a 45 degree inclination, to test the NavSat system; the KU Navy had plans to launch a constellation of eight such NavSats into polar orbits, to allow for whole-Kerbin coverage and spares. NavSat 1B atop Koddard IIb LV. Note new Attica upper stage. The Attica upper stage is a refinement of the K-I upper stage, and nearly identical to the K-Ib, but renamed following KSA's naming guidelines. NavSat 1 in 150x150km at 45 degree orbit. Mission: Telstar 1 Mission Control: Kerbican Space Agency Administered By: KSA / Kerbican Telephone and Telegraph Launch Vehicle: Granite-Attica Launch Site: CSC LC-5, Union of Kerbican States Objective: Communications satellite Intended Orbit: Medium Kerbin Outcome: Success Background: Telstar was designed as a testbed for commercial communications relay via satellite. Covered in solar panels to power the advanced electronics necessary for its store/forward mode of operation, Telstar 1 could handle four multiplexed telephone calls over its single transponder; unlike the earlier Oracle satellites the transponder allowed it to relay them in real time. It was designed to orbit three times per day, to provide considerable "hang time" over the UKS. At its 1068km orbit, necessary for that period, it could relay signals from the UKS to ground stations across both oceans--when above the horizon, of course. Telstar was designed in partnership with KT&T, who used it to relay telephone calls, and the public-(semi-)-private partnership was an attempt to see how space could be used for more than research. Telstar 1 atop Granite-Attica LV. The Attica upper stage is a refinement of the K-I upper stage, and nearly identical to the K-Ib, but renamed following KSA's naming guidelines. Telstar 1 in its 1068km orbit.

Well, as a holdover until there are such parts, you can just decrease the boil-off rate (or even turn it off altogether). You can edit those fuel specs in Modular Fuels/RealFuels/Resources/ResourcesFuels.cfg and find the Cryogenic tank type (if that's the one you want to decrease boil-off for) and decrease the loss rate.

I would dearly love a larger VAB too...

Thanks for the node sizes! (And the rest, obviously...)

bs1110101, check the respective threads. They're there now. Pipcard, thanks! I decided I wouldn't try to clone either Ariel or Prospero for this one (unlike Pioneer and Ranger, which you'll see shortly). I figure Mulbin will get to them eventually. And you know, your KASDA thread was quite an inspiration for this, so thanks for that too!

For LH2, from to 0.0000000005 to 0.0000000002, so to 40% of normal. ialdabaoth was going to add an active cooling system at some point, to reduce it further.

There are already some tanks set up for that type, like the Jumbo 64. But if you want to change a tank, go to your modular fuels folder, open the CFG file for where the part is from (i.e. Squad if it's stock), find the name of the part (note, this is the internal name, not the part's title you see ingame) and change its type from Default to Cryogenic. If you need to find a part's internal name, open its own CFG. Like if you wanted to change the Rockomax X-8, you know it's from Squad so you open the Squad folder, then Parts, then Fuel Tanks. Look in each Part cfg (in each of the subfolders) until you find one that has the line title = Rockomax X-8 (or whatever). Then look and see what the name is (look, above that, for the line name = SOMETHING). That's the part's name.

Tank type cryogenic has a much lower loss rate, yes. It has the insulation.

Hey AncientGammoner, Looks like we're having PM problems again? So trying a post. The Stretchy SRB (and my changes to the codebase to support the new textures, and better scale MFS values, incorporating Starwaster's fix) is here: https://www.dropbox.com/s/q6c7qdk7fnkihyn/StretchySRB.zip The source is next to the DLL. This gets unzipped into the existing StretchyTanks folder. The SRB counts as a SuperStretchy, and G+mouseover scales burn time (and, inversely, thrust)

As I said in the notes above, I wish there _were_ normal maps for procedural fairings models, but there aren't. And that's something that can only happen if e-dog re-exports with the normal map on, I think, or hacks the code to force on a normal map (like ST does). (It's sure possible--the custom fairings KOSMOS uses have normal maps. But they use different meshes.)

Here are some new textures for the fairings; they're designed to blend in with StretchyTanks (and my new textures for ST). https://www.dropbox.com/s/qrgcs9fhmz3pq6l/PFTextures.zip Examples: US Style German style Stretchy Tanks "stock" style (needs a normal map on the fairings--ohai e-dog...) Stretchy Tanks style. (Sorry about the stretching...it's how PF works.)

Compare the parachute cfg for Orion to the one sumghai just released for the SDHI SM. Apparently the modules are in the wrong order or something, or the cut speeds aren't right.

Conti already has pull requests on your github

So, figured I should start translating the Latin if it's obscure (hopefully Sagitta isn't obscure, especially given the post title?). Hence all the parentheticals. And, astropapi1, after all that it ain't Black Arrow (though it kinda looks like it)--more like an early Blue Streak with tiny upper stage, with Atlas stage-and-half setup.

Arrow to the Stars The Kritish Enter the Space Age RED GLADIUS As the successes to their east and west piled up--though none had yet beaten the Kritish feat of a Kerbal in space--the Kritish stepped up their booster programs. Finally, the program codenamed RED GLADIUS bore fruit. Based on the BLUE EQUITE intermediate range missile but considerably scaled up, the RED GLADIUS relied on Kritish ingenuity to make up for (temporary) technological deficiency. The Kritish had not yet had success with lighting rocket engines in near-vacuum conditions (notably the HARC lit its rockets while still in the atmosphere), and did not yet trust staging for that and other reasons; nor did they have as much access to Krodinan solid rocket technology as did the Kerbicans. Thus they came up with a unique "stage-and-a-half" design. As innovative as the single-wall pressure-stabilized tanks used on the Kerbican Prometheus, the stage-and-a-half design ensured that all three engines would be lit at launch. One minute into flight, the booster would be jettisoned; the two sustainers would continue to fire until MECO, over a minute and a half later. This greatly increased performance compared to a single-stage design and meant that total mass (and the thrust needed to lift it) were much less than the Prometheus, despite needing a larger reentry vehicle. The Red Gladius RV was a slightly-scaled up Blue Equite RV with a small orbital maneuvering system using hypergolic monopropellant. All told, Red Gladius massed half again what Blue Equite did, and launched with double the thrust. The booster was a derivate of the Blue Equite's Decurion engine, the Miles; the sustainers were brand new, advaned Tribunes with half the thrust but a full 315 seconds vacuum specific impulse. The missile suffered considerable teething troubles, but on the eighth flight (and third revision) it worked flawlessly. Launched from Woomera, the dummy RV splashed down twelve and a half minutes later, 1,250km downrange. Mission: IGNIS CAELI 8 Program: IGNIS CAELI (Fire of Heaven) Mission Control: Royal Air Force Administered by: Ministry of Defence / Ministry of Space Partners: Royal Aircraft Establishment, Rocket Propulsion Establishment, Atomic Weapons Research Establishment, Rolls Royce, de Havilland Launch Vehicle: Red Gladius Mk3 #4 Launch Site: Woomera, Launch Area 3 Objective: ICBM Development Outcome: Success Notable Flight Events T-00:02:00 Red Gladius Mk3 #4 being assembled before rollout to LA-3. T+00:00:00 All engines green, umbilical disconnect. Liftoff! T+00:00:19 Roll program ends, pitch program begins. T+00:01:00 Boost engine dropped. Note remaining kerosene in the feed line lighting off; while no danger to the rocket, later Red Gladius boosters will not shut down boost engine until after feed lines are cut (to burn remaining fuel), and only then jettison it. Sustainers operating perfectly. T+00:02:41 MECO, fuel exhausted. T+00:02:50 Booster staged away from support bus/reentry vehicle. T+00:02:55 OMS test fire. T+00:11:50 Peak reentry heat. Splashdown at T+00:12:22, 1,251km downrange. BLUE SAGITTA - Prosperabimus Mission: Prosperabimus Program: BLUE SAGITTA Mission Control: Ministry of Space (and GCHQ) Partners: Royal Aircraft Establishment, Rocket Propulsion Establishment, Oxford University, Rolls Royce, de Havilland Launch Vehicle: Blue Sagitta Launch Site: Woomera, Launch Area 6 Objective: Signal Relay, Kerbin Science Outcome: Success Description: Launch the Prosperabimus satellite into a 150x150 at 45 degree inclined orbit. Launch vehicle is Blue Sagitta, composed of Red Gladius-derived stage-and-a-half booster and HGMP-1 upper stage. Prosperabimus will act as signal relay and conduct kerbin science experiments once in space. Background: While development of RED GLADIUS was ongoing, its potential use as a satellite launcher was studied. A small second stage and satellite payload could easily fit within the massive fairing used to house the reentry vehicle for the missile, and its payload of approximately two tons would be enough for a small satellite and upper stage. Thus was born the BLUE SAGITTA program and launch vehicle. However, given the problems the Kritish had been having with vacuum-ignited upper stages, this upper stage would have to use hypergolic propellant, in particular the same hypergolic monopropellant used in the Red Gladius OMS. This stage was christened the HGMP-1 upper stage, and was built with a unique feature: three small solid motors would fire on payload separation to clear the stage from the payload's orbit. Unlike other programs of Kritain's space efforts, HGMP-1 did not receive a Rainbow Code, and in particular not a Latin-derived one as other space components did. With the Red Gladius booster proven in multiple tests, that stage of Blue Sagitta seemed quite reliable. Further, the thruster used in HGMP-1 was merely a scaled-up version of those used in the Red Gladius support bus, and so the MoS felt safe in testing Blue Sagitta in all-up configuration with an actual satellite aboard. The satellite was built by the Royal Aircraft Establishment in cooperation with Oxford University for two roles: it would act as a space-born signal relay, and with various sensors perform kerbin science experiments. The project lead was fond of the works of the Kard and at first wanted to name it Prospero, after the magic it would do in space (and it being a perfectly good Latin verb); however, given the end of that play, the team prevailed upon him to change it to the first person plural future, Prosperabimus ("we shall prosper"). Prosperabimus had a large guidance ring, with a short truss placed atop it. Inside were batteries and RCS tanks. Atop it was a large, long-range antenna. On the sides of the truss were large solar panels and small RCS thrusters. Unlike the small, uncontrollable first satellites of the other powers, Prosperabimus was designed for a long life in orbit, with considerable propellant tankage. Beyond keeping it in a stable orbit, small maneuvers could even be conducted with the thrusters. This last requirement, and indeed the large power-generation abilities of Prosperabimus, were related to its third, secret mission. It was later revealed, under the Thirty Year Rule, that GCHQ, the United Kingdom's signals intelligence agency, had also played a role in the satellite's design. Not only was it suited for signal relay, but also signal intercept and relay. The inclined orbit, which brought it over most of Kerbin's surface, was necessary not only for the kerbin science mission, but also the sigint mission, as were the solar panels and large suite of power-hungry electronics aboard. If successful, more such satellites would be launched. Notable Flight Events (Boost phase events omitted unless different from Red Gladius flights) T-00:02:00 Prosperabimus and HGMP-1 upper stage inside fairing, two hours prior to rollout at LA-6 at Woomera. T+00:00:50 Boost engine separation. Note early separation time, as total payload for the booster is less than the RV and warhead. This is an improved booster where the boost engine fuel line is cut well before separation. T+00:04:20 After MECO at 2:50 and fairing jettison at 4:15, HGMP-1 upper stage and Prosperabimus satellite reorient for orbital insertion. Red Gladius booster can be seen in the background at bottom left. T+00:15:01 HGMP-1 burns for orbital insertion, 150x150km at 45 degrees. T+00:15:19 Final separation: the small solid motors ignite, pushing away the HGMP-1 upper stage. Prosperabimus in orbit.

FYI, my fork is totally backwards-compatible, and the new features default to off (unless you use that zip I just posted, which is a simple zip of my own RT folder with the settings already at non-default...). It is perfectly compatible with the RT1 antennae and dishes (in fact, it uses the RT1 part module since it's only a slight tweak of the RT1 code). So if you like RT1 antennae, feel free to use them! But the one thing I did take from RT2 is moving all those antenna and dish modules (that establish range) out of the parts and put them in MM cfgs. So you can do all your tweaking in one place. That said, if you do tweak (or do use other antennae/dishes, like from RT1) then you probably should decrease the range. Be a bit OP otherwise.

Uh...what's wrong with the ejection module from EVA parachutes? Put the module in the pod cfg and presto, ejection seat.

gwichy, you're most welcome! Let me know how it plays, and if the balance works vs. the original...

Legnad: the formula for multiple antennae on a single craft is: longest_range + ((sum_of_all_ranges - longest_range) * 0.25). gwichy: Hmm. Sounds like install problems. But my install instructions are pretty wonky, so here's a better approach: Delete EVERYTHING in your RemoteTech folder. Replace its contents with the Extracted contents of this: https://www.dropbox.com/s/16928ut2x37kih8/MyRemoteTech.zip Things should work then. Note you'll probably have to move the window around some (or via settings reset its coordinates) since I have a big screen.

Chrison, you might want to look at Mission Controller Extended. Does that, + missions. http://forum.kerbalspaceprogram.com/threads/43645-%28KSP-0-21%29-Mission-Controller-Extended-%28MC-Version-20-2%29-%28FORK%29-%28ALPHA%29 Faark, yeah, my best bet right now is on setting engine configuration to trawl through fxgroup 'running', delete all emitters with "flame" and then add the appropriate ones....but I'm puzzled why SaveEffects and LoadEffects don't seem to work.