undercoveryankee

It's been three or four days that I didn't really check the forum below the front page. Please give me at least a week before you start telling people that my work is obsolete, and if you test it and tell me what's broken I can be more productive when I do have time to work on it.

Should work. The USI packages are compatible with both versions, and I haven't seen any changes in Interstellar 0.13 that would break any of the things that I change.

In real physics where surface area is not proportional to mass, a denser object of the same shape will have a faster terminal velocity. The Wikipedia page has a derivation of the equations that show terminal velocity varying with mass. Or if you would rather test for yourself, find a place where you can drop an empty plastic bottle and a full plastic bottle from fairly high up and see which one falls faster.

The best alternative we have so far, Alternative Tree Configurator, is able to rename and rearrange existing nodes, including the 1000-science reserved tier, But no one has found a reliable way to create new nodes in current KSP. If we have to do without new nodes for long, using ATC to shuffle the reserved nodes from one 1000-science tier into two or three tiers will help a little. Or Squad could give us a recommended way to create new nodes, or someone could stumble across a solution and contribute it to ATC. So it's annoying, but I wouldn't call it the end of Interstellar.

Yes. http://forum.kerbalspaceprogram.com/showthread.php?p=1458077#post1458077

Thanks for the catch. Edited the post and the file on Dropbox.

I don't know the costs of the TreeLoader nodes, but you should be able to find the right numbers in WarpPlugin/tree.cfg.

I've been experimenting with my own build of RealChute trying to isolate the problem with stock chutes. I may be making some progress, but whenever I try to open a window that displays the version number in my build, I get this exception and no window: ArgumentException: There must be 2, 3 or 4 components in the version string. at System.Version..ctor (System.String version) [0x00000] in <filename unknown>:0 at RealChute.RCUtils.get_assemblyVersion () [0x00000] in <filename unknown>:0 at RealChute.SettingsWindow.OnGUI () [0x00000] in <filename unknown>:0 I'm building with Mono's command-line xbuild on OS X. Any pointers on how to get my build to report a valid version?

There is intentionally no way to use stupid_chris's releases on Windows 64-bit because distinguishing people who need help with the mod from people who are just having bad luck with the experimental build causes modder burnout. If you're comfortable building RealChute from source, there's nothing stopping you from compiling a version without the checks for personal use. Just respect stupid_chris's license decision and don't redistribute.

Like any MM patch, you can put it anywhere under GameData. I would put it either under WarpPlugin or at the top level of GameData. I don't recommend putting it inside the TreeLoader folder because I recommend deleting TreeLoader completely.

I took a few minutes to write up a ModuleManager config to move all of the upgrades from TreeLoader nodes down to stock nodes. I move some of the parts' initial unlocks from the 1000-science reserved-for-mods tier down into stock nodes so it makes sense to have upgrades in the 1000-science tier. Copy and paste from here or download a file that already has the right extension from https://www.dropbox.com/s/9cvtczz58x06qx3/KSPI-0.13-no-treeloader.cfg?dl=0 . @PART[AntimatterReactor*] { @TechRequired = advScienceTech @MODULE[FNAntimatterReactor] { @upgradeTechReq = experimentalScience } } // Since I moved the AM reactors up to make room for their upgrade, I need to // move the tanks as well. @PART[AntimatterTank*] { @TechRequired = advScienceTech } @PART[FNFissionFusionCatReactor] { @TechRequired = specializedElectrics @MODULE[InterstellarCatalysedFissionFusion] { @upgradeTechReq = experimentalElectrics } } @PART[FusionReactor250,FusionReactor375] { @TechRequired = metaMaterials @MODULE[InterstellarTokamakFusionReactor] { @upgradeTechReq = nanolathing } } +PART[FusionReactor250] { @name = placeholder_fusion_upgrade @TechRequired = nanolathing @category = -1 @title = Tokamak Upgrade } @PART[NuclearReactor*,FNPFissionReactor*] { @MODULE[InterstellarFissionMSRGC,InterstellarFissionPBDP] { @upgradeTechReq = metaMaterials } } @PART[FusionReactor0625,FusionReactor125] { @techRequired = specializedElectrics @MODULE[InterstellarInertialConfinementReactor] { @upgradeTechReq = experimentalElectrics } } @PART[*MPD] { @MODULE[ElectricEngineControllerFX] { @upgradeTechReq = experimentalScience } } @PART[ThermalTurbojet*] { @MODULE[FNNozzleController] { @upgradeTechReq = hypersonicFlight } }

