Drew Kerman

basic steps for a basic mission: use LVD to design a launch into an equatorial parking orbit use Rendevous Maneuver Sequencer to get an ejection path towards Mun use Mission Architect or LVD to plot remainder of mission: enroute to Mun, plane change and adjust orbital insertion to match station inclination enter into Mun polar orbit use RMS to meet up with station

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

good to hear a resolution was reached to resecure the account. Sorry you had to deal with that

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

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

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

@Arrowstar just realized I heard back from you on all my recent postings except this one with the odd dynamic pressure plot:

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

This isn't even Scatterer water yet when I saw it on reddit my first reaction was still "ZOMG Scatterer vehicle water reflections!!!"

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

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

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

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

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

minor bug - flight path angle is described in the GA output as km/s instead of degrees

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?

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 the result I want, which you can see in Ascension Mk3 #1 Ascent 250km.mat Now go and set the Initial UT to the day I want to launch: 139494660.0 - you should see the trajectory completely change. I was confused by this but since all I changed was the time I figured the optimizer could get me a launch time during this day that would work again. So I disabled all the event optimizations and set a hi-lo for Initial UT and let the optimizer run. You can see the results of this in Ascension Mk3 #1 Ascent 250km Time Constraint.mat Right, here's where it gets weird. Looking at the final state you can see I'm back to nailing 250km. Now change the Initial UT to 139494659.766019. The trajectory will change to reflect a final state Ap of only 108.5111km. Now change the Initial UT to 139494659.466019 and you should see the trajectory jump again back almost to normal at 249.9998km. Now change the Initial UT again to 139494658.466019. New trajectory will be back on the money at 250km. Okay one more UT change to 139494648.466019 - now it's telling me I'm going up to 810.1884km!! BTW the timing is important for this mission cause I want to launch and put my Ap direct opposite the sun so I can go high on initial climb without hitting the inner radiation belt, which is further away on the night side. This also makes me ask if the Sun Vector view option can draw the arrow through the planet and maybe have a length adjustment? Right now I'm just taking a screenshot and using Paint.NET to continue the vector through to the night side

another issue or perhaps just need some clarification on some behavior - check this LVD case file. If you compute a Jacobian you'll see values upwards of 8x10^5 but if you go into the Initial State and set the initial UT to 0, when you recompute the Jacobian you'll see the values are now properly scaled to less than 1 While you have this file open, check the Dynamic Pressure output from the GA. This is what it looks like for me: The double hump is back and it not being smooth on the backside is also strange. Would this have to do with the changes you made back here? Looking back on this though, I realized that there was never any mention made of the switch to the linear model in the change log - neither for the pre-releases or in the full log in the OP Also, if you could get this rocket into an orbit using the linear tangent steering model it would be great to see how that would work. However this is simply me asking a favor. I will get around to figuring it out myself eventually. Was hoping to use it for this upcoming mission but losing my PC for a week has me crunched to get this mission aloft and I'm just reverting back to what I know from previous flights.

hey @Arrowstar have a look at this LVD case file - if you delete the Kerbin III stage and close the vehicle config window the script will propagate to the max 15s. It seems to actually be the SUL-V1 x2 tank. If you delete the SUL-V1 x2 -> LV 303 connection and close the config window, it's okay. If you then delete the Restart x6 tank and close, it's okay. If you remove the LV 303 engine and close, it's okay. As soon as you delete the SUL-V1 x2 tank however the script runs off the deep end Rats, instead of deleting the problem tank after removing the engine and other tank I tried to set the mass to 0 and the script ran amok still. Even 0.0001 didn't work

hey @Katten I've discovered the latest version 1.8.5 under KSP 1.10.1 breaks the settings menu. It shows an Advanced Options (1) and Advanced Options (2) and if you click on either it selects both and shows double options and breaks the UI. Tested with stock + both DLC and no other mods except MM

yup 31.5% if you average out all the values. Spiffy. Ever since I built my own rig for the first time in 2006 I've stuck as close as possible with updating my CPU every 4yrs and my GPU every 4yrs but offset but 2yrs, so every two years I do a hardware upgrade, which gives me enough time to slowly save up and so far it's kept me on pace with games and tech in general, never really felt I had a "slow system" at any point

mobo died last week but I was overdue for a 4yr CPU upgrade anyways since my i7 was purchased in 2016. Now rocking an i9 10900K, haven't done any OC yet nor to I plan to anytime soon but decided to flex it and see the results. Was not disappointed: (01:25:41) Executed mission script in 2.144 seconds. (01:25:46) Executed mission script in 1.083 seconds. (01:25:48) Executed mission script in 0.969 seconds. (01:25:50) Executed mission script in 0.934 seconds. (01:25:52) Executed mission script in 0.987 seconds. (01:25:54) Executed mission script in 0.899 seconds. (01:25:56) Executed mission script in 0.893 seconds. Look forward to unleashing 10 cores on the optimizer...

well, you know the old refrain... "152 bugs on the wall, 152 bugs.... take one down, patch it around, 221 bugs on the wall...."

Launch the vessel, exit to space center. Go into your save file with a text editor, search by “VESSEL” (case sensitive) and if you have the option reverse search from end cause it’ll be the last one. Change situation to LANDED and remove the value for “landedAt”. Save. Reload the save in the game. Now when you launch a new vessel the game won’t detect any other vessel on the runway (or launchpad using same technique). After launching the new vessel and returning to space center tho this will revert and both vessels will be removed upon launch of a third vessel, so you have to do it each time. Best to create a separate save you can reload with whatever you want to remain out there and then launch anything new.

He's talking about this feature to work with AGE: http://ksp-kos.github.io/KOS_DOC/addons/AGX.html <- @garwel this is your answer