Jump to content

aquilux

Members
  • Content Count

    199
  • Joined

  • Last visited

Community Reputation

19 Good

About aquilux

  • Rank
    Spacecraft Engineer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm not sure about real fuels, so you'll have to try it out both your suggested way, and by listing each fuel, but you'll have to make a whole copy of each fuel. The reason why I had to separate oxidiser and monoprop is that apparently " | " does not work in the filter section. If this changes, or I'm wrong, I'll be combining the two so that there is only one math section and what not.
  2. the math is... mostly fixed. I think. Should work for the most part.
  3. If the useEngineResponseTime components carry over to any new engines generated by MM copies of .cfg files, then yes you can, otherwise you could probably just change the resources it looks for (unless the engine code gets stupid complicated with the ability to select various fuels). But I just realised that I think I got the math backwards, and I'm in the process of reworking it, so give me a little while.
  4. Engine spool delay for all. Ok, so here is the completed patch. I'd like to thank @Aelfhe1m for all their help, I couldn't have figured this thing without them. This patch adds engine spool delays to all engines that pump some form of fluid for a chemical reaction (stock resources only). The delays are based off of engine mass, with the ratios being loosely based on the KW rocketry engines. //Add engine response time to engines that pump fluids but have no engine spooling. //Author: Aelfhe1m & Aquilux //////////////////////////////////////////////////////////////////// //Thi
  5. Good eye. I'm not sure how I missed that. Same with the @ on the second section, that was leftover from when I made and deleted the variables twice.
  6. Something in the math keeps throwing exceptions, but I'm not seeing it. I'll keep looking, but for now, this is what I have. //Add engine response time to engines that pump fluids but have no engine spooling. //Author: Aelfhe1m & Aquilux //////////////////////////////////////////////////////////////////// //This script adds engine spooling delay to engines that pump at least one liquid for a chemical reaction. //Engine spooling delay is dependent on the momentum of the turbines in the engine. //This script assumes that turbine mass is an average fraction of engine mass, thus delay is d
  7. That's weird. I could have sworn I copy/pasted from a squad .cfg. That might be it. I was starting to guess that. I feel kind of dumb for not trying it. Thank you so much for the help @Aelfhe1m. Also, considering how atrocious the <code> tool is for tabbing and alignment, I'm not even going to try. I'll just copy/paste directly from notepad++ and dump it into the widget. Hopefully it comes out right on the other side when others copy/paste from the page. In case you or someone else uses notepad++ as well, there's a forum post that has a user defined language
  8. This is what I'm working with. //Add engine response time to engines that pump fluids but have no engine spooling. //Author: Aelfhe1m & Aquilux //////////////////////////////////////////////////////////////////// //This script adds engine spooling delay to engines that pump at least one liquid for a chemical reaction. //Engine spooling delay is dependent on the momentum of the turbines in the engine. //This script assumes that turbine mass is an average fraction of engine mass, thus delay is derived from engine mass. // //equations for accel/decel/mass relationships derived from KW roc
  9. @PART[*]:HAS[@MODULE[ModuleEngines*]:HAS[!PROPELLANT[SolidFuel],~useEngineResponseTime[True]]] @PART[*]:HAS[@MODULE[ModuleEngines*]:HAS[@PROPELLANT[Oxidizer],~useEngineResponseTime[True]]] So I'm getting stumped. what is the difference between these, and why would the one asking for oxidiser fail but not the one rejecting solid fuel?
  10. So, I've managed to chart the engineAccelerationSpeed, engineDecelerationSpeed, and Mass values for the KW rocketry engines as examples and derive trendlines. Problem is the equations are polynomial. Now, I'm total crap at algebra and the MM algebra functions appear to be done one step at a time, but this'd be easily solved if I could use multiple variables. and toss them when done. Is this doable within MM config files, or will I have to somehow consolidate the mass variables together? These are the equations: engineAccelerationSpeed = -0.153838m + 0.00495282m2 + 1.95125 engine
  11. So I 'll have to make separate MM configs for each resource I guess. I have a few hybrid rocket engines that still need to spool up the delivery of oxidiser, but use solid fuel. Yeah, just found that. Feel kind of dumb for it, but hey, that's how you learn right? Hmmm. Going to have to wrap my head around that math then, I got my assumptions backwards. That clarifies things. I guess I missed that in the documentation. I'll post my results when I figure out the math, as that's likely going to be the last thing I'll figure out.
  12. Sorry, I missed that bit. I've been trying this out: //Add engine response time to all instant response engines based on part mass. //Author: Aelfhe1m, Aquilux //@PART[*]:HAS[@MODULE[ModuleEngines*]]:HAS[PROPELLANT[Oxidizer]|PROPELLANT[MonoPropellant],~useEngineResponseTime[True]] //Aq version @PART[*]:HAS[@MODULE[ModuleEngines*]]:HAS[!PROPELLANT[SolidFuel],~useEngineResponseTime[True]] //Ae version //find parts containing ModuleEnginesFX that uses Oxidiser, but does not have useEngineResponseTime { @MODULE[ModuleEngines*] { engineAccelerationSpeed = #$/mass$ //edit engineAccelerationS
  13. But once we find the .cfg we want to edit with the search section, aren't we then telling it which module to modify? What happens if it finds a part without the *FX module, then tries to modify the nonexistant module?
  14. The ModuleEnginesFX issue occured to me as well, but if we also test for ModuleEngines wouldn't we need to detect which one is being used, and change our package accordingly? I was just going to perfect the FX version, then copy it for the sans-FX version. Edit: I'm testing the code now with an absurd delay, I'll see if this patch is catching the solids, though I do have hybrid engines (Solid Fuel+Oxidiser), and figured they'd need spool up times as well.
  15. So, I seem to have it working, though it appears as though it's adding response time to solid fuel engines despite the addition of the requirement for oxidiser as a propellant. I'm trying to figure out what I did wrong, and if I can get it to check for oxidiser OR monopropellant. I know OR involves the | symbol, I just don't know how to incorporate it into the search. Here is what I have (ps: notepad++ is boss for catching nesting errors before you get syntax exceptions). //Add engine response time to all instant response engines based on part mass. //Author: Aelfhe1m, Aquilux @PART[*]:HAS
×
×
  • Create New...