Issue for OPS1 Ascent

[FlandreScarlet1]

for some reason the once the the srb are decoupled after 1:55 the main engines of the rs-25 switch off and im also targeting to intercept the mir space station which idk if thats the reason.

[giuliodondi]

Can you tell me if the main engines shut down before or after the script crashed with the error showed in your terminal? I can see that the throttle is zero for some reason. I suspect that something else caused this, maybe even an inadvertent keyboard press, and this caused the script crash in turn.

Nevertheless, I'd like to recreate your scenario for testing. Please post here the contents of the launch script shuttle.ks that you ran, along with the parameters of your target station. For conformation: did you launch from the Cape?

[FlandreScarlet1]

after the boosters separate the main engines shut down before the script crashes and the throttle automatically switches to zero automatically without me even touching anything on my keyboard. with the error showed in my terminal

[FlandreScarlet1]

this was the script i used exactly used for the same one in the picture

@LAZYGLOBAL OFF.

//Launch Settings

GLOBAL target_orbit IS LEXICON (
"periapsis",30, "apoapsis",220, "cutoff alt",112, "inclination",40 ).

// uncomment this line to trigger automatically an engine failure. Alternatively shutdown manually one of the engines //GLOBAL engine_failure_time IS 150. //GLOBAL engine_failure_time IS 230.

//TAL site selection is now automatic. Uncomment this to select a specific TAL site //GLOBAL TAL_site is "Zaragoza".

GLOBAL logdata Is true.

RUNPATH("0:/Shuttle_OPS1/src/ops1_launch").

[FlandreScarlet1]

these are the logs i gotten Space Shuttle Discovery STS-91 RS-25A_log.csv Space Shuttle Discovery STS-91 RS-25A_log_old.csv

[FlandreScarlet1]

the parameter of the Mir space station is exactly the 51.6 degrees but at night was at -51.6 in ksp RO 1.12.5 and was targeting -51.6 degrees

[FlandreScarlet1]

and yes i launched from launchpad 39a in cape canaveral

[FlandreScarlet1]

[FlandreScarlet1]

PE for mir is 354,000 meters and for AP its 374,000 meters the something in orbit like it used to be in real life but for the target and its at -51.6 at night for cape

[giuliodondi]

these are the logs i gotten

FYI these logs must be of some RTLS abort you did, based on the timestamps, the altitude and thrust trends, as well as the latitude/longitude positions. so I'm not sure there will be something to learn from these.

I'll do my own tests and write back. In the meantime, please check if you have installed any third-party mod that controls throttle position, maybe when you cross an altitude threshold.

[FlandreScarlet1]

these are the logs i gotten

FYI these logs must be of some RTLS abort you did, based on the timestamps, the altitude and thrust trends, as well as the latitude/longitude positions. so I'm not sure there will be something to learn from these.

I'll do my own tests and write back. In the meantime, please check if you have installed any third-party mod that controls throttle position, maybe when you cross an altitude threshold.

I checked if i had any third party installed avionics throttle controlled and i dont have any but i do have mechjeb which i use to for throttle not to be lowered to less than 5 percent

[giuliodondi]

I was able to reproduce and find the problem, Nothing to do with throttle, it was the script that crashed first because of a targeting bug that only showed itself when a target vessel was selected.

I was able to perform successfully a nominal ascent to a target in a similar orbit to your scenario:

Please update the launch script files and test if it's fixed on your end as well. Take care that soon I'll be making furher changes here once I'm done working on the new Shuttle OPS3 script.