ebigunso

I really miss those LE-7 engines I had way back on 1.2.2, so I request ROEngines to include engines from the mod "Forgotten Real Engines" as well.

@taniwha Thanks, I'll try that out.

How can I stop FAR from automatically bringing up the menu every time I stage?

Now that I'm used to RO, I can't get myself to go back to stock, since it's too easy XD

If you're going to use RO, I reccomend copying the install elsewhere since Steam automatic update will mess with your install a LOT.

I heard engine groups were for independent throttle control by groups, but I can't figure how I'd be doing that in flight. Is there a newly assigned key to press to cycle through the groups or something?

I found the cause. It was my very stupid mistake. I have multiple installs of RO, and I was editing files in the wrong install. No wonder it didn't get applied. Oops. Case closed.

I'm trying to add Test Flight configs to RO engines that doesn't have them yet, and have succeeded in one, but my second attempt using almost the same MM patch has failed for some reason. Here is the MM patch in question: @PART[*]:HAS[@MODULE[ModuleEngineConfigs]:HAS[@CONFIG[RD-56]],!MODULE[TestFlightInterop]]:BEFORE[zTestFlight] { TESTFLIGHT { name = RD-56 ratedBurnTime = 800 ignitionReliabilityStart = 0.95 ignitionReliabilityEnd = 0.98 ignitionDynPresFailMultiplier = 0.1 cycleReliabilityStart = 0.93 cycleReliabilityEnd = 0.98 } } @PART[*]:HAS[@MODULE[ModuleEngineConfigs]:HAS[@CONFIG[KVD-1]],!MODULE[TestFlightInterop]]:BEFORE[zTestFlight] { TESTFLIGHT { name = KVD-1 ratedBurnTime = 800 ignitionReliabilityStart = 0.95 ignitionReliabilityEnd = 0.98 ignitionDynPresFailMultiplier = 0.1 cycleReliabilityStart = 0.93 cycleReliabilityEnd = 0.98 } } @PART[*]:HAS[@MODULE[ModuleEngineConfigs]:HAS[@CONFIG[CE-7.5]],!MODULE[TestFlightInterop]]:BEFORE[zTestFlight] { TESTFLIGHT { name = CE-7.5 ratedBurnTime = 720 ignitionReliabilityStart = 0.95 ignitionReliabilityEnd = 0.98 ignitionDynPresFailMultiplier = 0.1 cycleReliabilityStart = 0.93 cycleReliabilityEnd = 0.98 } } The engine I succeeded in adding a Test Flight config was the Vikas engine, which I was able to add a config for Vikas-1, Vikas-1+, Vikas-2, and Vikas-2B varients of the engine. The MM patch is basically the same except the name and rated burn time fields. I don't see why this would work in one but not another. Can anyone point out to me what I'm doing wrong here? EDIT: The only major difference I noticed with the original engine config I was patching, was that the Vikas used ModuleEngines, and KVD-1 used ModuleEnginesFX. Would this cause the issue?

I was messing around with Hyperedit on a craft that was about to decay according to Orbital Decay manager. Being in the flight screen for that craft past it's "supposed to decay" time seemed to have plagued my Orbital Decay plugin with NaN. I see "Time Until Decay: NaN" for that craft and every other craft I launch after. I want to go in my save files to edit out the NaNs so Orbital Decay could regenerate proper values for them again, but I don't know where to look. Can I get some advice on this matter?

Hi. I have a little feature request that could make the experience smoother. Filter results by launch site latitude. Add a box to have the user input the launch site's latitude, and FF could filter out results that require starting orbit inclinations lower than what is achievable from that latitude.

@Kerbas_ad_astra Hi. I want to know if your branch has any known incompatibilities with KSP 1.3.1. I want to use this mod along with RO.

Thank you! I've got the files.

I want to have KCT in my RO game on KSP 1.3.1. I looked at the previous pages and on p.129 I found related posts, but I can't find this build 39 thing that was being mentioned there. Is it not on the Github releases? Because I only see build 38 and then it jumps to the latest. Where can I find this build 39 file?

Does the latest texture pack work with RSS v12.0? Or do I need the latest RSS as well? If so, does it have any known incompatibilities with KSP v1.2.2?

@Nightside Quite late but I just tried it out. I bumped the value up just slightly from the default by 0.5 each, and it's working well. Thanks for the tip!

@Nightside Thanks! I currently don't have my desktop PC at hand so it'll be next week that I try this out. Seems very promising though.

@Nightside Ohhhh, thanks. That looks promising. Which file should I look in to find that entry?

So, is there any mod that tones down the reentry effect's starting conditions, so I don't get fiery launches but still get fiery reentries? It just doesn't look right to have flames showing on screen while not having any heat issues on the craft at all.

I noticed that the total decay rate shown in the Manager window is inconsistent with the rates shown in the Breakdown Display. The screenshot below is of a probe orbiting the Moon in RSS. As you can see in the screenshot, the Manager shows the value for Radiation Pressure Decay only and ignores the Gravitational Effect decay rate. I use v1.5.4 from ZAJC3W (Thanks!) on KSP 1.2.2 with RO.

Alright then. Looks like I'll have to wait on this mod until RO is 1.3 compatible. Thanks anyways!

Does the latest version with the Kopernicus fix work with 1.2.2 as well? If not, how should I manually include the fix into the older version of this mod? I want to use this with Realism Overhaul which the latest is currently on 1.2.2.

So, KCT removed it's simulation function and has moved it to the KRASH mod. Can the "no failures in simulation" function be applied to this mod too? If not atm, I request this to be implemented for the next release.

Oh, great news somebody has already come up with a fix. Is there a way I can manually implement this fix into my local install?

On the flight engineer readouts, the current stage Dv reads 0 when the stage's engine is firing. Otherwise it shows correct values. I use Realism Overhaul, and KSP 1.2.2. Has this happened to anybody else, and is there a fix?

@ElWanderer Thanks! I guess that was what I was looking for.