Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

139 Excellent

1 Follower

About TheDog

  • Rank

Recent Profile Visitors

4,280 profile views
  1. Seems to be a stock bug affectung all sort of fuel switchers (not only configurable containers, but also ifs, firespitter, wbi, ...). I just happened to notice first with CC: I have filed a bug report with squad: https://bugs.kerbalspaceprogram.com/issues/26988
  2. Indeed. I am running most of the USI stuff, most of Nertea's things, and many wildblue mods. Nertea's mods, especially station parts, always fully supported USI-LS and integrate very well. With his latest things (farfuture) you have to carefully look if you want to switch over to the systemheat approach (heating topic) and the space dust (resource distribution topic). That could potentially conflict with usi, or you have 2 things running side by side. Wildblue is a different story, but i have my own solution for that.
  3. Yeah, honestly, I am also curious, and dont have a clear idea where it'll be going with that topic. In general my idea is more to adapt Pathfinder etc to USI, as that is my "leading" setup. So in the near future i suppose i'll be adding USI konfrabricator to WBI mods that currently have OSE workshop, and thus add stock inventory space (if angel-125 is not going that route anyway). We'll see
  4. And it is now on CKAN! Lots of thanks to @HebaruSanfor making this possible. Due to him CKAN now recognizes and supports conflict-free installation of WBI Playmodes!
  5. The only thing that stands out in the logs is a fsfuelswitch error about parsing a resource amount, and i believe that shouldnt be there. Could you maybe just replace the bundled firespitter with a fresh version from the individual mks download?
  6. Not discounting Nertea's work, but for me it doesnt work very well (doesnt account for a lot of ec consumers) and is a frequent source of nullref spams in my logs...
  7. Please forgive me, I am cross-posting this from @allista's configurable containers, see Posts #1 and #2: I am experiencing an oddity with KSP 1.11 and mods that can switch tank contents, such as CC and IFS: * if a tank content is switched to something other than its original contents, then the resources drained in VAB, vessel launched & immediately recovered, the recovery funds are off - part value for the recovered tank can even go negative in case of expensive resources such as from the community resource kit, but can be verified with stock resources such as MonoProp. Hence you
  8. More observations and more weirdness: 1. Stock install (no configurable containers): Rockomax X32, LFO, resources emptied before launch, launc+immediate recovery: ->The recovery funds are 100% correct 2. With Configurable Containers (otherwise just stock): Rockomax X32, 100% as LFO tank, resources emptied before launch, launc+immediate recovery: ->The recovery funds are 100% correct 3. With Configurable Containers (otherwise just stock): Rockomax X32, 100% as MonoProp tank, resources emptied before launch, launc+immediate recovery: ->The recovery funds are incorrect (n
  9. Something is extremely fishy in KSP 1.11... See also screenshots: * configure a tank with an expensive resource. (Vessel price with FLT400 full of rare metals would be >300.000 kredits) * empty the tank. vessel will cost a few bucks * launch vessel, immediately recover from launchpad. I get a negative refund, effectively I have to "pay" for over 300k in "missing" rare metals...!! what! Actually, I am not even sure that is related to Configurable Containers - seems more like a KSP bug. Anyone can confirm/having seen that?
  10. At least in USILS this represents the complete LifeSupport supplies: meals, water, oxygen, toothpaste, ... I find it more unrealistic (too easy) that supplies->mulch is mass conserving. But it is a reasonable abstraction.
  11. I am "a bit" late to the party, but if anyone is still interested, here you go...
  12. @m4v its analyzed: You could indeed not repro it, because in MOLE's "standard playmode" after installalation, "ClassicStock", the engine (Fulcrum in this case) is configured as a multi-mode engine, and indeed has 2 usable modes. So no problem here (see screenshot #1). If the playmode is changed, e.g. to "CRP", then there is a problem on the engine config: it is still declared in the part config as multi-mode, but has actually only one usable mode. This confuses RCSBuidlAid and leads to that nullref spam (see screenshot #2). Showing the situation: 1) no problem, and 2) problem
  13. Interesting, i'll have a more detailed look in a trimmed down install (currently at 80+ mods, not good for finding root causes...). Will get back to u!
  14. update: playmode switching may not be good for ckan in case of updates, sorry...
  15. Getting VAB nullref spam with the latest 1.0.4 version, but for some engines only (all mod delivered ones, such as the "Fulcrum" engine from WildBlueIndustries MOLE). In the log it says: [EXC 18:27:46.863] NullReferenceException: Object reference not set to an instance of an object RCSBuildAid.EngineForce.getThrust () (at <d47c6305c5d444f8ac716df736136b89>:0) RCSBuildAid.EngineForce.getThrust (System.Boolean asl) (at <d47c6305c5d444f8ac716df736136b89>:0) RCSBuildAid.EngineForce.Update () (at <d47c6305c5d444f8ac716df736136b89>:0) RCSBuildAid.MultiModeEngineForce.U
  • Create New...