Jump to content

[1.12.5] TechTrees: QUARTIX 3.7, TETRIX 2.23, SIMPLEX 1.33


theJesuit

Recommended Posts

4 minutes ago, Vl3d said:

For Simplex, yes. Currently the first decoupler is radial, so we can only build boosters + one stage. In practice this means that we end up with SSTO type rockets in orbit at the start of the game, instead of small satellites (upper stages are not possible).

I always maintained you can kerbalise it.  Break rockets up using the probe cores.  But also the heatshields can be ejected, so these could be used as pre-decouplers too.

I MAY  revisit this due to my thinking around Quartix though.  But it won't be till the summer break.

Link to comment
Share on other sites

  • 3 weeks later...
  • 4 months later...

Small updated coming as I move some of the bahaEPL parts.

I've also been working on a small set of truss with tank parts using the UbioWelder i want to add these in as an alternate to how I use Near Future Construction.  These will be in a different Simplex mod, but I'm not sure which one yet.

Link to comment
Share on other sites

  • 4 weeks later...

Query regarding the TETRIX tree: Is there a reason the LV-TX87 is in Very Heavy Rocketry instead of Heavy Rocketry with its upper-stage counterpart? a 1.8m first stage engine seems very out of place in there with all the 3.75+ monsters.

Link to comment
Share on other sites

4 hours ago, ussdefiant said:

Query regarding the TETRIX tree: Is there a reason the LV-TX87 is in Very Heavy Rocketry instead of Heavy Rocketry with its upper-stage counterpart? a 1.8m first stage engine seems very out of place in there with all the 3.75+ monsters.

Yup.  It was a balance thing based on as I never really played with them.  But with the QUARTIX tree then I placed them before the 2.5 and now I have had a playthrough of that tree with the ReStock equivalents, I am sold on moving them back to a more appropriate level.

Check for an update in the next few days  

Link to comment
Share on other sites

  • 3 weeks later...
  • 1 month later...

Looks like there's a small bug where the patch "AngleCanMods/SIMPLEXTechTree/SIMPLEXTechTree-KerbalismConfig/@PART[FuelCell]:NEEDS[ProfileDefault]:FOR[KerbalismDefault]" is using FOR instead of NEEDS, causing other mods to trigger kerbalism patches.

Just need to change it to NEEDS[ProfileDefault,KerbalismDefault], if that's the intended behavior at least

Link to comment
Share on other sites

  • 3 weeks later...
On 8/14/2023 at 8:43 AM, Rodger said:

Looks like there's a small bug where the patch "AngleCanMods/SIMPLEXTechTree/SIMPLEXTechTree-KerbalismConfig/@PART[FuelCell]:NEEDS[ProfileDefault]:FOR[KerbalismDefault]" is using FOR instead of NEEDS, causing other mods to trigger kerbalism patches.

Just need to change it to NEEDS[ProfileDefault,KerbalismDefault], if that's the intended behavior at least

Fixed in 3.32 update.  Thank you!  

Also, all three have been updated to include the inline parachutes with SIMPLEX Station Parts, and also WaterDrinker prop engines.

Peace.

Link to comment
Share on other sites

  • 4 weeks later...

So, working up my current Quartix save, I think that the Ground Anchor works better in the engineering branch with the Ground Tether rather than in the Construction branch with the docking ports.  

This means it is a more natural progression with landing legs in the Engineering branch and would be in the same node as the Grabber.

I also think that i may allow a cross from the construction to engineering branch to potentially skip the landing legs if you want.

So that will be a Quartix only update to 3.5.

 

Link to comment
Share on other sites

QUARTIX Tech Tree updated to 3.6 - 

Changelog 3.6

  • moved Ground Anchor to composites (engineering branch)
  • composites Node can be researched from specialisedConstruction OR specialisedEngineering
  • differentialVolumeContainment only needs one previous node to unlock
  • advancedMotors only needs one previous node to unlock
Link to comment
Share on other sites

  • 3 weeks later...

I am seeing some odd tech tree placement in Tetrix and Quatrix. This might be because of my mod list, but I've kept it pretty lean when it comes to part mods.

 

Quatrix:

-TAC-LS 2.5m Life Support Supplies parts are listed under Heavy Rocketry

