sidfu

Members
  • Content count

    1083
  • Joined

  • Last visited

Community Reputation

66 Excellent

About sidfu

  • Rank
    Rocket Scientist

Recent Profile Visitors

1468 profile views
  1. i already have a settings.cfg included with it changed. also included is a profile that keeps some modules that conflict with MKS but are removed in the normal setup.
  2. can we get some new SS to show all the updates the SS and vid are all very old now
  3. all my profile does is disable the parts that conflict with tac like food consumption and such. a few modules are disabled like the mono fuel cell mostly to prevent ui clutter but other than that is all the base kerbalsim systems
  4. well what i do when i make a patch is i normaly just use a old one then tweak it much faster. than doing from scratch every time. now i have to do the probe plus ones thats missing rt stuff like the solar panel thats a antanna and such think i got the last of them for the probe plus. just put all of them included what was already did //Support for Coatl Aerospace //Configs by rakol, komodo, akron //CA-A01 Ground Plane Antenna @PART[antenna_tv]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0OmniRange = 500000 %Mode1OmniRange = 5000000 %EnergyCost = 0.18 %ProgressFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } //CA-A06 'Quetzal' Omni Antenna @PART[antenna_quetzal]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0OmniRange = 500000 %Mode1OmniRange = 1000000 %EnergyCost = 0.1 %ProgressFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } //CA-KPS KerbNet Position System Antenna @PART[ca_ant_gps]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0OmniRange = 500000 %Mode1OmniRange = 1000000 %EnergyCost = 0.1 %ProgressFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } //CA-A02 Conic Antenna @PART[antenna_cone_toggle]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0OmniRange = 500000 %Mode1OmniRange = 1000000 %EnergyCost = 0.1 %ProgressFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } //CA-A02 Conic Antenna @PART[antenna_cone]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0OmniRange = 500000 %Mode1OmniRange = 2000000 %EnergyCost = 0.15 %ProgressFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } //CAE-A03 Vorona Communication Array @PART[ca_vor_comm]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0OmniRange = 500000 %Mode1OmniRange = 2000000 %EnergyCost = 0.15 %ProgressFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } //CA-A100 Small Dish Antenna @PART[dish_S]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { @cost = 1000 // a bit more money. !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 36000000000 // should be good to duna, but only just. Needs testing. %EnergyCost = 0.60 // more energy hungry, but we can use solar in the inner system. %DishAngle = 3 // mega-nerf from 55 deg. %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } //CA-A200 Medium Dish Antenna @PART[dish_M]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { @cost = 2000 // more monies. !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 70000000000 // good to dres always, and jool on closer approaches. %EnergyCost = 0.29 // should fit ok in a 0.4 ec/s budget, but worse than higher tech below. %DishAngle = 1 // nerved slightly from 1.5 deg %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } //CA-A300 Large Dish Antenna @PART[dish_L]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { @cost = 8000 // age old balance technique: make the awesome thing expensive. !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 125000000000 // should be good out to jool for sure. Unsure what the min range for eeloo is. %EnergyCost = 0.21 // low enough to run on the 0.39 ec/s rtg, better than above. %DishAngle = 0.3 // kept at 0.3, should be a decent trade off. %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } //CA-A10 Small Folding Dish Antenna @PART[dish_deploy_S]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 90000000 // I don’t know what to do with this one; unsure what the application is intended to be. %EnergyCost = 0.50 %DishAngle = 20.0 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } //CA-AD1-R Folding Dish Antenna @PART[dish_deploy_S2]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 18000000000 %EnergyCost = 0.40 %DishAngle = 20.0 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } //Torekka Probe Core @PART[torekka]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { %MODULE[ModuleSPU] { } %MODULE[ModuleRTAntennaPassive] { %TechRequired = unmannedTech %OmniRange = 3000 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } } //CAE-L165 'Fomalhaut' Lander Probe @PART[ca_fom_lander]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { %MODULE[ModuleSPU] { } %MODULE[ModuleRTAntennaPassive] { %TechRequired = unmannedTech %OmniRange = 3000 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } } //barquetta Probe Core @PART[barquetta]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { %MODULE[ModuleSPU] { } %MODULE[ModuleRTAntennaPassive] { %TechRequired = unmannedTech %OmniRange = 3000 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } } //tatsujin Probe Core @PART[tatsujin]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { %MODULE[ModuleSPU] { } %MODULE[ModuleRTAntennaPassive] { %TechRequired = unmannedTech %OmniRange = 3000 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } } @PART[dish_tatsujin]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { @cost = 1150 // Slightly more than dish_S, although we are similar in specs. !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 38000000000 // Boosted to a little more than dish_s %EnergyCost = 0.55 // Tiny bit better than dish_S, but see below. %DishAngle = 5 // Better transmitter, later tech, a bit better cone? %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.2 // faster interval %PacketSize = 4 // jumbo packets %PacketResourceCost = 20.0 // but more costly to transmit as a trade off. } } %MODULE[ModuleSPUPassive] {} } //CA-A200 Medium Dish Antenna -- duplicated for new quetzal dish @PART[dish_quetzal]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { @cost = 2000 // more monies. !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 70000000000 // good to dres always, and jool on closer approaches. %EnergyCost = 0.29 // should fit ok in a 0.4 ec/s budget, but worse than higher tech below. %DishAngle = 1 // nerved slightly from 1.5 deg %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } @PART[ca_vor_dish]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { @cost = 1200 !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 38000000000 %EnergyCost = 0.55 %DishAngle = 5 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.2 %PacketSize = 4 %PacketResourceCost = 20.0 } } %MODULE[ModuleSPUPassive] {} }
  5. here a quick and dirty patch for RT and ground ops. think i got all the parts.all u need to do is tweak it and u can use it @akron //ca_landv_core @PART[ca_landv_core]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { %MODULE[ModuleSPU] { } %MODULE[ModuleRTAntennaPassive] { %TechRequired = unmannedTech %OmniRange = 3000 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } } //ca_landv_hga @PART[ca_landv_hga]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { %MODULE[ModuleSPU] { } %MODULE[ModuleRTAntennaPassive] { %TechRequired = unmannedTech %OmniRange = 3000 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } } //ca_landv_orbiter_core @PART[ca_landv_orbiter_core]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { %MODULE[ModuleSPU] { } %MODULE[ModuleRTAntennaPassive] { %TechRequired = unmannedTech %OmniRange = 3000 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } } //ca_landv_orbiter_HGA @PART[ca_landv_orbiter_HGA]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { %MODULE[ModuleSPU] { } %MODULE[ModuleRTAntennaPassive] { %TechRequired = unmannedTech %OmniRange = 3000 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } } //ca_landv_omni @PART[ca_landv_omni]:AFTER[CoatlAerospace]:NEEDS[RemoteTech] { !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0OmniRange = 500000 %Mode1OmniRange = 2000000 %EnergyCost = 0.15 %ProgressFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} }
  6. This is a Kerbalism profile to allow it and TAC-Life Support to work together. This removes kerbalism processes of food,water,oxygen consumption and co2 and waste production in favor of TAC. It leaves most kerbalsim systems intact. License:Unlicense Download Link: Spacedock Source: none as its only 2 .cfg files Install instructions. 1.extract 2.copy over kerbalsim install. 3. optional. includes a modified profile for those that dont use MKS. If you dont use mks then install that profile.
  7. hmm seems the fuel cell changes made by kerbalsim will conflict with the ones that MKS make. updated my kerbalsim profile to add a version without fuel cell edits by kerbalism for mks users. opened own page for my profile here
  8. @Linusgurugamer can u remove extra MM thats inside the NEBULA folder. for some weird reason it was causeing issues with my custom kerbalism setup. its weird as i thought MM was suppose to disable other MM dll if a newer version is found first. but it seemed like the 2.8 that was in the NEBULA folder was causeing removal of some nodes and double adding other nodes almost like both MM where running at start.
  9. Wouldn't it be good to list in OP which other mission packs are not needed if u use this one?
  10. finaly getting around to playing ksp again updated my tac profile for kerbalsim. any feedback is welcome.
  11. it doesnt have its on ksp forum entry as its i just made a modifcation of prexisting .cfg didnt want to have to go thru putting a licence on it just to have a forum topic
  12. think this error might be related to sceince revisted have to check next time i play NullReferenceException: Object reference not set to an instance of an object at KERBALISM.Configure.configure () [0x00000] in <filename unknown>:0 at KERBALISM.Configure.OnGUI () [0x00000] in <filename unknown>:0 its only on manned cpsules with exermpents on them so thats probaly what it is. ill check tomorrow its late here
  13. updated tac profile hopely that fixed the weird gui repeating error i had. it seemed to in limited testing
  14. if seti is compatiable with stock game now then it is with kerbalism
  15. encounttred a bug but couldnt pinpoint the cause. when i clicked the enabled station keeping on a ship manulay(in the right click menu) that was around 320km above kerbin everything disappeared and i was taking to exactly 0 heigt and the world textures where gone even on the space center(building still there thou). there was no error thou( i have critical error like that set to show on screen). funny thing is even going back to title the world textures where gone. havent booted up again to see if does again or if was random kracken hit. update. ok the black planet and 0alt seems to happen if u enabled sation keeping while on a suborbital path. doesnt seem to do it every time thou. probaly a check to prevent station keeping enable till they in alt greather than 1 to prevent. yeah right now cant enable station keeping on some except when u select them as the lists need update to include all the stock game categories on update why not make the llist by planet dropdown then slit into types. would be much more neater. for example kerbin sat relay sat 1