Apricot

I don't think 0.9.0.1 would be a suitable version name. Too many commits, including Bop rotation fix for Principia. I am afraid upgrading silently would break some existing games.

I have JNSQ and Principia installed. The ship was on a trans-munar injection trajectory, soon will entering Mun's SOI. Mun perigee was ~20km (principia calculated). I didn't notice what patched conics looked like.

This mod makes my in-game flight performance jitters every second. Is there a timer that triggers every second doing a lot of computation?

Totally. That's what this mod achieves. I was just complaining about stock CommNet behavior.

This mod rocks! The stock behavior tends to prefer fewer hops to stronger signal or Kerbalism data rates, which is quite annoying for Kerbalism science transmission. Sometimes a LKO vessel at the backside is reluctant to connect through local KSO relays, it instead relays through Mun with very weak signal just because it takes only one less hop! Maybe we can advertise this mod to the Kerbalism team?

Some engines like LV-45 seeme updated and named differently (liquidEngine2 => liquidEngine2_v2) in KSP 1.12. Needs configurations.

This works brilliantly. Thank you so much!

My KSC is floating after a game crash. Creating new games or reinstalling JNSQ/Kopernicus won't fix the problem. I don't have rescaling mods installed.

Quite a few parts of BDB still goes into the wrong node. For example, MOS-DOTD-F2 Fixed solar arrays goes into "survivability". Any plan to improve this?

I also came into this problem. Just update R-T-B Kronometer patch and it should work. Btw, new JNSQ release when?

RealFuels says However I can use the default tank (not "highy pressurized") for RCS to work, as long as I configure them to use Aerozine50 instead of Hydrazine. I think RCS are OP compared to "Propulsion Systems" small engines, which suffers from ullage and most are pressure fed. Is this intended? Also RealFuels says that RCS should be configured to type "L" for RCS-specific multipiers. The "HotGasThruster-M" and "L" engines however are configured to "O" instead.

StnSciExperiment2.cfg titled #autoLOC_expPrograde_title which is "Experiment: Prograde Kuarqs" in English localization. exper02ProgradeKuarqs.cfg in ArcanumIndustries dir also titled "Experiment: Prograde Kuarqs"

I also came into contract issues. Contract generator (StnSciContract.cs) generates contract for "Experiment: Seed Growth" (/GameData/StationScience/Parts/StnSciExperiment1.cfg). However this part is not avaible at all in the tech tree (idk why). There is another part called "Experiment: Plant Growth" (/GameData/StationScience/ArcanumIndustries/Parts/exper01PlantGrowth.cfg) available instead. These two parts are definitely not the same part. Thus the contract cannot be completed. I think many others running into "Kuarqs" might share the same issue, because the Kuarqs experiment parts happen to be named the same in (/GameData/StationScience/Parts/) and in (/GameData/StationScience/ArcanumIndustries/Parts/). @linuxgurugamerPTAL.

I'm afraid changing the value would affect all users. Vessel mass will decrease and delta-v increase on existing vessels. From my limited experiments in Kerbal-Mun-Minus system, I would say that JNSQ + current version of RealFuel is the hardest. Mass proportion of tanks (Dry mass : Wet mass ratio, not accounting engine) takes up over the stock 1:9 for most types of propellant. Low-density high-Isp propellants (especially LH2+LO2) are counter-productive. The current config (0.00015) needs 150kg tank per 1m^3 propellant, LH2 is less than 100kg/m^3 dense. Single stage delta-v is limited With a staging ratio (m_upperstage / m_everything) of 1:6, Isp = 300s, propellant density = 1t/m^3, we can achieve only 4km/s for an infinite heavy stage. In fact, 3km/s is already too heavy. (RIP Falcon 9) This is on par with real-life difficulty early days (3.5 stage Vostok), not a great experience for gaming, huh? JNSQ + stock (including Restock+, or other stockalike) engines/fuels is modest difficulty. JNSQ is designed for that. JNSQ + 0.000016 RealFuel, easier than JNSQ + stock parts. With 1.25m parts, I achieved 2.5 stages for minimal crewed launch(1.5t), 3 stages (3rd stage is RCS) for a minimal Mun lander probe (300kg). Stock world + stock engine is OP, everyone agrees. Stock world + current version of RealFuel, not tried this yet, but it should be the same that LH2+LO2 is no-go. Stock world + 0.000016 probably too easy, 6km/s dv can do a lot of fancy things. Besides JNSQ, I also have Principia, FAR, RealHeat, and Kerbalism, TETRIX tech tree (for uncrewed probe early-game) installed, which might affect rocket design and tech planning. Conclusion: current difficulty is acceptable, though not very entertaining for JNSQ. The fact that LH2+LO2 is the worst propellant really annoys.

