Jestersage

So I noticed both KER and stock show that my AP drops even though I am above 70k. My mods are following: ClickthroughBlocker toolbarControl Craftmanager EVE KER KerbalKonstructs HyperEdit KVV NavBallDocking DockingBallAlignment RCSBuildAid Scatterer Stagerecovery SVE Trajectories ModuleManager Which one caused the problem?

What I would propose is that you can pick either Mun or Kerbin as your main base of operation, but not both.

Quick Challenge: Using a "horrible IVA craft" (KV-1 to 3 or Mk1 capsule), send Kerbalnauts to the Mun, pilot through only IVA and KER. Land them safely, then take them back to Kerbin safely. As this is first iteration of this challenge, I just want to see how many can pull this off. (Unfortunately a certain team IRL didn't).

Starting from 1.7, some parts are moved to zDepreciated folder. While straight-loading of crafts containing those parts will upgrade them, for those that want all the new parts NOW, the following are the name change. NOTE: 1) USE AT YOUR OWN RISK 2) I commend you follow the flow; some parts' names is a substring of another part name. /// Beta to release mark3Cockpit --> mk3Cockpit.Shuttle mk3Fuselage --> mk3FuselageLFO.50 mk3spacePlaneAdapter --> adapterMk3-Mk2 ////////////////////////////////////////////// /// 1.4 /// // TR-2V Stack Decoupler → TD-06 Decoupler stackDecouplerMini_ --> Decoupler.0_ // TR-18A Stack Decoupler → TD-12 Decoupler stackDecoupler_ --> Decoupler.1_ // Rockomax brand decoupler → TD-25 Decoupler decoupler1-2_ --> Decoupler.2_ radialDecoupler.2_ --> radialDecoupler1-2_ // Reason for this: radialDecopler have the same problem,Convert Back // TR-38-D → TD-37 Decoupler size3Decoupler_ --> Decoupler.3_ // TR-2C Stack Separator → TS-06 Stack Separator stackSeparatorMini_ --> Separator.0_ // TR-XL Stack Separator → TS-25 Stack Separator stackSeparatorBig_ --> Separator.2_ // TR-18D Stack Separator → TS-12 Stack Separator stackSeparator_ --> Separator.1_ // ROUND-8 Toroidal Fuel Tank → R-12 'Doughnut' External Tank toroidalFuelTank_ --> externalTankToroid_ // Rockomax X200-8 Fuel Tank → same name fuelTank4-2_ --> Rockomax8BW_ // Rockomax X200-16 Fuel Tank → same name fuelTank2-2_ --> Rockomax16.BW_ // Rockomax X200-32 Fuel Tank → same name fuelTank1-2_ --> Rockomax32.BW_ // Rockomax Jumbo-64 Fuel Tank → same name fuelTank3-2_ --> Rockomax64.BW_ // Mk 1-2 Pod → Mk 1-3 Pod Mark1-2Pod_ --> mk1-3pod_ ////////////////////////////////////////////// ///1.5/// // Mk1 Command Pod mk1pod_ --> mk1pod.v2_ // HECS probeCoreHex_ --> probeCoreHex.v2_ * HECS2 HECS2 // OKTO probeCoreOcto_ --> probeCoreOcto.v2_ // OKTO2 probeCoreOcto2_ --> probeCoreOcto2.v2_ * QBE probeCoreCube // RoveMate roverBody_ --> roverBody.v2_ // Stayputnik probeCoreSphere_ --> probeCoreSphere.v2_ // RT-5 "Flea" Solid Fuel Booster solidBooster_sm_ --> solidBooster.sm.v2_ // RT-10 "Hammer" Solid Fuel Booster solidBooster_ --> solidBooster.v2_ //convert back solidBooster.v2.sm_ -->solidBooster.sm_ ////////////////////////////////////////////// ///1.6/// // Mk2 Lander Can mk2LanderCabin_ --> mk2LanderCabin.v2_ // 48-7S Spark liquidEngineMini_ --> liquidEngineMini.v2_ // RE-L10 Poodle liquidEngine2-2_ --> liquidEngine2-2.v2_ // LV-909 Terrier liquidEngine3_ --> liquidEngine3.v2_ * FL-A10 adapterSmallMiniTall_ * FL-A5 adapterSmallMiniShort_ // ADTP-2-3 Size3to2Adapter_ --> Size3To2Adapter.v2_ * Rockomax Brand Adapter largeAdapter_ * Rockomax Brand Adapter 02 largeAdapter2_ // TVR-200 Stack Bi-Coupler stackBiCoupler_ --> stackBiCoupler.v2_ // TVR-1180C MK1 Stack Tri-Coupler stackTriCoupler_ --> stackTriCoupler.v2_ * TVR-2160C Mk2 Stack Quad-Coupler stackQuadCoupler_ * TVR-200L Stack Bi-Adapter adapterLargeSmallBi_ * TVR-300L Stack Tri-Adapter adapterLargeSmallTri_ * TVR-400L Stack Quad-Adapter adapterLargeSmallQuad_ * Small Nose Cone standardNoseCone_ * Aerodynamic Nose Cone noseCone_ * Advanced Nose Cone - Type B pointyNoseConeB_ * Advanced Nose Cone - Type A pointyNoseConeA_ // Protective Rocket Nose Cone MK7 rocketNoseCone_ --> rocketNoseCone.v2_ ///1.7/// // 24-77 Twitch smallRadialEngine_ --> smallRadialEngine.v2_ // LV-1 Ant microEngine_ --> microEngine.v2_ // LV-1R Spider radialEngineMini_ --> radialEngineMini.v2_ * O-10 Puff omsEngine_ * Place-Anywhere 7 linearRcs_ // RV-105 Thruster Block RCSBlock_ --> RCSBlock.v2_ * Vernor Engine vernierEngine_