-Double C Seismic Accelerometer is listed twice (Advanced Rocketry and Advanced Electronics)

-Kerbal Planetary Base Systems K&K X1000 Storage parts are listed under Advanced Rocketry

-Kerbal Planetary Base Systems K&K Docking Port is listed under Unmanned Tech

 

Tetrix:

-TAC-LS 2.5m Life Support Supplies parts are listed under Heavy Rocketry

-Double C Seismic Accelerometer is listed under Advanced Rocketry

 

player.log

https://1drv.ms/u/s!AtJ0gZSLiapDh8ROZ00GUi-ejswQiQ?e=AAPpze

MMPatch.log

https://1drv.ms/u/s!AtJ0gZSLiapDh8RPzlT4y-BgUPMIDw?e=q29zzA

 

(I am aware of the AnglecanProgression / contract configuration errors and will post those in the other thread.)

Edited by Mitokandria
Link to comment
Share on other sites

5 hours ago, Mitokandria said:

TAC-LS 2.5m Life Support Supplies parts are listed under Heavy Rocketry

-Double C Seismic Accelerometer is listed twice (Advanced Rocketry and Advanced Electronics)

-Kerbal Planetary Base Systems K&K X1000 Storage parts are listed under Advanced Rocketry

-Kerbal Planetary Base Systems K&K Docking Port is listed under Unmanned Tech

Hi.  Quartix only has a small number of mods supported,  but the accelerometer listed twice is definitly an issue.  KPBSS is  a big mod to bring over, but i can have a look.

6 hours ago, Mitokandria said:

TAC-LS 2.5m Life Support Supplies parts are listed under Heavy Rocketry

-Double C Seismic Accelerometer is listed under Advanced Rocketry

 

I've never supported TAC-LS but i could add it in. The accelerometer is in this place as it is a science part derived from seeing acceleation from vibrating rockets from the logic of the placement, and allows a science part to be in that branch.  

I'll have a look at the issues over the next few days possibly.  

Link to comment
Share on other sites

35 minutes ago, theJesuit said:

Hi.  Quartix only has a small number of mods supported,  but the accelerometer listed twice is definitly an issue.  KPBSS is  a big mod to bring over, but i can have a look.

I've never supported TAC-LS but i could add it in. The accelerometer is in this place as it is a science part derived from seeing acceleation from vibrating rockets from the logic of the placement, and allows a science part to be in that branch.  

I'll have a look at the issues over the next few days possibly.  

Thanks. I've been "shopping around" for life support mods to replace Kerbalism and TAC-LS so far has been my go-to.  Is there a LS mod that would work better with Quatrix or Tetrix?

Link to comment
Share on other sites

1 hour ago, Mitokandria said:

Thanks. I've been "shopping around" for life support mods to replace Kerbalism and TAC-LS so far has been my go-to.  Is there a LS mod that would work better with Quatrix or Tetrix

I think i suggirt IFI-LS in Tetrix, but I might look at supporting Snacks with Simplex Resources in the near future that will have Air and Consumables.

Link to comment
Share on other sites

  • 3 weeks later...

Hello, so I'm building a new KSRSS+TETRIX install right now but some of the parts mods I want to use aren't supported. I'm about to try and put together some extra custom configs to place them on the tech tree for my own personal use and I was wondering if you (or anyone else) might want them for TETRIX proper once I'm done so you don't ever have to go through the trouble of supporting those mods yourself. The mods I'm looking to add support configs for are: Ablative-Airbrake, Bumblebee, CryoEngines Extensions, Heat Control, Kerbal Reusability Expansion, Missing Robotics, Near Future Aeronautics, and Supplementary Electric Engines.

Link to comment
Share on other sites

35 minutes ago, SpudNutimus said:

Hello, so I'm building a new KSRSS+TETRIX install right now but some of the parts mods I want to use aren't supported. I'm about to try and put together some extra custom configs to place them on the tech tree for my own personal use and I was wondering if you (or anyone else) might want them for TETRIX proper once I'm done so you don't ever have to go through the trouble of supporting those mods yourself. The mods I'm looking to add support configs for are: Ablative-Airbrake, Bumblebee, CryoEngines Extensions, Heat Control, Kerbal Reusability Expansion, Missing Robotics, Near Future Aeronautics, and Supplementary Electric Engines.

