rgr

@Raptor831 i have been using ckan versions of RF/RP and i tried fiddling with the configs on and off, also with the standalone pkgs, with mixed results. the dependency/install system of ckan does not like it and has a hard time getting its head around these two(four) packs living next to each other with RF/SA + RP only, i was getting 3 phantoms, but after the RFSA 3.2.3 update, only the RT-5 Flea remains problematic in stock. good

this happens with realfuel 12.0(SA 3.2.2) and RP 10.5.1(SC 0.11.2): phantom plumes on (clockwise) swivel, spark, Dawn, LVN trimodal, twitch, ant, skipper

if you are interested in an apollo type fuel cell, i made one as a MM

Line-of-Sight being a strong contender

FOD - Foreign Object Damage RT - Remote Tech (mod) F5 - ... F5 (for safety) MAL - Minimum Ambient Lighting (mod) ALA - Ambient Lighting Adjustment (mod) CTT - Community Tech Tree (mod) DRE - Deadly Re-entry (mod) FF - Final Frontier (mod) KJR - Kerbal Joint Reinforcement (mod) dCoM - dry CoM fpm - feet per minute DOA - Dead on Arrival SECO - Second-stage Engine Cut-Off sep - Separation

what would it require for this mod to be able to switch reference to things like the celestial plane or equatorials of focused/other bodies? (that would really help in map view)

This applies if you are using RealFuels mod. And only when without RealismOverhaul mod. In that case, the file is located in kspdir/GameData/RealFuels/ Any other extension than .cfg is going to be ignored by KSP/ModuleManager on load.

they are massively overfueled by RealFuels. it's done in a global RF patch RealFuels/zSolidFuelMult.cfg you can rename that file and RSB will be back to normal. The fuel "number" still changes, because RF modifies the resource stats, but the weight and burn time are right. RF Stockalike then takes care for other supported parts. Unsupported solidfuel parts may loose their performance, though. RealFuels still breaks some RSB parts (like the Common Centaur Stage), by ripping out the tanks and not placing right modular volumes back in. This might be fixed in RO, but I'm not currently running that though.

adapter parts for connecting other tank types would really help so far I managed to cheat it with a radial attachment point, that makes an additional bottom node on the tank but it needs alignment/positioning and looks a bit strange like this on the rockomax tank with RL10 and the delta II interstage:

the spacedock 1.0.10-2467 link/file is broken. well, may be the spacedock CDN being itchy. it needs a while for different locations to settle i guess.

The Undervalued "Root Mode" in RemoteTech Are you confused that a ground dish of the size of a whole rocket cannot communicate with the nearest moon? Do you find standard Remote Tech too challenging, but like the line-of-sight logic? Looking for a gameplay twist? Want bragging rights to claim playing KSP w/RT? Welcome to Root Mode. In essence, it calculates antenna ranges based on their combined performance (optionally their count). A stronger antenna on one end will "boost" (gain) the range of the weaker one. It's details and calculations with the base RangeMultiplier are well documented, I'll try to show you what else it enables you to do for your gameplay. With the exposure of the RT configs in the UI, it is now easier to activate and offers a whole range of difficulty scaling. And if you are playing a RSS or any other scale mode, you will love it. Example 1. Stock RT with lower RangeMultiplier (0.333) What this does, it "opens" up the hard cap of the standard mode, but in a more stricter way than the 0.5 modifier, while two identical antennas still maintain 90% of their "nominal" range. You can kick off your Keosynchronous satellite network (~3.0Mm) up with the VR-2 omni, a single 88 dish can put omnis on Mun and KSC can almost reach to a medium dish around Duna (10-20Gm). Also more antenna/relay combos are possible for other planets. Circles designate LKO/KSO/Munar/Gigameter ranges. A green value means the gain is hard capped by the "root flat max" limit. Example 2. RSS RSS is big. So big, that you need a lot of ground stations beyond KSC just to start, and still be out of touch almost half the time. Root mode really comes into play as it gives the 'deep space' a meaning again. The recommended multiplier (0.5) is too much here, considering the massive range of real dishes - the small 500km reflectron could be picked up at GPS orbit by the DSN Note: RT in RSS doesn't seem to change ground station range when rm is used. Values between 0.1-0.333 start to make sense, depending on decisions like if you want to reach the Moon with omnis or not. Let's take rm=0.15 Here circles go LEO+/GSO/Moon/Mars. Jupiter would be 800+Gm. Numerous, but short range yellow stations now greatly expand ground contact coverage for big antennas up to the Moon. Green stations can lock omnis at synchronous orbits and narrow-beam dishes can, at moments, easily call home from the inner planets. There is an additional config value allowing combined effect of multiple omnis, but its implementation seems to be a little unclear github #594. But that would be really helpful in spacecraft pairing at these lower rm values, as 2 antennas only reach a performance of ~54%. But you win some, you loose some. It takes a bit of tweaking to find what suits you, but all in all, it makes RT to be much more than it seemed to be. I went from RT to AntennaRange, but with Root Mode, back to RT. Take a look at it P.S. the spreadsheet is based on a very useful one I grabbed once from RT or RO posts, but don't remember where, anymore.