It is stock. You will have to stay 1.6 for old saves/start a new one. And they gave you 3 releases to change it -- and I released some text files that allow you to do in-place replacements. That being said, I did some experiment, and notice that with stock loader, any parts that are zDeprecated will automatically upgraded to new parts. So at least your crafts will be fine. Just saved games may have issues.

Below is the actual part name change in craft files. For those that are adventurous, they can use programs such as notepad++ and use "replace in files" to replace the name. NOTE: USE AT YOUR OWN RISK Also, as I discovered, anything moved to zDeprecated will be loaded with the new parts in any case. Based on release window, that means there are 3 release before KSP does it for you. If you are not trying to put the newest stuff out, you may as well just rebuild them manually. // 24-77 Twitch smallRadialEngine_ --> smallRadialEngine.v2_ // LV-1 Ant microEngine_ --> microEngine.v2_ // LV-1R Spider radialEngineMini_ --> radialEngineMini.v2_ * O-10 Puff omsEngine_ * Place-Anywhere 7 linearRcs_ // RV-105 Thruster Block RCSBlock_ --> RCSBlock.v2_ * Vernor Engine vernierEngine_

But how is that different from what had been doen from 1.4 to 1.6? EDIT: I just tried it out. Basically it does the automatic conversion if you go Try To Load anyway (with kerbalX mod). Have not tested it with pure stock loader. What I did: loaded an old Raptor9's craft (in this case, his EV-2C with Thunder) made in 1.2 and still have "Mark1-2Pod" resave it, and it automatically becomes "mk1-3pod" in the file.

