leatherneck6017

Members
  • Content Count

    234
  • Joined

  • Last visited

Everything posted by leatherneck6017

  1. Like you said, any .dll that's not part of an installer is going to get flagged by most antivirus software. You can always use dnSpy to browse the code before using a strangers recompile.
  2. A config that would cover ALL parts would be hundreds, if not thousands of patches. Most part mods that want to enable TweakScale functionality already include MM patches with their releases. Keep in mind there are different "types" of TS modules for a reason. For example, engine resizing must utilize specific formulas to scale thrust and fuel consumption. Using type=free on an engine would produce unrealistic and possibly unusable results.
  3. I looked at the MM patch. The "type = free" will break proper TweakScale implementation on most parts. Sorry to tell you, but I would not recommend anyone to use this.
  4. @JacobJHC This looks interesting, and well done. I'll check it out! Agreed! I literally spit coffee on my keyboard (and a little on my monitor).
  5. @linuxgurugamer Thank you for doing this. It will be a welcome addition to my game!
  6. I'd imagine that those are both very lightweight. Not a valid complaint, IMO. But --\O/--
  7. Do people complain about it? Many of your mods require it. I think it's a fantastic dependency.
  8. My toolbar is up top to the right of the time warp indicator. I have problems with click through in map view. No biggy, just an idea.
  9. @linuxgurugamer Perhaps I'm misunderstanding the function of the collect all button. The way I understand it is, when pressed it collects results that are stored in the experiments and transfers them to an available science storage container. Is this correct?
  10. I believe the 1.4 version was working fine, but I did the recompile just because. The Dropbox link to my recompile is a few posts back.
  11. It is disabled by default. It's only "on" if you set a reference for it to use.
  12. @linuxgurugamer Are there any plans to add support for click through blocker?
  13. What do you mean? Collect all transfers the data from the experiment to science storage located in the pod/probe/etc.
  14. You know what would be amazing (to me, anyway)? If the window were to show "collect all" whenever any science is stored in the experiment/scan/etc. For example, I have only one experiment on board, I run it and on the results window I tell it to save the data. In its current state, this mod will no longer display anything in its GUI. Let's say I've changed biome's and there would be the option to run it again, but the mod won't tell me because the previous data is still stored in the experiment itself. But if the collect all button was always visible if you had uncollected science, then it would prompt me to "clear out" my experiments. Hope this makes sense the way I've written it .
  15. Congrats on the release. I'm looking forward to trying it out.
  16. I miss having this in my 1.6.1 game. I used it a lot last year in 1.4.X.
  17. @BlackHat I'll admit that I completely forgot about that collection of MM patches. I enjoy writing my own, though. This is how I've done it: @PART[*]:HAS[#vesselType[Probe]]:Final { %MODULE[ModuleScienceContainer] { reviewActionName = #autoLOC_502201 //#autoLOC_502201 = Review Stored Data storeActionName = #autoLOC_502202 //#autoLOC_502202 = Store Experiments evaOnlyStorage = True // i.e. can nearby regular vessels also do this, or EVA only storageRange = 2.0 canBeTransferredToInVessel = True canTransferInVessel = True } } @PART[*]:HAS[@MODULE[ModuleCommand],!MODULE[ModuleScienceContainer]]:Final { MODULE { name = ModuleScienceContainer reviewActionName = #autoLOC_502201 //#autoLOC_502201 = Review Stored Data storeActionName = #autoLOC_502202 //#autoLOC_502202 = Store Experiments evaOnlyStorage = True // i.e. can nearby regular vessels also do this, or EVA only storageRange = 2.0 canBeTransferredToInVessel = True canTransferInVessel = True } } @PART[*]:HAS[@MODULE[ModuleCommand],@MODULE[ModuleScienceContainer]]:Final { @MODULE[ModuleScienceContainer] { %canBeTransferredToInVessel = True %canTransferInVessel = True } }
  18. IMO, anything with command (pod, probe, etc) should have the ability to store results. For that reason, I wrote a MM patch to add it to anything with ModuleCommand. Big QoL improvement! Oh, and thanks for fixing this. I had been using an action group to collect all.