I'd love to add them if you want to share the config.  Thanks!

Link to comment
Share on other sites

23 hours ago, theJesuit said:

I'd love to add them if you want to share the config.  Thanks!

Alright, here's the config. It includes TETRIX support for:

- Ablative-Airbrake

- Bumblebee

- CryoEngines Extensions

- Heat Control

- Kerbal Reusability Expansion

- Missing Robotics

- Near Future Aeronautics

- Supplementary Electric Engines

Spoiler

//    SpudNutimus put together these mod support configs for theJesuit's ANGLECAN TETRIX Technology Tree.
//    ============================================================
//    *** Ablative-Airbrake

    @PART[AblativeAirbrake]:NEEDS[Ablative-Airbrake]
        {    @TechRequired = specializedControl
        }

//    ============================================================
//    *** Bumblebee

    @PART[bb_Aeroshell]:NEEDS[Bumblebee]
        {    @TechRequired = heavyAerodynamics
        }
    @PART[bb_Chute]:NEEDS[Bumblebee]
        {    @TechRequired = advancedEngineering
        }
    @PART[bb_Core]:NEEDS[Bumblebee]
        {    @TechRequired = advUnmanned
        }
    @PART[bb_Decoupler]:NEEDS[Bumblebee]
        {    @TechRequired = advConstruction
        }
    @PART[bb_Drogue]:NEEDS[Bumblebee]
        {    @TechRequired = advancedEngineering
        }
    @PART[bb_HGA]:NEEDS[Bumblebee]
        {    @TechRequired = advUnmanned
        }
    @PART[bb_Prop]:NEEDS[Bumblebee]
        {    @TechRequired = aviation
        }
    @PART[bb_PropSingle]:NEEDS[Bumblebee]
        {    @TechRequired = aviation
        }
    @PART[bb_RTG]:NEEDS[Bumblebee]
        {    @TechRequired = nuclearElectrics
        }
    @PART[bb_Seismometer]:NEEDS[Bumblebee]
        {    @TechRequired = electronics
        }
    @PART[bb_Sensor]:NEEDS[Bumblebee]
        {    @TechRequired = automation
        }
    @PART[bb_SingleTruss]:NEEDS[Bumblebee]
        {    @TechRequired = aviation
        }
    @PART[bb_Skids]:NEEDS[Bumblebee]
        {    @TechRequired = generalEngineering
        }
    @PART[bb_Truss]:NEEDS[Bumblebee]
        {    @TechRequired = aviation
        }
    @PART[bb_Dunaprop]:NEEDS[Bumblebee]
        {    @TechRequired = highAltitudeFlight
        }

//    ============================================================
//    *** CryoEngines Extensions

    @PART[CEX_LMO_Owl]:NEEDS[CryoEnginesExtensions]
        {    @TechRequired = heavyRocketry
        }
    @PART[CEX_LMO_Shikra]:NEEDS[CryoEnginesExtensions]
        {    @TechRequired = heavyRocketry
        }
    @PART[CEX_LMS_Achillo]:NEEDS[CryoEnginesExtensions]
        {    @TechRequired = heavyRocketry
        }
    @PART[CEX_LMS_Carnotaurus]:NEEDS[CryoEnginesExtensions]
        {    @TechRequired = veryHeavyRocketry
        }
    @PART[CEX_LMS_Therizino]:NEEDS[CryoEnginesExtensions]
        {    @TechRequired = veryHeavyRocketry
        }
    @PART[CEX_LMS_Yiqi]:NEEDS[CryoEnginesExtensions]
        {    @TechRequired = advRocketry
        }
    @PART[CEX_LHD_Hestia]:NEEDS[CryoEnginesExtensions]
        {    @TechRequired = precisionPropulsion
        }
    @PART[CEX_LHL_Aso]:NEEDS[CryoEnginesExtensions]
        {    @TechRequired = appliedAerospaceTech
        }
    @PART[CEX_LHL_Datun]:NEEDS[CryoEnginesExtensions]
        {    @TechRequired = heavyRocketry
        }
    @PART[CEX_LHL_Karakuni]:NEEDS[CryoEnginesExtensions]
        {    @TechRequired = heavierRocketry
        }
    @PART[CEX_LHL_Kunlun]:NEEDS[CryoEnginesExtensions]
        {    @TechRequired = aerospaceTech
        }

