Jump to content

Drew Kerman

Members
  • Posts

    5,829
  • Joined

  • Last visited

Posts posted by Drew Kerman

  1. 2 hours ago, Arrowstar said:

    What do you all think?

    I think I'm glad I took a break and didn't launch my interplanetary mission last month like I had originally planned a few years ago :P Was *not* looking forward to getting it implemented in MA or LVD earlier this year given my shrinking time constraints. Look forward to plotting a new series of Extremis missions now! Bummer I need to go back to finding new flyby routes first since I only searched through 2021...

  2. On 9/3/2021 at 9:20 PM, Arrowstar said:

    First, would anyone actually use something like this when they play KSP? 

    *jumps up and down waving arms* ME! OOH! OOH! MEMEMEME!

    On 9/3/2021 at 9:20 PM, Arrowstar said:

    Be realistic, as this could potentially be a lot of effort. 

    But it wouldn't be for a while. KSA will resume ops in 2022 but it's still a ways from launching scanning satellites tho that is a priority. I'd use it right away for cameras tho

    Still, there's always people asking about good scanning orbits in the DMagic SCANSat thread and no one has really produced a tool dedicated to helping people with this. Best that's ever been done is a table of good orbits per instrument but that's been outdated for a while with more recent changes to how the SCAN instruments work

    On 9/3/2021 at 9:20 PM, Arrowstar said:

    there any other uses you can come up with that you might want to be able to do with this sort of functionality?

    Not yet...

  3. 5 hours ago, darthgently said:

    I was hoping to automate that process by having a sticky flag

    pretty sure this terminology is causing the confusion, especially since flags are an actual thing in KSP you can place on the ground

    @Ezriilcmy interpretation of this is he wants an option in the Hyperedit settings menu that when enabled:

    1. checks the type of vessel on scene load
    2. if the type == base then
    3. lift the vessel n (user defined amount in the settings) meters off the ground
    4. land it at the same coordinates

    So, automatically uses the functionality of the vessel landing feature

  4. On 7/3/2021 at 1:30 PM, dlrk said:

    Could someone walk me through planning a polar orbit rendezvous? I'm trying to plan a flight from Kerbin orbit to dock with a station in a polar orbit of the Mun

    basic steps for a basic mission:

    1. use LVD to design a launch into an equatorial parking orbit
    2. use Rendevous Maneuver Sequencer to get an ejection path towards Mun
    3. use Mission Architect or LVD to plot remainder of mission:
      1. enroute to Mun, plane change and adjust orbital insertion to match station inclination
      2. enter into Mun polar orbit
      3. use RMS to meet up with station
  5. not playing currently but will be returning eventually - does the latest version still cause the camera to "jump" up a bit when you launch a vehicle and unhook from a clamp? That always annoyed me and was something KerbCam didn't do. KerbCam also let you target other objects beside the main vessel, which also helped prevent the camera jump. If this is fixable with the way CameraTools is doing things, that would be great

  6. On 2/23/2021 at 7:48 PM, Arrowstar said:

    What do you think, @Drew Kerman?

    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

  7. 5 hours ago, Arrowstar said:

    At this point it'll be next week, but I'll look into it.

    cool thx, no rush at all just making sure it was still on your radar

    5 hours ago, Arrowstar said:

    Yes, there is a warning in the warning/alerts area that tells you if variables are near their bounds.

    @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

  8. 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

    H4cTL83.png

    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 ascent telemetry

    D6X8vis.png

  9. 1 hour ago, Arrowstar said:

    If you check your output log

    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 log in LVD/MA - is it possible to lock its position? As in, there's a behavior for some applications where the scroll position remains constant even if stuff is appended to the bottom, but if the scroll bar is all the way to the bottom it scrolls with any addition updates

    1 hour ago, Arrowstar said:

    Try switching events 5, 7, and 8 to the ODE5 integrator

    Can I get a bit more insight into your decision to switch to ODE5 and for those particular events? I recall you have the ability to see where things get hung up but I'm still wondering if there's a way I can come to this conclusion myself

    1 hour ago, Arrowstar said:

    The only impact non-sequential events have (and have ever had) is the ability to fire off actions in the middle of a sequential event.  They've never been able to change event colors, integrators, stuff like that.  I should really disable all that stuff for non-sequential events, to be honest...

    Yea, if you can't use them I would agree they be removed or disabled. But also if they *can* modify trajectory properties like I described that would be cool too :P So okay then I guess I just re-worked the ascent to use all sequential events to build my colored plot. That's not really a big deal to have to do either if I must, cause like I already did heh heh

     

  10. 24 minutes ago, Arrowstar said:

    I think I've got this one figured out.  It was an issue where the minimum thrust to weight achievable (at zero throttle) was actually greater than your target T2W ratio, causing the system to basically not know what to do.  I've added a check for this case, which is in addition to the existing check for a maximum T2W being less than the target T2W.

    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

  11. 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

  12. was there a behavior change with Non-Sequential Events coloring trajectory lines or am I not remembering correctly? I made this last year:

    Uui1aY9.png

    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 sequential event color changes rather than a combo of both

×
×
  • Create New...