Yes. Now that CRP integration is caught up to the latest USI packages, a no-TreeLoader configuration for the upgrades will probably be my next project.

Here's what I do: Once I have a ring of satellites set as close to the same period as I can get with the thrust limiters on the engines and Mechjeb/KER readouts, I hand-edit the save file to give them all the same semimajor axis. I wouldn't mind a mod that would allow me to right-click the probe core and say "copy the SMA of my target", but to get around rounding error when the vessel goes on rails you would have to do the orbit editing after the player switches away from the vessel. Are there any existing mods that adjust the orbits of inactive vessels?

LH2/LOX was used on the Saturn V second and third stages. (http://en.wikipedia.org/wiki/Rocketdyne_J-2 ) - - - Updated - - - You remove treeloader by deleting GameData/Treeloader or not installing it when you install Interstellar. No rocket science required.

If you get the EPL->Karbonite conversion and its dependencies, you'll have ore extraction using the same modules that Karbonite uses. Heads up that the conversion needs an unofficial update for the last couple of Karbonite versions (http://forum.kerbalspaceprogram.com/threads/89774-24-2-%28V-16-7%29-ExtraPlanetary-Launchpads%28EPL%29-Karbonite-Adaptation-%289-10-14%29?p=1446360&viewfull=1#post1446360 )

Thanks for the report! Good to know things still at least look sane. Honestly, I thought the Interstellar uranium fuels would have more restrictive flow modes than the EnrichedUranium. When I saw that Interstellar uranium was ALL_VESSEL, I didn't see any need to worry about NO_FLOW uranium on my end. I'll work on adding Interstellar fuels to the portable transfer cans in the next update, but you are no worse off with an MKS lab producing UF4 than you are with a KSPI refinery producing UF4. And since USI doesn't actually have a Uraninite drill until the next update, the important part at the moment is that Interstellar and SCANsat are using the same maps, and I'm reasonably confident that we have that. Conversions and refueling will be polished once I can test them without having to configure my own drills and tanks first.

You still need to have the current version of Firespitter. It complains about compatibility for now, but the animation module that the 6S parts use is reported to work adequately.

All of the parts are configured to appear in stock nodes without further config editing if you remove TreeLoader entirely. It's not as balanced as the full tree, but it's playable.

I didn't bother to check. The first time I installed one of the experimental bundles on my test copy of 0.24.2 (sometime in September before the stable release of ORSX), I got a freeze at the loading screen and out-of-memory exceptions in the log, so I installed ATM.

It's listed as compatible with 0.25 because the only thing that's broken is TreeLoader. In this state, saying it's compatible with 0.25 is less wrong than saying it isn't.

I've posted a new version at https://www.dropbox.com/s/dxpl5o85th7jd5l/KSPI_CRP_20141011.zip?dl=0 that merges uranium maps and allows the MKS/OKS science lab to produce Interstellar uranium fuels as well as EnrichedUranium. Tested on KSP 0.24.2 with Interstellar 0.12.2 and the USI_ALLMODS_2014.10.06 combined distribution. Testing on 0.25 with Interstellar 0.13 is waiting for an update to Active Texture Management. The first time I tried Interstellar and a full USI_ALLMODS package together, I found that I needed ATM.

Researched parts becoming unresearched can be a symptom of having duplicate parts installed. Make sure you have only one copy of anything in the ART package.

To clarify: FAR 0.14.2 disables itself on 64-bit. FAR 0.14.1.1 does what @wingnutspeed says: attempts to run on 64-bit, warns about not being tested on 0.25, but tries to run anyway. Even if the results appear promising at the moment, running long-term under a compatibility warning means accepting the risk that a mod will eat your save at the worst possible time.

There's an Apple guideline that logs go under ~/Library/Logs that Unity decided to follow and didn't really give their users like Squad much of a choice in the matter. Would be nice if they made it per-app, so I can keep my last KSP log around even if I run another Unity game, but that's Unity for you.

It was the first really solid plugin that allowed you to control a part's animations in the VAB. Since stock didn't do that until 0.25, Firespitter got popular. It also has the single-part mode-switching features that B9 and USI like.