//    ============================================================
//    *** Heat Control

    @PART[radiator-conformal-1]:NEEDS[HeatControl]
        {    @TechRequired = composites
        }
    @PART[radiator-conformal-2]:NEEDS[HeatControl]
        {    @TechRequired = metaMaterials
        }
    @PART[radiator-conformal-3]:NEEDS[HeatControl]
        {    @TechRequired = microGeeFabrictaion
        }
    @PART[radiator-universal-1]:NEEDS[HeatControl]
        {    @TechRequired = metaMaterials
        }
    @PART[radiator-universal-2]:NEEDS[HeatControl]
        {    @TechRequired = microGeeFabrictaion
        }
    @PART[radiator-universal-3]:NEEDS[HeatControl]
        {    @TechRequired = microGeeFabrictaion
        }
    @PART[radiator-fixed-1]:NEEDS[HeatControl]
        {    @TechRequired = metaMaterials
        }
    @PART[radiator-fixed-2]:NEEDS[HeatControl]
        {    @TechRequired = composites
        }
    @PART[radiator-fixed-3]:NEEDS[HeatControl]
        {    @TechRequired = microGeeFabrictaion
        }
    @PART[radiator-fixed-4]:NEEDS[HeatControl]
        {    @TechRequired = quantumEngineering
        }
    @PART[radiator-microchannel-1]:NEEDS[HeatControl]
        {    @TechRequired = quantumEngineering
        }
    @PART[radiator-microchannel-2]:NEEDS[HeatControl]
        {    @TechRequired = quantumEngineering
        }
    @PART[radiator-microchannel-fixed-1]:NEEDS[HeatControl]
        {    @TechRequired = quantumEngineering
        }
    @PART[radiator-microchannel-fixed-2]:NEEDS[HeatControl]
        {    @TechRequired = quantumEngineering
        }
    @PART[radiator-surface-25-1]:NEEDS[HeatControl]
        {    @TechRequired = metaMaterials
        }
    @PART[radiator-surface-125-1]:NEEDS[HeatControl]
        {    @TechRequired = composites
        }
    @PART[radiator-surface-375-1]:NEEDS[HeatControl]
        {    @TechRequired = microGeeFabrictaion
        }
    @PART[heat-exchanger-25-1]:NEEDS[HeatControl]
        {    @TechRequired = metaMaterials
        }
    @PART[heat-exchanger-125-1]:NEEDS[HeatControl]
        {    @TechRequired = composites
        }

//    ============================================================
//    *** Kerbal Reusability Expansion

    @PART[KRE-AeroLeg-L]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = experimentalEngineering
        }
    @PART[KRE-AeroLeg-M]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = nanolathing
        }
    @PART[BoosterWingKRE]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = heavierAerodynamics
        }
    @PART[BoosterWingsMountKRE]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = heavierAerodynamics
        }
    @PART[HotGasThruster-L]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = actuators
        }
    @PART[HotGasThruster-M]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = specializedControl
        }
    @PART[CapsuleDockingPort1]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = advMetalworks
        }
    @PART[SmallCapsuleEngine]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = precisionPropulsion
        }
    @PART[SmallCapsuleEngineRCS]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = precisionPropulsion
        }
    @PART[DragonFuelTank]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = largeVolumeContainment
        }
    @PART[Grid?Fin?L]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = actuators
        }
    @PART[Grid?Fin?M]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = specializedControl
        }
    @PART[Grid?Fin?S]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = advFlightControl
        }
    @PART[Grid?Fin?L?Titanium]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = actuators
        }
    @PART[Grid?Fin?M?Titanium]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = specializedControl
        }
    @PART[Grid?Fin?S?Titanium]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = advFlightControl
        }
    @PART[Heatshield-M]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = specializedConstruction
        }
    @PART[KRE-HexLegsMountL]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = experimentalEngineering
        }
    @PART[KRE-HexLegsMountM]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = nanolathing
        }
    @PART[KRE-HexLegsL]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = experimentalEngineering
        }
    @PART[KRE-HexLegsM]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = nanolathing
        }
    @PART[KRE-ShepardLeg-M]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = miniaturization
        }
    @PART[KRE-ShepardLeg-S]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = specializedEngineering
        }
    @PART[KRE-FalconLeg-L]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = experimentalEngineering
        }
    @PART[KRE-FalconLeg-M]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = nanolathing
        }
    @PART[KRE-FalconLeg-S]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = miniaturization
        }
    @PART[KRE-FalconLegMk2-L]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = experimentalEngineering
        }
    @PART[KRE-FalconLegMk2-M]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = nanolathing
        }
    @PART[TrunkServiceModule]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = heavyAerodynamics
        }
    @PART[TrunkFin]:NEEDS[KerbalReusabilityExpansion]
        {    @TechRequired = aerodynamicSystems
        }

