Jump to content

NewtSoup

Members
 View Profile  See their activity

  • Posts

    532

  • Joined

  • Last visited

 Content Type 

Posts posted by NewtSoup

    Out Of Science! - Destination Duna

    in KSP1 Mission Reports

    Posted

    22 minutes ago, FleshJeb said:

    I appreciate your journeys through the tech tree—I always learn a few things, and it’s a mode I’m not willing to play.

    Will you be bringing the lander back to Kerbin?

    Will the Overkill get left in Kerbin orbit, or discarded?

    The lander may get left in Duna Orbit if dV is looking a little slim.  As for the Overkill - you'll have to wait and see.  My plan is to record certain sections rather than just screenshot.  So the launch of the core.  Maybe attaching one arm ( 4 would get tedious ) I'll screenshot a refuellling trip to save the snores.  Mostly I'm going to try and capture the interesting bits

    some of this depends on how frustrated I get with KDEnlive though :D  It seems to be quite powerful.  But also hard to use.

    Dammit Jim, I'm an actor, not a video editor!

    Out Of Science! - Destination Duna

    in KSP1 Mission Reports

    Posted

    Something I just learned in testing before actually launching and assembling:

    The arms made of a fuselage and girders and holding the solar panel array -

    First of all I put down a Docking Port, then I added a small adapter plate.  To that I attached the structural fuselage, then another adapter plate and then 3 girders and on the end of that another docking port.  The solar panels were attached to the girders.

    I then wanted to hide batteries and reaction wheels inside the fuselage so I plopped them onto the node available on the docking port at the end of the arm and used the movement arrows to slide them right down inside the tube.  All well and good!

    Except, once you have done that you can no longer use the docking port as a docking port.  It's node is of course occupied by the battery stack.   Glad I realised/confirmed in testing before I did the actual mission launch!  Time for a quick redesign.

    Out Of Science! - Destination Duna

    in KSP1 Mission Reports

    Posted · Edited by NewtSoup

    Hooray for struts and auto struts!  Hooray for Solar Panels.  Hooray for docking ports!  It's time to go to Duna! On this much Tech:

    GmQawey.png


     First of all A lander was designed that would be capable of landing on Duna and getting off the surface again.  Secondly a ship was designed that would be able to transport the lander to Duna ( and Ike ) and then get home again.  The key to doing this is the ability to assemble the ship in space and swap parts ( I do love my engine swapping ).  Though this will be trickier than usual with no RCS ability yet.

    Here is an Artists Impression of what the vessel will look like once it's fully assembled in LKO

    0AFIsUk.png

    Features:

    KSS Overkill:
    3800m/s dV
    0.39 TWR from 5 Terriers
    4 Krew - 2 Pilots, 1 Scientist, 1 Engineer

    Duna Lander:
    2200 m/s dV
    3.01 TWR from a single terrier
    2 Krew - 1 Pilot, 1 Scientist ( Away team from main krew )

    Because there were no extendable solar panels available I put loads of them on the arms which are made of girders and a structural fuselage.
    Each Arm is attached by a docking port to the core of the Overkill to facilitate assembly in orbit and provides external docking for the whole structure to allow refuelling.  The structural fuselages hide batteries and reaction wheels that provide almost enough torque to pull the ship apart :) 

    The ship has enough fuel to service the lander on an Ike landing ( maybe 2 ) while we're in the area and get into LDO and back to LKO with little to no air braking.  The main Krew compartments are the four re-entry pods which will be used to return the Krew to safety.  Thanks to the magic of auto-struts ( careful use of ) the vessel despite being made of way more tanks than it should be has some rigidity instead of flopping around like a fish on land.

    Out Of Science!

    in KSP1 Mission Reports

    Posted

    So my choices were as follows:

    Electrics - for solar panels 
    Miniaturization - for a docking port 
    Flight control for fins and an inline reaction wheel
    General Construction for STRUTS, FINALLY SOME RIGIDITY.

    My tree now looks like this:
     

    GmQawey.png

    Yeah.. Duna and Ike are going to be easy peasy!

     

    Out Of Science!

    in KSP1 Mission Reports

    Posted · Edited by NewtSoup

    So, a quick jolly to Minmus was in order as science points were in demand.  The cheese containers were primed.  The batteries were charged. The rocket was fuelled.  Batteries were feared to be the deciding factor in mission length as once the main engines were jettisoned and the ship was on terriers only, batteries would be the only source of power and must last.  After a quick "spin" through the lower atmosphere the onion was finally peeled leaving only the core.  This brought tears to the Krew's eyes but not too many.

    3SLFoLW.png

    An uneventful and undocumented hop through local space later Valentina settled the imaginatively named Science Ship II down on its landing tanks and then stood with Devis on the surface for the obligatory selfie.
    iLaCAWt.png

    After visit to 5 of Minmus' 8 biomes fuel in the lander war running low.  Battery power had lasted well however with judicious use of SAS and was at just under half capacity.  Although the return vehicle was replete with go juice and some could have been transferred to the lander the mission was to return to LKO before landing so it was decided to say farewell to the great cheese planes and minty mountains of Minmus and return to Kerbin.

    cjdiK4t.png

    Thanks to Valentina's fine piloting skills ( and not repeated reloads in LKO ) the ship was dropped within spitting ( well a short bus journey ) distance of the KSC.
    FKXk7jB.png

    hikaiui.png

    One last Selfie was in order to celebrate a safe return with no unplanned explosions.


    UkPsZDw.png

    With a haul of 290 precious science points bringing the total to 305 the mission was declared a resounding success.  Next stop.  Duna!  ( now that we can afford solar panels )

     

    Kerbal Behaviour

    in KSP1 Discussion

    Posted · Edited by Vanamonde

    5 hours ago, Lo Var Lachland said:

    With one hand or two? Sometimes the kerbals will "clap," which can be translated as a wave. 

    I might have been a clap which I caught out of the corner of my eye in the bottom right of the screen as their faces appeared.  I've never noticed the clap before either.

    [snip]

    Out Of Science!

    in KSP1 Mission Reports

    Posted

    Turns out those SRBs were producing some unwanted torque effects this time ( AKA rotating uncontrollably ) so It got changed to this:

    Sh5Hve1.png

    Same everything except the SRB's just boost together at full power whereas before the inner ones had a smaller max thrust to burn for longer and this time everything is pseudo onion staged.

    Out Of Science!

    in KSP1 Mission Reports

    Posted · Edited by NewtSoup

    Science Vessel II - The strut free version.  Also features no alternators on the terriers.

    However, dumping the Reliant engines in favour of Terriers upped the dV by over 1000.  This ship has ~8200 dV now.   Also changed fuel tanks for bigger ones and fewer of them, this does not affect the dV only the rigidity of the ship, still woeful though and no struts or autostruts.  Also removed the landing gear, now relying entirely on Landing Tanks!  Upped the battery capacity to 700.  Hopefully will be enough!.   I think the next electronics box really should be next on my purchase list.

    1XJBMUm.png

    Time to sample the finest cheeses of Minmus.

    Out Of Science!

    in KSP1 Mission Reports

    Posted

    This is a really interesting way to play.  With only 10% of the science rewards available the emphasis becomes on being able to get to more places to do what little science you can rather than maximising your science potential.

    I did a mun mission.  I did not document it as everyone has seen a mun mission.  I got 57 science whereas normally that would have been 570 and opened up a slection of around 5 6 boxes.  This time I could choose just one tier 3 box and so it was Advanced Rocketry for the Terrier and Thud Engines and the larger fuel tank which will help stop "concertina" behaviour in my ships. 

    I did not have enough science to get electrics.  I could have gone aviation and scavenged further points around Kerbin but this time, that is not the efficient way.  Better to extend my range and open up more space opportunity.

    Also - Pilots are much more useful now.  I can't just slap a probe on because I don't have the comms or electrics available.  So it's got to be krewed missions to keep the stability options open. 

    So now I have 7 tech boxes and I can think about going to minmus now.  Or at least exploring more biomes of the Mün.

    I wonder if I can do Duna on 7 boxes?

    Also learned.  Micro Landing struts are pointless.  Land on fuel tanks very gently or on girders.  You do not need all that bounce even when their sliders are  upped.  Micro struts are really only good for probes which you can't make at this low tech.

    Science Game Broken :( CTD when Kerbals EVA

    in KSP1 Technical Support (PC, modded installs)

    Posted

    New Test - build the same ship in sandbox hack into orbit

    And KRAKEN!  Any time SAS is on  Kerbals on EVA go really weird!.

    This must be mod related then and it must be because I updated a couple of mods to 1.5 when I'm on 1.45.

    I will update my game to 1.5 and retest  ( I actually have a 1.5 game ready in steam - I just kept a copy of 1.45 as that's where I was playing and modded for at the time )

    Science Game Broken :( CTD when Kerbals EVA

    in KSP1 Technical Support (PC, modded installs)

    Posted

    Nope it's my save file.  Happens any time I press R to activate the thruster pack on a scientist.

    BUT... Having just Reloadsd I activated the thruster pack on a scientist and it was fine.  

    What was different?  SAS was turned off.  I got the scientist back inside.  Turned SAS ON then EVA the scientist

    Presss Space to let go.  Press R and KRAKEN!

    So new theory - this is an SAS related bug and the reason it appeared to be just scientists was because when you EVA a pilot SAS turns off.

    New test - Reload and launch the ship with 2 pilots.

     

    Oh and it seems to have also bumped the Science Vessel into a solar orbit!

    New Theory confirmed

    Hacked Ship into Orbit with 2 Pilots

    EVA a pilot with SAS on the ship OFF.

    No Kraken

    EVA a pilot with SAS on the ship ON

    Kraken Present ( but hiding.  did not present until I touched the ship )

    Science Game Broken :( CTD when Kerbals EVA

    in KSP1 Technical Support (PC, modded installs)

    Posted

    I have rebuilt the ship from the ground up.

    Added 2  more parachutes and coaxed it into orbit with a little extra dV for over engineering's sake.

    Same Krew - Devis and Zelfrid.

    I think EVA Devis as a test..  Hit R - she gets pinged off the ship and her RCS fuel is empty!  Pretty much the same bug as before just without a crash.

    It must be Devis.  It's not the ship, it's not the game it's not the mods I apparently have a corrupt scientist.   I am going to try this in the same save file with a different Krew.

    Science Game Broken :( CTD when Kerbals EVA

    in KSP1 Technical Support (PC, modded installs)

    Posted · Edited by NewtSoup

    I am playing a game with 10% science rewards and I've hit an issue.  This suddenly started happening last night and I have no idea why.  I am running KSP 1.45

    The below save game has a ship in orbit ( of which Dr Evil would be proud! ) It has 2 Crew, A Pilot and a Scientist.

    When I EVA the Pilot everything is fine and works as normal.

    When I EVA the Scientist the game has a tendency, on pressing R to activate the RCS on her thruster pack,  to crash to desktop or make the universe vanish at which point the game crashes on loading a save game.

    I made it to the Mün and set down on the surface.

    I sent Devis the Scientist on an EVA - if she bangs her head she falls to the floor VERY fast and her EVA pack is suddenly empty.  Zelfrid the the Pilot is fine and everything behaves normally.

    I went back to a previous save game prior to launch and reloaded the ship and began the mission anew but the same thing is happening.

    This does not happen in my sandbox save using a similar ship and the exact same mods so I don't think it's mod related.

    Has anyone encountered this before and is there a way to fix it?



    My Save Game:
    https://drive.google.com/open?id=14xgDpkKj4cigwdm2u04DnIiif2ek6bS9

    CKAN of my mods:

    https://drive.google.com/open?id=1FYGAQSqI2W4V70w3Zig54fikMptamwGy

    Tail of ksp.log - appears to have pertinent information: 

     

     

     


    [LOG 19:32:01.672] Game State Saved to saves/10% Science Rewards/persistent
    [LOG 19:32:01.673] [AutoSave]: Game Backed Up and Saved
    [LOG 19:32:10.642] [FLIGHT GLOBALS]: Switching To Vessel Devis Kerman ---------------------- 
    [LOG 19:32:10.643] [PlanetariumCamera]: Focus: Devis Kerman
    [LOG 19:32:10.647] [12/12/2018 7:32:10 PM [x] Science!]: <Trace> (ShipStateWindow) - MapObjectSelected
    [LOG 19:32:10.647] [12/12/2018 7:32:10 PM [x] Science!]: <Trace> (ShipStateWindow) - Vessel
    [WRN 19:32:10.648] [Part]: kerbalEVAfemale (Devis Kerman) holds crew but has no interior model defined!
    [LOG 19:32:10.650] [BetterBurnTime] Vessel changed to Devis Kerman
    [LOG 19:32:10.651] 12/12/2018 7:32:10 PM,KerbalAlarmClock,Vessel Change from 'Science Ship I' to 'Devis Kerman'
    [LOG 19:32:10.665] 12/12/2018 7:32:10 PM,KerbalAlarmClock,Active Vessel changed - resetting inqueue flag
    [LOG 19:32:10.671] 12/12/2018 7:32:10 PM,KerbalAlarmClock,Removing DrawGUI from PostRender Queue
    [LOG 19:32:10.679] 12/12/2018 7:32:10 PM,KerbalAlarmClock,Adding DrawGUI to PostRender Queue
    [LOG 19:32:10.679] 12/12/2018 7:32:10 PM,KerbalAlarmClock,Skipping version check
    [LOG 19:32:14.474] recalculating orbit for mk1pod (Science Ship I): Kerbin ( Update mode TRACK_Phys )
    rPos: [672734.476872271, -29569.5377114697, -49764.6901030479]   rVel: [156.950279030908, -84.0198264608665, 2283.54463787945] |2290.47349570223|
    [LOG 19:32:14.474] recalculated orbit for mk1pod (Science Ship I): Sun ( UT: 306424.499399264 )
    rPos: [NaN, NaN, NaN]   rVel: [NaN, NaN, NaN] |NaN|
    Delta: [NaN, NaN, NaN] / [NaN, NaN, NaN]
    [LOG 19:32:14.475] [Progress Node Reached]: Flyby
    [LOG 19:32:14.475] [Progress Node Reached]: Sun
    [LOG 19:32:14.475] [Progress Node Complete]: Flyby
    [LOG 19:32:14.477] recalculating orbit for kerbalEVAfemale (Devis Kerman): Kerbin ( Update mode TRACK_Phys )
    rPos: [672734.559721796, -29564.5115633922, -49763.6845585864]   rVel: [157.251455719811, -84.0084336822492, 2283.42669197626] |2290.3761470303|
    [LOG 19:32:14.477] recalculated orbit for kerbalEVAfemale (Devis Kerman): Sun ( UT: 306424.499399264 )
    rPos: [NaN, NaN, NaN]   rVel: [NaN, NaN, NaN] |NaN|
    Delta: [NaN, NaN, NaN] / [NaN, NaN, NaN]
    [LOG 19:32:14.477] Look rotation viewing vector is zero
    [LOG 19:32:14.478] Look rotation viewing vector is zero
    [LOG 19:32:14.478] Look rotation viewing vector is zero
    [LOG 19:32:14.479] Kerbin: Resetting
    [ERR 19:32:14.487] Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "kerbalEVAfemale (Devis Kerman)/model01/female01/helmet01/helmetCollider"

    [ERR 19:32:14.487] Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "kerbalEVAfemale (Devis Kerman)/model01/female01/helmet01/helmetCollider"

    [ERR 19:32:14.487] Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "kerbalEVAfemale (Devis Kerman)/model01/jetpack01/jetpackCollider"

    [ERR 19:32:14.487] Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "kerbalEVAfemale (Devis Kerman)/model01/jetpack01/jetpackCollider"

    [LOG 19:32:14.498] Look rotation viewing vector is zero
    [LOG 19:32:14.498] Look rotation viewing vector is zero
    [LOG 19:32:14.498] Look rotation viewing vector is zero
    [LOG 19:32:14.500] setting new dominant body: Sun
    FlightGlobals.mainBody: Sun
    [LOG 19:32:14.500] Vessel mk1pod (Science Ship I) velocity resumed. Reference body: Sun vel: [NaN, NaN, NaN]
    [LOG 19:32:14.500] Vessel kerbalEVAfemale (Devis Kerman) velocity resumed. Reference body: Sun vel: [NaN, NaN, NaN]
    [LOG 19:32:14.500] Vessel parachuteRadial velocity resumed. Reference body: Sun vel: [NaN, NaN, NaN]
    [LOG 19:32:14.500] Vessel parachuteRadial velocity resumed. Reference body: Sun vel: [NaN, NaN, NaN]
    [LOG 19:32:14.500] Vessel mk1pod velocity resumed. Reference body: Sun vel: [NaN, NaN, NaN]
    [LOG 19:32:14.500] Vessel ServiceBay.125 velocity resumed. Reference body: Kerbin vel: [NaN, NaN, NaN]
    [LOG 19:32:14.500] Vessel Decoupler.1 velocity resumed. Reference body: Kerbin vel: [NaN, NaN, NaN]
    [LOG 19:32:14.500] Vessel fuelTankSmallFlat velocity resumed. Reference body: Sun vel: [NaN, NaN, NaN]
    [LOG 19:32:14.500] Vessel fuelTankSmall velocity resumed. Reference body: Sun vel: [180732223815680, 268899312467968, 10170482556928]
    [LOG 19:32:14.500] Vessel Decoupler.1 velocity resumed. Reference body: Sun vel: [NaN, NaN, NaN]
    [LOG 19:32:14.504] [F: 58179]: kerbalEVAfemale (Devis Kerman) collided into mk1pod (Science Ship I) - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.504] kerbalEVAfemale (Devis Kerman) Exploded!! - blast awesomeness: 0
    [LOG 19:32:14.506] [kerbalEVAfemale (Devis Kerman)]: Deactivated
    [LOG 19:32:14.519] [F: 58179]: kerbalEVAfemale (Devis Kerman) collided into mk1pod - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.519] [F: 58179]: kerbalEVAfemale (Devis Kerman) collided into mk1pod - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.519] [F: 58179]: kerbalEVAfemale (Devis Kerman) collided into Decoupler.1 - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.520] [F: 58179]: kerbalEVAfemale (Devis Kerman) collided into Decoupler.1 - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.520] [F: 58179]: kerbalEVAfemale (Devis Kerman) collided into Decoupler.1 - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.520] [F: 58179]: kerbalEVAfemale (Devis Kerman) collided into Decoupler.1 - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.520] [F: 58179]: kerbalEVAfemale (Devis Kerman) collided into Decoupler.1 - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.520] [F: 58179]: kerbalEVAfemale (Devis Kerman) collided into Decoupler.1 - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.520] [F: 58179]: kerbalEVAfemale (Devis Kerman) collided into Decoupler.1 - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.521] [F: 58179]: kerbalEVAfemale (Devis Kerman) collided into Decoupler.1 - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.521] [F: 58179]: kerbalEVAfemale (Devis Kerman) collided into fuelTankSmallFlat - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.521] [F: 58179]: kerbalEVAfemale (Devis Kerman) collided into fuelTankSmallFlat - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.521] [F: 58179]: kerbalEVAfemale (Devis Kerman) collided into liquidEngine2 - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.521] [F: 58179]: kerbalEVAfemale (Devis Kerman) collided into liquidEngine2 - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.522] [F: 58179]: Decoupler.1 collided into ServiceBay.125 - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.522] Decoupler.1 Exploded!! - blast awesomeness: 0.5
    [LOG 19:32:14.522] [Decoupler.1]: Deactivated
    [LOG 19:32:14.538] recalculating orbit for ServiceBay.125: Kerbin ( Update mode TRACK_Phys )
    rPos: [672737.518461446, -29572.8806462069, -49723.3500106012]   rVel: [NaN, NaN, NaN] |NaN|
    [LOG 19:32:14.538] recalculated orbit for ServiceBay.125: Sun ( UT: 306424.539399264 )
    rPos: [NaN, NaN, NaN]   rVel: [NaN, NaN, NaN] |NaN|
    Delta: [NaN, NaN, NaN] / [NaN, NaN, NaN]
    [LOG 19:32:14.538] Look rotation viewing vector is zero
    [LOG 19:32:14.538] Look rotation viewing vector is zero
    [LOG 19:32:14.538] Look rotation viewing vector is zero
    [LOG 19:32:14.539] Look rotation viewing vector is zero
    [LOG 19:32:14.539] Look rotation viewing vector is zero
    [ERR 19:32:14.540] Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "miniLandingLeg/model/miniLeg/PistonCap/leg/leg_collider"

    [ERR 19:32:14.540] Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "miniLandingLeg/model/miniLeg/PistonCap/PistonCapCollider"

    [ERR 19:32:14.540] Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "miniLandingLeg/model/miniLeg/PistonCap/leg/leg_collider"

    [ERR 19:32:14.540] Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "miniLandingLeg/model/miniLeg/PistonCap/PistonCapCollider"

    [ERR 19:32:14.540] Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "miniLandingLeg/model/miniLeg/PistonCap/leg/leg_collider"

    [ERR 19:32:14.540] Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "miniLandingLeg/model/miniLeg/PistonCap/PistonCapCollider"

    [ERR 19:32:14.540] Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "miniLandingLeg/model/miniLeg/PistonCap/leg/leg_collider"

    [ERR 19:32:14.540] Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "miniLandingLeg/model/miniLeg/PistonCap/PistonCapCollider"

    [LOG 19:32:14.542] [F: 58179]: miniLandingLeg collided into fuelTankSmall - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.542] miniLandingLeg Exploded!! - blast awesomeness: 0
    [LOG 19:32:14.542] [miniLandingLeg]: Deactivated
    [LOG 19:32:14.544] [F: 58179]: mk1pod collided into miniLandingLeg - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.544] mk1pod Exploded!! - blast awesomeness: 0.5
    [LOG 19:32:14.544] [mk1pod]: Deactivated
    [LOG 19:32:14.544] [F: 58179]: miniLandingLeg collided into fuelTankSmallFlat - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.544] miniLandingLeg Exploded!! - blast awesomeness: 0
    [LOG 19:32:14.544] [miniLandingLeg]: Deactivated
    [LOG 19:32:14.545] [F: 58179]: miniLandingLeg collided into Decoupler.1 - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.545] miniLandingLeg Exploded!! - blast awesomeness: 0
    [LOG 19:32:14.545] [miniLandingLeg]: Deactivated
    [LOG 19:32:14.546] [F: 58179]: GooExperiment collided into mk1pod (Science Ship I) - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.546] GooExperiment Exploded!! - blast awesomeness: 0.5
    [LOG 19:32:14.546] [GooExperiment]: Deactivated
    [LOG 19:32:14.546] [F: 58179]: miniLandingLeg collided into mk1pod (Science Ship I) - relative velocity: NaN - impact momentum: NaN
    [LOG 19:32:14.546] miniLandingLeg Exploded!! - blast awesomeness: 0
    [LOG 19:32:14.546] [miniLandingLeg]: Deactivated
    [LOG 19:32:14.552] Look rotation viewing vector is zero
    [LOG 19:32:14.552] Look rotation viewing vector is zero
    [LOG 19:32:14.552] Look rotation viewing vector is zero
    [ERR 19:32:14.553] Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "ServiceBay.125/model/Squad/Parts/Utility/ServiceBay/ServiceBay_125(Clone)/untitled/Service01/cargo/TrussMount/Door01/Cylinder_003"

    [ERR 19:32:14.553] Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "ServiceBay.125/model/Squad/Parts/Utility/ServiceBay/ServiceBay_125(Clone)/untitled/Service01/cargo/TrussMount/Door01/Cylinder_004"

    [ERR 19:32:14.553] Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "ServiceBay.125/model/Squad/Parts/Utility/ServiceBay/ServiceBay_125(Clone)/untitled/Service01/cargo/TrussMount/Door2/Cylinder_009"

    [ERR 19:32:14.553] Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "ServiceBay.125/model/Squad/Parts/Utility/ServiceBay/ServiceBay_125(Clone)/untitled/Service01/cargo/TrussMount/Door2/Cylinder_010"

    [ERR 19:32:14.553] Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "ServiceBay.125/model/Squad/Parts/Utility/ServiceBay/ServiceBay_125(Clone)/untitled/Service01/cargo/TrussMount/Door3/Cylinder_011"

    [ERR 19:32:14.553] Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "ServiceBay.125/model/Squad/Parts/Utility/ServiceBay/ServiceBay_125(Clone)/untitled/Service01/cargo/TrussMount/Door3/Cylinder_012"

    [ERR 19:32:14.553] Infinity or NaN floating point numbers appear when calculating the transform matrix for a Collider. Scene hierarchy path "ServiceBay.125/model/Squad/Parts/Utility/ServiceBay/ServiceBay_125(Clone)/untitled/Service01/cargo/TrussMount/Door4/Cylinder_005"

     

    Out Of Science!

    in KSP1 Mission Reports

    Posted

    Quick test in Sandbox and I think I will go for the nose cone. 
    Hammer SRB 4 basic fins and an OKTO reaches 12,292 meters
    Hammer SRB 4 basic fins and and OKTO with an aerodynamic nose cone reaches 15,134 meters
    With a flea and the same setup the nose cone was detrimental to max alt, but that was because it didn't have enough power to go transonic.
    Once you're into transonic speeds ( and when pushing through the sound barrier ) the nose cone really pays off it seems.

    Out Of Science!

    in KSP1 Mission Reports

    Posted

    Thank you for the info.  I will resist looking it up though in case it turns out to be a bit of a "walkthrough" for me.  I'm currently trying to work out how I can land on the Mün with just those 3 tech boxes.  I'm not sure I can but I can now afford General Rocketry and have a more powerful main engine.  OR I could take stability and have a radial decoupler, a nose cone and a new fin!.  Choices choices!  I may have to take the roller out for another spin to get both.

    Out Of Science!

    in KSP1 Mission Reports

    Posted · Edited by NewtSoup

    She's a little squirly low down, and in the mid atmosphere, and higher up to be quite honest.  I gets far to boring after 3rd stage separation though.  Just a bit standard really.  I'm not sure I'll be able to land on the Müm with just this tech. Well, Land, yes.. get home, probably not.

    Out Of Science!

    in KSP1 Mission Reports

    Posted · Edited by NewtSoup

     

    I want the next bit to be a separate post and not combined with the original :D

    Aha.. and so after waiting long enough I can post the next video.   Just for giggles and because I'm going to need the science I decided to see if I could get to the Mün on just  3 tech boxes.  I was completely optimistic from the outset and an no point did I blow up on the launchpad, randomly deconstruct or fall out of the sky.

    I proudly present the "Kraken Tempter"

    Craft file available on request! (I'm sure she'll be very popular )
     

     

    Out Of Science!

    in KSP1 Mission Reports

    Posted · Edited by NewtSoup

    I decided to start a new game, I will continue my "Going Mostlywhere" but I've not been well again and just felt like starting over.  To make things interesting I decided to turn off reverts, make Kerbals not respawn and play on 10% of the science rewards!.  I decided to not make it career though.  The idea is that I won't simply finish the tree on Mun, Minmus and Duna and that I'll have to work harder and more creatively to get to where I want to go and earn those oh so scrumptious science points ( this should make the lab actually useful too ).

    Early game though I hit a snag.  Pretty much Out of Science as the title says.  Time to stop being "standard" and think a way  to get more science when you  have no rover and just a 2 boxes along the science line.
     

     

     

     

    My First Mod - Chihuahua Engine - Help needed.

    in KSP1 Mods Discussions

    Posted

    1 minute ago, wasml said:

    The documentation does list the parameters available for tweaking but unfortunately has very few descriptions as to what they actually do. A place to go to look for likely looking names when trying to accomplish something or just poking around - provides clues but doesn't answer many questions directly. In my experience creating things for KSP consists of experimenting as you've been doing, looking at other's projects, and asking question here on the forums.

    I had indeed noticed that in the docs - "Yes, I can see the name of that, but what does it do?" :D

    My First Mod - Chihuahua Engine - Help needed.

    in KSP1 Mods Discussions

    Posted

    2 hours ago, wasml said:

    I think the reason you had trouble replacing the rcs model with the terrier model is due to the baked in thrust transform names. The rcs "thrusterTransformName = RCSthruster" vs "thrustVectorTransformName = thrustTransform" in the Terrier confg. The fairing is also  part of the model - not sure if renaming the fairing mesh name to something that's not in the model would cause it to disappear, not be jettisonable,  or if it would cause the entire part not to load. You might check the doc's page and see if it's possible to set it as jettisoned when created - try searching on "ModuleJettison". Good luck with your mod(s).

    Thank you.  I suspected it might be something along those lines as the fairing appeared spontaneously.  But there was nothing to indicated what was going on.  In time I will get through the documentation.

    For now I'm happy I have the functionality I wanted.  

    In time I will get the model I want ( the terrier was not specifically what I was after either ) and the particle effects I want.

×
×
  • Create New...