RSS ground station colors (supplied by Real Solar System mod): Yellow - Mm range (106, high orbit) Red - Gm range (109, avg. Venus, partial inner solar system coverage) Green - Gm/low Tm range (1012, avg. Jupiter coverage, partial outer solar system coverage) Blue - high Tm range - (1014, full solar system coverage - DeepSpace Network) Note: actually there are 3 blue nodes, but the "DSS 63 Madrid" node is masked by adjacent/higher up green "DSA 2 - Cebreros" station

well the idea was sorting and filtering what's really available

RO/RF engine data info? I parsed this engine sheet (google docs) out of my MM cache, but it's polluted and dirty, so before wasting more effort on it... Can I find a better (and/or curated) list of the engine numbers which come with RO?

that "input-field-onchange-auto-sort" thing needs to get addressed when updating starts again ;P unless you paste the whole value, each digit typed shuffles the row order - but cursor doesn't follow the edited field, it stays on the same row (which is a different value by that time). also x-axis dashes would be appreciated... but it's already a great help for modding w/o unity.

(1.0.5) it actually looks as if without CoreHeat the `TemperatureModifier` in ResourceConverter is ignored? No heat shows up anywhere during conversion regardless of the value. Using CoreHeat, I was able to build this LH/LOX Fuel Cell (inspired by the Apollo cells) though: It has an electrical 'Heater' to start it up (bring it up to 470K) - this couldn't be done in flight, the electrolyte was prepared before launch. at that point the cell will start producing roughly 50% output and continue to rise to 99% efficiency at 500K. The heater can be modified to prevent the cell from stopping (leave it on, w/temp.modifier cutoff after 470K) - this was the actual operation mode For testing, it will help push the cell, up to 530K with decreasing efficiency, when the core shuts down - the cell was only to run at 470-500K setting actual CoreHeat values is still a mystery for me (what factor, what units?? relations to temp debug??), I made it heat up the part by a mild 10kW @ full power the heater input, cell output and tanks are arbitrary. LH/LOX/water ratios do reflect the specs. MODULE { name = ModuleResourceConverter ConverterName = Fuel Cell StartActionName = Start Fuel Cell StopActionName = Stop Fuel Cell FillAmount = 0.95 AutoShutdown = true GeneratesHeat = true UseSpecializationBonus = false DefaultShutoffTemp = 0.9 INPUT_RESOURCE { ResourceName = LqdHydrogen Ratio = 0.000074405 FlowMode = STAGE_PRIORITY_FLOW } INPUT_RESOURCE { ResourceName = LqdOxygen Ratio = 0.000044092 FlowMode = STAGE_PRIORITY_FLOW } OUTPUT_RESOURCE { ResourceName = ElectricCharge Ratio = 1.5 DumpExcess = false // shape cell load with power demand } OUTPUT_RESOURCE { ResourceName = Water Ratio = 0.0001184 DumpExcess = true } TemperatureModifier { key = 370 0 // 220F - electrolyte solidifies key = 420 1 key = 470 1000 // 385F - critical temperature, cell start key = 500 10 // 440F - peak power output temp key = 600 0 } ThermalEfficiency { key = 370 0 0 0 key = 420 0.01 0 0.005 key = 470 0.4 0.015 0.01 key = 500 1 0 0 key = 600 0 0 0 } } RESOURCE { name = LqdHydrogen amount = 50 maxAmount = 50 } RESOURCE { name = LqdOxygen amount = 32 maxAmount = 32 } RESOURCE { name = Water amount = 0 maxAmount = 4 } MODULE { name = ModuleResourceConverter ConverterName = Cell Heater StartActionName = Start Heater StopActionName = Stop Heater AutoShutdown = true GeneratesHeat = true DefaultShutoffTemp = 0.9 ThermalEfficiency = 1 TemperatureModifier { key = 0 5000 0 0 key = 300 1000 0 0 key = 471 1000 0 0 key = 652 0 -20 0 } INPUT_RESOURCE { ResourceName = ElectricCharge Ratio = 0.1 FlowMode = STAGE_PRIORITY_FLOW } } MODULE { name = ModuleOverheatDisplay // show Core Temp in menu } MODULE { name = ModuleCoreHeat CoreTempGoal = 480 CoreToPartRatio = 0.1 CoreTempGoalAdjustment = 10 CoreEnergyMultiplier = 0.1 HeatRadiantMultiplier = 0.01 CoolingRadiantMultiplier = 0.5 HeatTransferMultiplier = 0.5 CoolantTransferMultiplier = 0.01 radiatorCoolingFactor = 1 radiatorHeatingFactor = 0.01 MaxCalculationWarp = 1000 CoreShutdownTemp = 530 MaxCoolant = 100 } Insights? Comments? what's wrong with this Heat POC?

