Jump to content

Sir_Fanch

Members
  • Posts

    44
  • Joined

  • Last visited

Posts posted by Sir_Fanch

  1. I would suggest both RealChute and StageRecovery, AFAIK they are both currently working, but I haven't loaded up my KSP in a couple of weeks. RealChute will give you modifiable parachutes and far more options of deployment, and StageRecovery will tell you roughly the touchdown speed of a stage if the parachutes are deployed correctly (NOTE: If you're burning your parachutes up it is most likely you are deploying them too early, when the air density is too little for them too work, but high enough that friction with the air molecules causes the re-entry burning). Hope I've been able to help :)

    Edit: Also maybe for future reference I would hazard a guess that this isn't the perfect place for your question, this section is for Add-on Releases, you may want to try Add-on Discussion or the reddit page instead :) 

    Edit2: Should also be noted that StageRecovery has other functionality to it that you may want to fully read before trying it out. (auto recovering stages, etc)

  2. 1 hour ago, Guswut said:

    Tell me if you see anything that looks out of place as far as the orbits go.

    I'm afraid I'm not familiar enough with the KBO's or minor moons to make that kind of call, although the only one that jumped out at me was, as you mentioned, pluto's satellites immediately looked strange, but 2 months ago I wasn't aware Pluto had satellites, or that it was a binary system, so there's that :P. I'm just excited to have all the stuff in the right place finally so that I can use it, although someone mentioned earlier in the thread that some of the satellites in this mod had SOI's smaller than the planet they were associated, so were basically useless (as you couldn't orbit or land on them), so that might be something that needs addressing also, although I have no idea how to check that, short of trying to orbit all of the bodies.

    Anyway, great work on the patches mate, thoroughly appreciate it :D

  3. 18 hours ago, Whitecat106 said:

    Orbital Decay should work fine

    I second this, I've had some slight problems with it (certain test payloads not lasting quite as long as they did in real life, such as vanguard-1 which was more due to the way it maps surface area IIRC) but on the whole my test payloads have decayed at pretty close to the real life decay date, Whitecat has done fantastic work :P.

  4. On 28/07/2016 at 7:35 PM, SyzygyΣE said:

    the orbit itself does not change at all

     

    1 hour ago, h0yer said:

    before it just stopped decaying stuff

    1.1.3 added an option to stock KSP to 'freeze' orbits (to stop the orbit wobble bug), it's activated by default and needs to be de-activated for Orbital Decay to work AFAIK. I'm not 100% on the name or location of the option but it's in the options of the main menu. Sorry if this doesn't help, both of those sound like problems with that though just from a quick glance and I thought there might be a small chance you could fix your games quickly :P.

  5. On 28/07/2016 at 4:14 PM, MockingBird said:

    I am looking to incorporate TestFlight and RP-0 into the configs. However I've not actually played with either of them yet so havent really had chance to get my head around the config layout for them. If anyone has any pointers?

    Wish I could help, but it's a little out of my ballpark. Perhaps @NathanKell could help? Having a limit on burn time is actually surprisingly fun to work around haha.

    P.S. Sorry if the tag is bothersome, I'm not particularly familiar with the forum etiquette yet :P.

  6. @Phineas Freak Yeh I figured as much, I remember reading somewhere that KCT was removing simulations also so I thought I'd check just in case. Generally it isn't too huge of a deal, but if I'm testing a design that uses engine clusters the chances of one of them failing is pretty high, generally the flight isn't ruined from a single engine failure, but my testing of launch profiles and rocket performance definitely is :P. Anyways, thanks for the info, you're a great help as always mate :).

  7. Anyone have a decent alternative to KCT for running simulations without TestFlight failing parts? Love the mod, but I'm playing a no revert game, and kinda need to know how a rocket will perform if everything goes right, simulating a launch 5 times because the same engine failed get's tedious and rather time consuming given most of the time it's an engine I've not flown and so the failure rate is through the roof while simulating. Or is there a way to manually temporarily disable part failures?

  8. I'm playing an RP-0/RO install, and I'm wondering if anyone has a fix for the "Disable Part Failures" button not working, I'm playing without reverts and sims are kinda essential, but simulating the same launch 5 times because an engine keeps failing is a little annoying. Anyone know how to get it working again with the latest TestFlight (assuming that's what it was made for), or failing that anyone got an alternative they use they could point out :P

  9. Always on the look-out for more RO engine parts :D. These look awesome, totally agree this would be perfect to mix with Forgotten Real Engines, only need to decide who has the better Rutherford :P. Great work on the mod! Will definitely be adding this to my install :), love little lightweight insertion engines :D. Is TestFlight configs all this needs for RP-0?

  10. 16 hours ago, Friedrich Nietzsche said:

    Is there a way to use this mod without it messing up the inclinations?

    Really?

    On 09/07/2016 at 8:32 PM, ClLaw said:

    Which config file do you delete to change the inclinations back?

    On 09/07/2016 at 9:21 PM, Phineas Freak said:

     

    @ClLaw it is the "000-RSSPatches.cfg" file.

     

    Come now, 4 posts up isn't that far to go :P

     

    Also would I be correct in assuming this mod is most likely no longer being developed by the OP of this thread? Or am I missing updates elsewhere?

  11. 4 hours ago, Ravenchant said:

    We can make a duplicate part with MM and write separate configs so both capsules will be represented.

    Exactly what I was thinking. I can certainly see the value in the larger one, have more like a return craft instead of just a return pod, if that makes any sense :P. I wrote a config for the RO-RCS on the capsule, it should apply it only if RO-RCS is installed (pretty unlikely because I'm terrible at coding and this is literally my first patch), but it works AFAIK and I think the values should work somewhat well for both the large and small versions (untested), if you wouldn't mind having a look @Ravenchant, I'm fairly certain there's probably a lot of errors, I grabbed parts of it from the RO-RCS global config and tried changing it for just the parachute part.

    Spoiler

    @PART[SampleReturnCapsule_Parachute]:NEEDS[RP-0]
    {
        MODULE
        {
            name = ModuleAvionics
            massLimit = 0.5
        }
    }
    @PART[SampleReturnCapsule_Parachute]:FOR[RO-RCS]
    {
        MODULE
        {
            name = ModuleEngineConfigs
            type = ModuleRCS
            thrustRating = thrusterPower
            techLevel = 0
            minTechLevel = 0
            origTechLevel = 2
            engineType = L
            configuration = Hydrazine
            modded = false
            CONFIG
            {
                name = HTP
                PROPELLANT
                {
                    ratio = 1.0
                    name = HTP
                }
                IspSL = 0.177
                IspV = 0.465
                cost = -1
                entryCost = 7500
                techRequired = stability
            }
            CONFIG
            {
                name = Hydrazine
                PROPELLANT
                {
                    ratio = 1.0
                    name = Hydrazine
                }
                IspSL = 0.274
                IspV = 0.72
                cost = 0
                entryCost = 10000
                techRequired = stability
            }
            CONFIG
            {
                name = NitrousOxide
                PROPELLANT
                {
                    ratio = 1.0
                    name = NitrousOxide
                }
                IspSL = 0.2
                IspV = 0.525
                cost = -5
                entryCost = 5000
                techRequired = basicRocketry
            }
            CONFIG
            {
                name = Helium
                PROPELLANT
                {
                    ratio = 1.0
                    name = Helium
                }
                IspSL = 0.203
                IspV = 0.453
                cost = 0
                entryCost = 5000
                techRequired = engineering101
            }
            CONFIG
            {
                name = Nitrogen
                PROPELLANT
                {
                    ratio = 1.0
                    name = Nitrogen
                }
                cost = -10
                IspSL = 0.1001462
                IspV = 0.195
            }
            CONFIG
            {
                name = MMH+NTO
                PROPELLANT
                {
                    name = MMH
                    ratio = 0.5
                    DrawGauge = True
                }
                PROPELLANT
                {
                    name = NTO
                    ratio = 0.50
                }
                IspSL = 0.362
                IspV = 0.952
                cost = 30
                techRequired = flightControl
                entryCost = 30000
            }
            CONFIG
            {
                name = UDMH+NTO
                PROPELLANT
                {
                    name = UDMH
                    ratio = 0.413
                    DrawGauge = True
                }
                PROPELLANT
                {
                    name = NTO
                    ratio = 0.587
                }
                IspSL = 0.361
                IspV = 0.943
                cost = 25
                entryCost = 25000
                techRequired = flightControl
            }
            CONFIG
            {
                name = Aerozine50+NTO
                PROPELLANT
                {
                    name = Aerozine50
                    ratio = 0.502
                    DrawGauge = True
                }
                PROPELLANT
                {
                    name = NTO
                    ratio = 0.498
                }
                IspSL = 0.366
                IspV = 0.955
                cost = 30
                entryCost = 30000
                techRequired = flightControl
            }
            CONFIG
            {
                name = Cavea-B
                PROPELLANT
                {
                    ratio = 1.0
                    name = CaveaB
                }
                IspSL = 0.274
                IspV = 0.939
                cost = 30
                entryCost = 40000
                techRequired = heavyRocketry
            }
        }
    }

    @PART[SampleReturnCapsule_Parachute]:HAS[useRcsMass[True]]:FOR[RO-RCS]
    {
        @MODULE[ModuleEngineConfigs]
        {
            %origMass = #$../mass$
        }
        !useRcsMass = DELETE
    }

    @PART[SampleReturnCapsule_Parachute]:FOR[RO-RCS]
    {
        @MODULE[ModuleEngineConfigs]
        {
            @CONFIG[HTP]
            {
                %thrusterPower = 0.06375
                @cost *= 0.25
            }
            @CONFIG[Hydrazine]
            {
                %thrusterPower = 0.06875
                @cost *= 0.25
            }
            @CONFIG[NitrousOxide]
            {
                %thrusterPower = 0.059
                @cost *= 0.25
            }
            @CONFIG[Helium]
            {
                %thrusterPower = 0.018
                @cost *= 0.25
            }
            @CONFIG[Nitrogen]
            {
                %thrusterPower = 0.0285
                @cost *= 0.25
            }
            @CONFIG[MMH*NTO]
            {
                %thrusterPower = 0.11125
                @cost *= 0.25
            }
            @CONFIG[UDMH*NTO]
            {
                %thrusterPower = 0.1105
                @cost *= 0.25
            }
            @CONFIG[Aerozine50+NTO]
            {
                %thrusterPower = 0.11375
                @cost *= 0.25
            }
            @CONFIG[Cavea-B]
            {
                %thrusterPower = 0.10625
                @cost *= 0.25
            }
        }
    }

    @PART[SampleReturnCapsule_Parachute]:HAS[useRcsCostMult[*]]:AFTER[RO-RCS]
    {
        @MODULE[ModuleEngineConfigs]
        {
            @CONFIG,*
            {
                @cost *= #$../useRcsCostMult$
            }
        }
    }

    @PART[SampleReturnCapsule_Parachute]:HAS[@MODULE[ModuleEngineConfigs]:HAS[#type[ModuleRCS*]],!MODULE[ModuleRCS*]]:AFTER[RO-RCS]
    {
        @MODULE[ModuleEngineConfigs]
        {
            @type = ModuleEngines
            @CONFIG,*
            {
                %maxThrust = #$thrusterPower$
                %minThrust = #$thrusterPower$
                !thrusterPower = DEL
            }
        }
    }
    @PART[SampleReturnCapsule_Parachute]:HAS[useRcsCostMult[*]]:AFTER[RO-RCS]
    {
        !useRcsCostMult = DEL
    }
     

    I've started tweaking your config to balance out a smaller one (corona sized) as well, but you'd probably do a far better job (with a lot less effort :P) than I could, let me know if you want to see it though for reference or something, happy to be any help I can be. 

     

    EDIT: Had a thought, does anything need to be done to allow ship manifest to transfer science into the command part? Or does ship manifest just automatically do that for all parts with the command module?

×
×
  • Create New...