//    ============================================================
//    *** Missing Robotics

    @PART[DC_Arm_arm]:NEEDS[Missing_robotics]
        {    @TechRequired = composites
        }
    @PART[DC_Arm_arm2]:NEEDS[Missing_robotics]
        {    @TechRequired = composites
        }
    @PART[DC_Arm_arm3]:NEEDS[Missing_robotics]
        {    @TechRequired = composites
        }
    @PART[DC_Arm_rotor]:NEEDS[Missing_robotics]
        {    @TechRequired = actuators
        }
    @PART[DC_Arm_turn]:NEEDS[Missing_robotics]
        {    @TechRequired = actuators
        }
    @PART[DC_Arm_turn_02]:NEEDS[Missing_robotics]
        {    @TechRequired = actuators
        }
    @PART[DC_doorhinge_2m]:NEEDS[Missing_robotics]
        {    @TechRequired = actuators
        }
    @PART[DC_doorhinge_0075m]:NEEDS[Missing_robotics]
        {    @TechRequired = advConstruction
        }
    @PART[DC_doorhinge_075m]:NEEDS[Missing_robotics]
        {    @TechRequired = actuators
        }
    @PART[DC_GANTRY_01]:NEEDS[Missing_robotics]
        {    @TechRequired = specializedConstruction
        }
    @PART[DC_GANTRY_01_2X]:NEEDS[Missing_robotics]
        {    @TechRequired = specializedConstruction
        }
    @PART[DC_GANTRY_02_2Xs]:NEEDS[Missing_robotics]
        {    @TechRequired = advConstruction
        }
    @PART[DC_GANTRY_02s]:NEEDS[Missing_robotics]
        {    @TechRequired = advConstruction
        }
    @PART[DC_GANTRY_03_2Xs]:NEEDS[Missing_robotics]
        {    @TechRequired = advMetalworks
        }
    @PART[DC_Pivot_01]:NEEDS[Missing_robotics]
        {    @TechRequired = actuators
        }

//    ============================================================
//    *** Near Future Aeronautics

    @PART[nfa-atomic-jet-25-1]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = nuclearRocketry
        }
    @PART[nfa-atomic-multimode-25-1]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = nuclearRocketry
        }
    @PART[nfa-turbofan-25-1]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = highAltitudeFlight
        }
    @PART[nfa-turbofan-25-2]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = enduranceFlight
        }
    @PART[nfa-turbojet-25-1]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = hypersonicFlight
        }
    @PART[nfa-liftfan-10-1]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = hypersonicFlight
        }
    @PART[nfa-liftfan-25-1]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = highAltitudeFlight
        }
    @PART[nfa-liftfan-375-1]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = enduranceFlight
        }
    @PART[nfa-multimodal-25-1]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = appliedAerospaceTech
        }
    @PART[nfa-multimodal-25-2]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = aerospaceTech
        }
    @PART[nfa-multimodal-125-1]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = appliedAerospaceTech
        }
    @PART[nfa-propfan-125-1]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = supersonicFlight
        }
    @PART[nfa-turboprop-125-1]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = highAltitudeFlight
        }
    @PART[nfa-vtol-125-1]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = hypersonicFlight
        }
    @PART[nfa-vtol-0625-1]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = enduranceFlight
        }
    @PART[nfa-enginecooler-25-1]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = hypersonicFlight
        }
    @PART[nfa-enginenacelle-25-1]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = supersonicFlight
        }
    @PART[nfa-enginenacelle-25-2]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = supersonicFlight
        }
    @PART[nfa-enginepod-1]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = highAltitudeFlight
        }
    @PART[nfa-enginepod-2]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = enduranceFlight
        }
    @PART[nfa-enginepod-large-1]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = hypersonicFlight
        }
    @PART[nfa-fueltank-25-1]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = largeVolumeContainment
        }
    @PART[nfa-fueltank-25-2]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = largeVolumeContainment
        }
    @PART[nfa-fueltank-25-3]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = largeVolumeContainment
        }
    @PART[nfa-fueltank-25-4]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = largeVolumeContainment
        }
    @PART[nfa-intake-largecircular]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = supersonicFlight
        }
    @PART[nfa-intake-largeramp]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = enduranceFlight
        }
    @PART[nfa-intake-largeshock]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = hypersonicFlight
        }
    @PART[nfa-intake-radial-1]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = hypersonicFlight
        }
    @PART[nfa-intake-radial-2]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = hypersonicFlight
        }
    @PART[nfa-rcsblister-1]:NEEDS[NearFutureAeronautics]
        {    @TechRequired = actuators
        }