So to reiterate it from the 1.7 thread: While I understand where you comes from, one of the reason why some of us are not happy with the Spark/Cub change (back in 1.6) is due to the fact that SuperDraco, which would have been represented as a radial engine, is a OP engine in terms of TWR ; and seeing that many people are trying to Make Dragon/DragonV2... That means that some parts which can be done in 1 part in the past may need 2, which may affect performances. I think if you create an engine with horrible ASL (SuperDraco is only 235s (SL)) but OP TWR, people will be fine. (Draco don't need to be made as Twitch will do the job.) Even if you make it DLC, we will ask you to take our money. EDIT: However, Spark change isn't too bad. I actually ran it through KER, and 8x Twitch is still inferior in both TWR and Delta-V, to 8x Spark but somewhat compariable.

First off, I understand where you are coming from. I think one of the reason why some of us are not happy with the Spark/Cub change (back in 1.6) is due to the fact that SuperDraco, which would have been represented as a radial engine, is a OP TWR engine; and seeing that many people are trying to Make Dragon/DragonV2... I think if you create an engine with horrible ASL (SuperDraco is only 235s (SL)) but OP TWR, people will be fine. (Draco don't need to be made as Twitch will do the job.) Even if you make it DLC, we will ask you to take our money.

I can't download 1.7 Because I am at work right now, and I want to know more about this: Rebalanced the following engines: Twitch, Spark, Place-Anywhere 7, RV-105 RCS,Vernor.

Anyway, can someone who managed to download 1.7 give us a quick report on the balance change?

THIS!

I noticed that 1.7 have the following in patchnote "Previously Revamped Parts moved to zDeprecated. Parts revamped in 1.4:" So I want to know if a craft is in 1.3 with the old parts, will they work, automatically converted, or just plain fail? EDIT: I just tried it out. Basically it does the automatic conversion if you go tryToLoad anyway (with kerbalX mod) What I did: loaded an old Raptor9's craft (in this case, his EV-2C with Thunder) made in 1.2 and still have "Mark1-2Pod" resave it, and it automatically becomes "mk1-3pod" in the file.

Thanks. Guess I do have to wait until they release it and see what parts need to be replaced. Even though they seem to be small amount, I have too much crafts that used them.

Does anyone knwo what are the replaced parts to be introduce in 1.7? All I know is the 4 way RCS block...

In a way, there are no actual MaxQ in stock/MH KSP, simply because the components only have to think about drag and Heat - not structure load (even if you do not bother autostrut). Actual MaxQ is all about the structure load pressure. The reason we throttle down is to minimize heat, as well as use fuel efficently. Typically just keep TWR at around 2 at less than 50k, and 0.6~1+ above 50k, and you will fly efficiently. As far as I know, drag does not increase with more TWR.

In terms of Kerbal Craft: That's a good question, thank you for asking In terms of replica: Putting too much stuff in there where it just plain doesn't belong.... so I guess a Space Launch System clone using 4 or 4x2 solid boosters is over building, but not if you decide to call it Jupiter III and have 2x 3.75m fuel tank on its sides. Or your typical using Kerbal's 3.75m tank for Falcon 9s/Heavy.

I reject your reality and substitute my own!

Yeah. I actually can even put a cover over, until I read the LRV is exposed to the elements. So I figure since it added 150kg, I removed it.

So while I have just complete another craft, since 1.7 is literally around the corner, I will wait for it to release, replace it with 1.7 parts, before pushing it out. For now, please enjoy some simple screenshots for my LEM clone (The actual craft will have Saturn V with it, now clocking at 120 parts) P.S. 1.7 is coming this or next week, right?

First, for those that are feature oriented, the answer is naturally "No such thing as overbuild" IMHO. However, for replica, at what point do you consider as overbuilding? In the case of LM, I am falling into "over-science". How do you prevent that?

They did. It's call DLC.

I think because they would rather the community just suck it up and treat DLC as stock, mods be damned. If I am TakeTwo, challenge such as the "Regional Airline" would not be allowed on this forum because it ban DLC. Well, good thing I am not Take Two.

Updated the page to reflect which probe has reaction wheel

1) Different people, different philosophy. I never say change it. I will just fork it. 2) That being said, this kind of talk seems popular in Seattle, ain't it? Microsoft Windows 10 update style, 737 Max "anti-stall", etc. "feature, not a bug." A hidden feature is a bug, unless you announce it before hand, and even then it's underhand. And just like Linux Mint and etc, I am willing to concede and go with "don't like it, frok it thyself" route.