I removed those two blocks, falling back to 0.000016 RealFuels default. In JNSQ world, this enables 2STO for LKO crew cabs (5000m/s), 3STO huge rockets for crewed Mun mission or deep space probe/landers, and makes LH2/LO2 upper stage a feasible option. Now Isp matters more than propellant density. I suggest JNSQ players removing these two blocks for better realism/experience.

// set drymass of all RealFuels configured tanks dependent on max volume @PART[*]:HAS[@MODULE[ModuleFuelTanks]:HAS[#type[Default]]]:AFTER[RealFuels] { @MODULE[ModuleFuelTanks] { %basemass = volume * 0.00015 } } @PART[*]:HAS[@MODULE[ModuleFuelTanks]:HAS[#type[Cryogenic]]]:AFTER[RealFuels] { @MODULE[ModuleFuelTanks] { %basemass = volume * 0.00015 } } This 0.00015 multiplier makes low-density propellant such as liquid hydrogen (LH2) completely useless, as the dry mass takes up more than half the wet mass. Any thought on this?

I think this mod is OP for Kerbalism. All other orbital science (such as DMagic Orbital Science mod) takes days to finish and only gives a few points when complete, with strict situation restrictions. Kdex takes no time to finish, gives too much science points in nearly all situations and biomes.

Hiring back a dismissed kerbanaut (same name) results in exceptions: [ERR 20:13:41.529] Exception handling event OnApplicantHired in class EarnYourStripes:System.ArgumentException: An item with the same key has already been added. Key: Ceri Kerman at System.Collections.Generic.Dictionary`2[TKey,TValue].TryInsert (TKey key, TValue value, System.Collections.Generic.InsertionBehavior behavior) [0x000c1] in <ad04dee02e7e4a85a1299c7ee81c79f6>:0 at System.Collections.Generic.Dictionary`2[TKey,TValue].Add (TKey key, TValue value) [0x00000] in <ad04dee02e7e4a85a1299c7ee81c79f6>:0 at EarnYourStripes.EarnYourStripes.OnCrewHire (ProtoCrewMember p, System.Int32 numberOfEmployees) [0x00020] in <fb7693575ef84126a7b0413b6cf42436>:0 at EventData`2[T,U].Fire (T data0, U data1) [0x000b0] in <2afc64dea36946459d4707808bdac511>:0 [EXC 20:13:41.533] ArgumentException: An item with the same key has already been added. Key: Ceri Kerman System.Collections.Generic.Dictionary`2[TKey,TValue].TryInsert (TKey key, TValue value, System.Collections.Generic.InsertionBehavior behavior) (at <ad04dee02e7e4a85a1299c7ee81c79f6>:0) System.Collections.Generic.Dictionary`2[TKey,TValue].Add (TKey key, TValue value) (at <ad04dee02e7e4a85a1299c7ee81c79f6>:0) EarnYourStripes.EarnYourStripes.OnCrewHire (ProtoCrewMember p, System.Int32 numberOfEmployees) (at <fb7693575ef84126a7b0413b6cf42436>:0) EventData`2[T,U].Fire (T data0, U data1) (at <2afc64dea36946459d4707808bdac511>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:LogException(Exception) EventData`2:Fire(ProtoCrewMember, Int32) KerbalRoster:HireApplicant(ProtoCrewMember) KSP.UI.Screens.AstronautComplex:HireRecruit(UIList, UIList, UIListItem) KSP.UI.Screens.AstronautComplex:Vbutton(ButtonTypes, CrewListItem) UnityEngine.Events.UnityEvent`2:Invoke(ButtonTypes, CrewListItem) KSP.UI.CrewListItem:<Awake>b__28_0() UnityEngine.Events.UnityEvent:Invoke() KSP.UI.UIStateButton:<Awake>b__24_0() UnityEngine.EventSystems.EventSystem:Update()

Corvus command pod is unlocked in Flight Control. This is imbalanced.

Player.log: https://gist.github.com/apricot-azumi/e4da301fcc24b8a4ce1e7212d7edb1fb Principia log: https://gist.github.com/apricot-azumi/aec4ffd9ff4cf84a02e9050d467fe0c6 The vessel to deploy is named "Test" in case it leads to confusion. It seems Principia crashed during KSTS adding parts to the vessel.

I suspect that this mod is incompatible with Principia. The game crashes when a vessel deployment completes. Nothing special in KSP.log stderr.log prints this line when the game crashes: F0323 02:55:05.782352 3372 plugin.cpp:1601] Check failed: inserted part_id: 0 Principia Gödel with KSP 1.11.1 KSTS 2.0.1.7 I am ready to help if more info is needed.