the Fuel Cell too op? The cell is insanely hungry and powerful. At a rate of 16ECs it pumps out roughly 300kEC in just over 5 hours with the "packaged" fuel. Besides it's moved to an early tech node with Community Tech Tree, and it's too much surge for those crafts. In fact it eliminates battery buffering. in fact it's comparable to the massive liquid fuel stock Fuel Cell Array at 18 ECs, which comes four tech nodes later.

I have been encountering some more strange interactions with that SAS, but I need to pinpoint it on a clean install first. thanks for picking it up anyway.

I also tried adding ReservePower to Procedural Tanks in RO (... when less parts is more) This MM patch seems to work (for the specified 'servicemodule' type)

if anyone wonders why testflight keeps forgetting it's settings, create GameData\TestFlight\Plugins\PluginData folder. After that, I found out it'll be fixed in the 1.6 (1.1only) release...

I've been comparing this to Fusebox, which is the old champ; looking for a more advanced electrical sim. You seem to be going in the right way Small bug: ampyear does not account for other planet systems - time is calculated in standard-scale kerbin days (throws 4x day estimates in 24h mods like 64k). a hard-coded constant maybe? Feature/bug: the metering/calculation does not change when the source is shut off (via resource panel), but neither does it in fusebox. It's a definition thing, but you can switch on SAS/RCS via ampyear - they light up on the navball - which is not possible in a powered down module by regular R+T keys. So I lean on the bug side Also note that ampyear doesn't let fusebox know it's drawing power (manager's 0.017). It adds up in resource panels, so I guess it's not detectable by fusebox for some reason. that might be a fusebox thing but, just saying... Meanwhile I'll prepare some feature request (like inverters, load, cool/heat, buses, breakers)

How does 64k change "science body limits"? I was rather surprised to complete the high-orbit contract only above 4,000km otherwise you make the game great(er)