Jump to content

Drew Kerman

  • Content Count

  • Joined

  • Last visited

Community Reputation

2,140 Excellent

About Drew Kerman

  • Rank
    KSA Operations Director

Contact Methods

Recent Profile Visitors

12,985 profile views
  1. Alt+X by default. Alt+C to remove angle snap or maybe its Ctrl instead of Alt. Dunno why I can't remember I do it all the time lol
  2. I think I'm going to be throwing more data at you in the future but for now I agree, seems like a good correlation to explain what's happening. Also delay in response due to not checking the thread directly. FYI I have found that when you edit a post, even sticking in a new user tag doesn't generate an alert for that user
  3. cool thx, no rush at all just making sure it was still on your radar @russm a bit of extra info that may not be obvious: you need to hover your mouse cursor over the warning to get the detailed info as to which events are causing bounds issues Also keep in mind that when you make requests for things to lighten the workload on us end-users (which I agree is nice, I myself have requested things like the ability to export/import ground stations) you're taking away already limited spare time for development of new features, as both are only coming from one person
  4. @Arrowstar just realized I heard back from you on all my recent postings except this one with the odd dynamic pressure plot:
  5. sweet, this will hopefully pair nicely with PersistentRotation, recently revived as well. Currently I'm using MandatoryRCS mod to get both of these features but it hasn't been serviced in a while and it's dubiously working on more recent KSP versions. Thanks for the update and hope you continue with the QoL fork at the very least
  6. This isn't even Scatterer water yet when I saw it on reddit my first reaction was still "ZOMG Scatterer vehicle water reflections!!!"
  7. Sorry forgot to post here earlier this week as a reminder but turns out the Ascension Mk3 still has yet to launch due to ongoing delays. Next attempt is tomorrow 2/12 targeting L-0 of 19:00 UTC so don't miss it!! Click the image for the Ops Tracker Also if you did not catch the first launch of the year last month, click the image below to go to the Ops Tracker where you can not only review all the major events but the Additional Resources has links to the mission report, telemetry data and full flight analysis report. If you go back to the launch event you can replay the streaming a
  8. Aha! But frankly what would make me do that? I've only ever treated it as an error log so when the application goes *ding* that's the first place I look but there were no indications of a problem with script execution. In fact when I read this my first thought was that it showed up in the output log in LVD itself and that I could have easily not thought to check it since it updates at the bottom usually out of sight, but it wasn't there either so I finally opened the .log file. This seems like a thing that should pop up in the Warnings & Alerts area no? Also in relation to the output
  9. oooohhh daamn I was thinking soo hard on how it could possibly be affecting my script when I made sure no events had anything to do with that stage but I did not think about the mass change affecting TWR. Durr. Nice catch
  10. another example of weirdness that seems related to the UT issue would be to use the Ascension Mk3 #1 Ascent 250km Time Constraint.mat file and just uncheck the one optimized box for the steering in Event 3. That's it. Do nothing else just disable the optimization hi/lo and save, the trajectory will change. If you do this in the Ascension Mk3 #1 Ascent 250km.mat file where the UT starts at 0 it will not change the trajectory
  11. was there a behavior change with Non-Sequential Events coloring trajectory lines or am I not remembering correctly? I made this last year: And when I went to do one for my current ascent, if I changed the line color for a non-sequential event I don't see a color change on the plot anymore. I thought the non-sequential event triggered a plot color/line type change when it occurred, and this change persisted until the next sequential or non-sequential event happened. Of course I could be remembering wrong and the above colored plot could just be a rough approximation using only se
  12. Just to confirm I'm not missing anything, I can't find a way to lock these together so that when I move one the other shows the same data point. This is not a thing Matlab can do?
  13. woooah @Arrowstar I'm seeing some more serious hinkyness here when messing with the Initial UT, moreso than just its effect on the Jacobian. Files download. Start with Ascension Mk3 #1 Ascent.mat, which is mostly the same file I linked to in the last post but I reset the Initial UT to 0 and changed my constraints to have it find me a 250km apokee. I also labeled the last event more appropriately since no pitch change happens just the end of the burn so the engine should be shut off, SECO-1. Okay if I optimize from this point, after about 30 iterations or so over 45-60min it gets me t
  • Create New...