Jump to content

severedsolo

Members
  • Posts

    2,813
  • Joined

  • Last visited

Reputation

2,980 Excellent

5 Followers

Profile Information

  • About me
    Junior Rocket Scientist

Recent Profile Visitors

10,742 profile views
  1. Don't install any other mods than the ones that your mod is dependant on. Get the mod working in stock before you even consider supporting other mods.
  2. @[email protected] - ScrapYard_ContractConfigurator is an extension class. It adds a few PARAMETERS to Contract Configurator that can in theory be used if ScrapYard is installed. It doesn't actually do anything without CC installed, and AFAIK nobody is using them anyway (probably because they are undocumented)
  3. The departments still get allocated the monthly budget, as per the allocations. The only difference is that your funds aren't capped, so you'll get given the "funding" departments money on top of your existing funds.
  4. If you are planning to go interplanetary, in my experience this is a problem that solves itself later in the game - I turn on Rep Decay (at about 5/10%) - although I have plenty of money in the "Apollo era" - when I'm going interplanetary it's not unusual for a launch to cost me 400-500k funds which obviously takes a big chunk out of the budget. Without flying other missions, the rep is decaying between launches and you find yourself on a tight budget. Otherwise, you could turn down the multiplier, or the rep rewards as you said. Or you could allocate less money to Funds and give your Construction and Research departments more budget.
  5. It's the daily budget catching up with itself. The budget runs (approximately) every 1 solar day on your homeworld. However, if you happen to leave the scene before a full day has passed, you won't get the reward. So when the mod loads, it checks when the last update was and catches itself up.
  6. Expected behaviour - although I agree the tooltip could be worded a bit better (or possibly split into two tooltips). The margin is both the margin before the event, and the margin within which an alarm won't be set (to stop it from triggering alarms straight away when within the margin - as per your Maneuver node report below). That's definitely a bug, it should be respecting it if you are within the margin. These two are really the same issue, just coming at it from different ends - but definitely a bug. Thank you for the reports - raised #5
  7. That change would probably have to be done within TWP. It's all rather academic at the moment anyway as I understand TWP doesn't work in 1.12, but as I understand it TWP adds the alarm to KAC, so it would be up to TWP to update itself to add to the Stock Alarm Clock instead.
  8. I can certainly look at it! I've never used that feature so what does it do? I'm assuming it's an alarm for when an experiment has finished processing? (I never use the labs so excuse me if I ask stupid questions)
  9. Actually, the feature update is taking a while, so let's do it now. As I haven't received any feedback on the performance improvements, I'm going to assume they worked. Alarm Enhancements 1.0.2 Released Cache the list of Alarms to (hopefully) alleviate the GC stutters that were reported. Fix Maneuver Alarm setting not being respected.
  10. Yeah I missed a setting... sorry about that. Will get a fix out for that today, it's a simple enough fix.
  11. To be perfectly honest, your best bet in situations like this where your log isn't obviously blaming a candidate is to start doing the binary method. Remove half your mods (make sure you leave any dependencies) and see if you can reproduce the issue (probably in a new save, as loading an old save with half it's mods installed is asking for trouble). If the issue disappears, you know the problem is in the second half, so replace them and keep doing that into you narrow it down to the minimum set of mods required to reproduce the issue. Then report the issue to the mod makers and provide your logs etc, as you have here.
  12. Yep, it won't work 100% until you've upgraded your tracking station and got patched conics, but it won't break anything being installed mid-save. It doesn't save any data at all.
  13. @Apricot (and anyone else who might be having performance issues). Can you please try this build: https://1drv.ms/u/s!AtG2PODa0fmwi7g1Ey-jLgLKA0MkGA?e=gwb4F8 and see if it helps. (I've zipped it so your AV doesn't freak out, just replace the DLL in the AlarmEnhancements folder with this one).
  14. There's definitely some potential for excess GC allocation in the SOI calcs, thank you for raising it - I'll try and clean it up a little for the next release. I'll probably give you the option of increasing the timestep too, which should help. Raised #2
×
×
  • Create New...