speedwaystar

just time to empty based on current inputs would be best. that way, in the VAB, the result of adding/removing solar panels etc can be monitored easily, and in orbit, a rough estimation of current capacity would be available. a simple circular orbit estimation would be really useful for figuring out how many batteries to load onto satellites.

if was working properly you should see "Camera off", with a button to turn it on, in the docking port context menu. it may or may not make a difference, but if you've installed from CKAN, the line [CODE]model = OLDD/DockingCam/OnboardCamera[/CODE] in OnboardCamera.cfg should be changed to [CODE]model = DockingCam/OnboardCamera[/CODE] otherwise the camera model (not the one automatically added to docking ports) won't be placeable in the VAB.

i'll double check exactly what's happening re: the warp warnings also. couple more suggestions/requests: * add a display showing time until batteries run out at current drain (the addon is called AmpYear after all :D). this would be hugely helpful at the design stage to ensure sufficient battery grunt to run the vehicle's loadout during the expected periods of darkness. * as an added convenience, but of lesser priority: i believe fusebox (which i haven't used) had a tool which calculated hours of darkness in orbit around various bodies and when landed on the surface. is this easy to add? all with a view to saving the buttons on my calculator from being ground to powder :D

another question--sorry if this has already been answered. various parts report odd power-drain stats in the VAB (but show correct stats once launched). for example, the Mk1-2 command pod with no attachments shows 18 power consumption in the VAB and 0.175 (AmpYear's system drain) on the launchpad. is it possible to rectify this, or at least arrive at a close approximation?

for example, if i'm on a munar orbit and go into penumbra and end up on reserve power, i have to manually reenable timewarp repeatedly before i come out of shadow and my batteries recharge, because ampyear is turning timewarp off every time it reaches (from memory) about 50x warp to post the "not enough power" warning. ideally it should kick me out of timewarp once for the warning, and then leave me alone to timewarp out of the mun's shadow.

// Speedwaystar's RemoteTech patch for HGRSolarPanels // omni antenna, ranges = 100km undeployed and 1500km deployed @PART[HGRSolarPanels1]:NEEDS[RemoteTech]:FIRST { !MODULE[ModuleDataTransmitter] {} %MODULE[ModuleRTAntenna] { %Mode0OmniRange = 100000 %Mode1OmniRange = 1500000 %EnergyCost = 0.05 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.4 %PacketSize = 2 %PacketResourceCost = 12.0 } } %MODULE[ModuleSPUPassive] {} } // OPTIONAL: // make multiple deployed omni antennas act as one slightly larger antenna // (remotetech optional rule) @RemoteTechSettings:NEEDS[RemoteTech]:FINAL { @MultipleAntennaMultiplier = 1 }

@PART[Leek]:HAS[!ModuleScienceLab]:FIRST { MODULE { name = ModuleScienceLab containerModuleIndex = 0 dataStorage = 400 crewsRequired = 1 canResetConnectedModules = True canResetNearbyModules = True interactionRange = 5 SurfaceBonus = 0.1 ContextBonus = 0.25 homeworldMultiplier = 0.1 RESOURCE_PROCESS { name = ElectricCharge amount = 10 } } }

here's a summary of the various fixes/changes i've been able to scrape from this thread, if that helps. I've compiled them into a MM cfg, with attribution: // tank cost reduction by Kerbas_ad_astra // http://forum.kerbalspaceprogram.com/threads/60974-1-0-2-HGR-1-875m-parts%28v1-3-0-released%29?p=2256768&viewfull=1#post2256768 @PART[HGR_Small_Tank,HGR_Normal_Tank,HGR_Large_Tank,HGR_Huge_Tank] { @cost /= 2 } // AntennaRnage patch by Kerbas_ad_astra // http://forum.kerbalspaceprogram.com/threads/60974-1-0-2-HGR-1-875m-parts%28v1-3-0-released%29?p=2256768&viewfull=1#post2256768 @PART[HGRSolarPanels1]:NEEDS[AntennaRange] { @MODULE[ModuleDataTransmitter] { @name = ModuleLimitedDataTransmitter nominalRange = 6364 simpleRange = 20500000 maxPowerFactor = 8 maxDataFactor = 4 } MODULE { name = ModuleScienceContainer dataIsCollectable = true dataIsStorable = false storageRange = 2 } } // fairing size mass reduction by fatbrother // http://forum.kerbalspaceprogram.com/threads/60974-1-0-2-HGR-1-875m-parts%28v1-3-0-released%29?p=2091225&viewfull=1#post2091225 @PART[fairingSize1.5] { @mass = 0.1 // down from 0.2, qv 1.25 = 0.075, 2.5 = 0.175 @MODULE[ModuleProceduralFairing] { @UnitAreaMass = 0.0175 // down from 0.1, qv 1.25 = 0.015, 2.5 = 0.02 } } // add science lab to Onion by rasta013 & Kerbas_ad_astra // http://forum.kerbalspaceprogram.com/threads/60974-1-0-2-HGR-1-875m-parts%28v1-3-0-released%29?p=2000320&viewfull=1#post2000320 @PART[OnionNew]:HAS[!ModuleScienceLab]:FIRST { MODULE { name = ModuleScienceLab containerModuleIndex = 0 dataStorage = 350 crewsRequired = 1 canResetConnectedModules = True canResetNearbyModules = True interactionRange = 4 SurfaceBonus = 0.1 ContextBonus = 0.25 homeworldMultiplier = 0.1 RESOURCE_PROCESS { name = ElectricCharge amount = 10 } } } // add KIS inventory to SoyLima by ZentroCatson & Kerbas_ad_astra // http://forum.kerbalspaceprogram.com/threads/60974-1-0-2-HGR-1-875m-parts%28v1-3-0-released%29?p=2011785&viewfull=1#post2011785 @PART[Lima]:NEEDS[KIS] { MODULE { name = ModuleKISInventory maxVolume = 1000 externalAccess = true internalAccess = true slotsX = 4 slotsY = 4 slotSize = 50 itemIconResolution = 128 selfIconResolution = 128 openSndPath = KIS/Sounds/containerOpen closeSndPath = KIS/Sounds/containerClose defaultMoveSndPath = KIS/Sounds/itemMove } } // SoyJuice retro rockets fix by pacbard // http://forum.kerbalspaceprogram.com/threads/60974-1-0-2-HGR-1-875m-parts%28v1-3-0-released%29?p=2014580&viewfull=1#post2014580 @PART[Soy-Juice] { @MODULE[ModuleEngines] { engineID = LES powerEffectName = running_closed @fxOffset = 0, 0, 0.25 } }

could we have an option to disable the "not enough power to run timewarp" message and the accompanying timewarp disablement after the first warning? i'm not sure if setting Power Low Warning Percentage to 0 completely disables the message, but in any case it's a useful warning to see... once :D =

great work. i really like the keep-it-simple-stupid principle behind SMU (simple modulemanager adjUstments)--i hope it catches on! here's a stock 3m procedural LFO tank: [IMG]http://i.imgur.com/wYd7HU3.jpg[/IMG] and the same tank with SMURFF: [IMG]http://i.imgur.com/GUS7iV6.jpg[/IMG] fix: [CODE]@PART [*]:HAS[@MODULE[TankContentSwitcher]]:FOR[SMURFF]{ @MODULE[TankContentSwitcher] { @TANK_TYPE_OPTION[Mixed,LiquidFuel,Oxidizer,RCS] { @dryDensity /= 4 @RESOURCE[LiquidFuel] { @unitsPerT *= 4 } @RESOURCE[Oxidizer] { @unitsPerT *= 4 } @RESOURCE[Monopropellant] { @unitsPerT *= 4 } } @TANK_TYPE_OPTION[XenonGas] { @dryDensity /= 7 @RESOURCE[XenonGas] { @unitsPerT *= 7 } } @TANK_TYPE_OPTION[SolidFuel] { @dryDensity *= 0.6 @RESOURCE[solidFuel] { @unitsPerT /= 0.6 } } } %MODULE[ModuleSMURFF]{ } }[/CODE] [IMG]http://i.imgur.com/7gY6kO8.jpg[/IMG] enjoy! :D EDIT: pull request created

these are really nice. you should put them on CKAN!

[COLOR=#222222][FONT=Verdana]From the 1.05 patch notes: [/FONT][/COLOR] [QUOTE]* Added an option to antenna context menus to manually enable partial transmissions.[/QUOTE] [COLOR=#222222][FONT=Verdana]this doesn't seem to be displaying for me, which might be related to the problems FancyMouse is trying to address.[/FONT][/COLOR]

Thanks! I'll give that a try.

Howdy folks, For my own convenience I've added "Fuel Tanks" between "Kerbonauts & Control" and "Engines", as follows: CATEGORY{ name = Fuel Tanks icon = stockIcon_fueltank colour = #FF90F090 all = true SUBCATEGORIES { list = 0,LFO Tank [0.625m] list = 1,LFO Tank [1.25m] list = 2,LFO Tank [2.5m] list = 3,LFO Tank [3.75m] list = 4,Liquid Fuel Tank list = 5,Oxidizer Tank list = 6,Monopropellant Tank list = 7,Xenon Gas Tank list = 8,Radial Tank } } SUBCATEGORY { name = LFO Tank [0.625m] icon = cs_size0 FILTER { CHECK { type = category value = Fuel Tanks } CHECK { type = profile value = size0 } CHECK { type = resource value = LiquidFuel } CHECK { type = resource value = Oxidizer } } } SUBCATEGORY { name = LFO Tank [1.25m] icon = cs_size1 FILTER { CHECK { type = profile value = size1 } CHECK { type = category value = Fuel Tanks } CHECK { type = resource value = LiquidFuel } CHECK { type = resource value = Oxidizer } } } SUBCATEGORY { name = LFO Tank [2.5m] icon = cs_size2 FILTER { CHECK { type = profile value = size2 } CHECK { type = category value = Fuel Tanks } CHECK { type = resource value = LiquidFuel } CHECK { type = resource value = Oxidizer } } } SUBCATEGORY { name = LFO Tank [3.75m+] icon = cs_size3 FILTER { CHECK { type = profile value = size3,size4,size5,size6 } CHECK { type = category value = Fuel Tanks } CHECK { type = resource value = LiquidFuel } CHECK { type = resource value = Oxidizer } } } SUBCATEGORY { name = Liquid Fuel Tank icon = R&D_node_icon_fuelsystems FILTER { CHECK { type = category value = Fuel Tanks } CHECK { type = resource value = LiquidFuel } CHECK { type = resource value = Oxidizer invert = true } } } SUBCATEGORY { name = Oxidizer Tank icon = fuels_oxidizer FILTER { CHECK { type = category value = Fuel Tanks } CHECK { type = resource value = LiquidFuel invert = true } CHECK { type = resource value = Oxidizer } } } SUBCATEGORY { name = Monopropellant Tank icon = fuels_monopropellant FILTER { CHECK { type = category value = Fuel Tanks } CHECK { type = resource value = MonoPropellant } } } SUBCATEGORY { name = Xenon Gas Tank icon = fuels_xenongas FILTER { CHECK { type = category value = Fuel Tanks } CHECK { type = resource value = XenonGas } } } SUBCATEGORY { name = Radial Tank icon = cs_surface FILTER { CHECK { type = category value = Fuel Tanks } CHECK { type = profile value = srf } } } All works well, except for the Radial Tanks category which simply returns all items of type "Fuel Tank". I'm using the filtering method employed in 00_FilterExtensions Configs/SubCategories_Bulkhead.cfg, which seems to have similar issues. I also tried: CHECK { type = bulkheadProfiles value = srf } which didn't work (matches nothing), as does trying value = *srf*. bulkheadProfiles seems to be an array, since it's often initialized with something like: bulkheadProfiles = size1, srf I'm not sure if a CHECK {} block can query an array, if that's what it is. So basically, what's the best way to filter for surface-connected items?