//    ============================================================
//    *** Supplementary Electric Engines
    @PART[PPT_22]:NEEDS[SupplementaryElectricEngines]
        {    @TechRequired = ionPropulsion
        }
    @PART[PPT_33]:NEEDS[SupplementaryElectricEngines]
        {    @TechRequired = ionPropulsion
        }

Edited by SpudNutimus
Link to comment
Share on other sites

  • 2 weeks later...

Great job with the tech tree. I am doing a career playthrough right now with TETRIX installed and I'm having a hard time understanding some of the rationale behind some choices. 

For the most part, the engines seem to be unlocked in a logical order. But the rest of the tree just seems misplaced.

Why not move the mite and shrimp to the very beginning of the tree? Instead of using a 0.625m probe on a 1.5m flea booster.

For construction parts, why am I unlocking near-future orbital construction parts(tier3) before the most basic cubic family strut (tier5)?

the Airplane plus parts seem to be scattered all over the tech tree. low-tech fighter cockpits in tier 4, and next generation cockpits in tier 3.

Fixed landing gear being separated into different nodes for some reason.

Jet engines before prop planes, I could go on with the different mods I have installed that are compatible with the tree.

 

 

Link to comment
Share on other sites

@symphons, you make great points and I learnt a lot when i made the newer Quartix tree in regards to balancing and how the early tiny and small size tanks might work.

It some repsects it was a replication of the stock tree, but yes i agree now it seems a bit odd.  It looks like i may need to revisit perhaps when I'm on vacation in a couple of weeks.

Link to comment
Share on other sites

@theJesuit I think the main problem with a lot of tech trees seem to be the airplane parts, and this is coming from someone who has basically tried every tech tree. Even with GAP, ultimately planes seems to be a dead-end in terms of a career play through.

They simply do not net any science gains considering their value. I can spend upwards of 500science on a career play-through just to unlock an x-1 type craft air-dropped from a bigger plane.

Planes below SSTO capabilities I think should just be much lower science value. A slow flying cargo plane should not take a lot of science to unlock.

Link to comment
Share on other sites

7 hours ago, symphons said:

@theJesuit I think the main problem with a lot of tech trees seem to be the airplane parts, and this is coming from someone who has basically tried every tech tree. Even with GAP, ultimately planes seems to be a dead-end in terms of a career play through.

They simply do not net any science gains considering their value. I can spend upwards of 500science on a career play-through just to unlock an x-1 type craft air-dropped from a bigger plane.

Planes below SSTO capabilities I think should just be much lower science value. A slow flying cargo plane should not take a lot of science to unlock.

I agree, but the limitations of the game allow you to pretty much take a mk1 cockpit and fly it jool with enough boosters.  SSTO aircraft are quite straight forward as well.

I think I understand what you are looking for though, as science around kerbin for planes to collect is limited, a large wing subsonic aircraft should be earlier if not fairly early in the tech tree so that we can replicate a X1 rocket to send a kerbal into orbit?

This is what I intended with Tetrix, the Mk3 stuff coming before the Mk2.  Not perfect though according to this logic that we are discussing.

I'll have a think about it. Any suggestions?

Link to comment
Share on other sites

  • 3 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...