Higgs

Simple. They are constantly watching, cataloguing, taking notes and recording everything we do thats linked to anything google or internet. Its not natural and suspicious.

i cant watch the video. for me to watch it, would require me to be apart of the google machine, and i dont trust google. if you placed the video in a location that did not require selling my soul to google, id watch it.

I am going to say this once. Your reply was a 80-20 mix of rude (80) and useful (20). You made an assumption that, I was not being precise. This is far from the truth. I live with 2 hours of the gulf coast of the US. I myself have spent copious amounts of time on the coast, and 99% of the time I am there, guess what, the winds are coming off the Gulf. You also ran right past the point of my post. Given what we all know of how wind works, why is the wind in KSP 180 degrees off of what we see 99% of the time? If Tex, you have no answer that can help with this particular thread, I humbly ask you to refrain from commenting.

Ok, gonna start of by saying this to the mods: if ive miss-located this thread, redirect it to a more suitable home on the forums as honestly, i doubt this is a bug, but, sure does warrant some discussion if only to point it out lol. Now, with that said: Check this out yall. If you have ever gone to the coast you know the wind tends to, most of the time, come off the water. Well, with that being said, what gives at the KSC, I am showing yall a picture that makes no sense from a reality point of view. The wind moving the flag at the pad is heading out to sea, not heading onto land. Now, before anyone barks at me that this is a game, and shouldnt be taken all that seriously, I point out, some of this game is being taken seriously, what with all the work on atmospherics and heating, why not have the flag point as if the wind is coming ashore? just askin. Thoughts below please like i said, what the jebs evil smile is goin on with the winds?

this is not a 100% guarantee tho. MechJeb has some funky bugs in it right now. take for example, the pre 0.90 like say .26 for example and its compatible mechjeb, IT could use launch to rendezvous, now? its just a button taking up GUI space if you ask me, as that button causes odd things to happen. has been so since .90. no one listens...back on point. MechJeb CAN help, DOES help, but, much like a 5 year old, you really need to keep your eyes on it. DUDE! you related to Jeb? Cuz, how the green goo cans did that puppy fly in the new aero?!?

it would seem that what ever bug or glitch or error that was haunting me and my family during KSP 0.90 and MJ 2.4.2 has blossomed into something even uglier. My issues were unending warping, pre launch time clamp firing and random paths to orbit not called for. It seems now that some people are not even getting auto warp to function correctly as well as a few others. My fear has been confirmed, what ever the bug was that no one could find when i brought it up, has now gone thru a full transformation and has reared its ugly head. <runs off crying>

You make me glad I am not the only one seeing errors with mechjeb and a very visible function. According to some, we are doing things wrong. BUT, having used mechjeb from .21 KSP thru .25 KSP <6 full versions mind you> along with my cousin, both of us using the procedures he learned during .21 KSP, Launch to Rendezvous USED to do this after selecting a target: It would calculate your launch window, auto-warp to said window if auto-warp was turned on, then, all the while, it would then alter the inclination box as it was setting up its calculations, then, as the window showed up, it would disengage auto-warp count down the last few seconds, usually from about t minus 10 seconds or so, then hit the milliseconds, then slam on the gas and you were off to the races. I think it needs to be addressed, but again, thats just me.

Well, finding this issue is turning into a sisyphean task. No matter how far I seem to get that boulder up the mountain, it keeps slamming back into me. SO. I ask you, the general population, coders with a working knowledge of not only the games code, but the code with in MechJeb for help. I am going to tear links from my post on page 881, post 8807 for ease of posting. http://www.filedropper.com/outputlog1 test 1 using launch to rendezvous http://www.filedropper.com/outputlog2 test 2 using launch into plane http://www.filedropper.com/outputlog3 test 3 using launch to rendezvous 2nd target http://www.filedropper.com/outputlog4 test 4 using launch into plane 2nd target http://www.filedropper.com/outputlog5 test 5 using launch to rendezvous 3rd target http://www.filedropper.com/outputlog6 test 6 using launch into plane 3rd target http://www.filedropper.com/mechjeb242experimental ship used for all 6 tests, all stock parts save mechjeb http://www.filedropper.com/persistent persistent save file that all 6 tests were conducted in, as well as being my main sandbox. mods needed: proc fairings, novapunch, lazor docking cam, mechjeb http://www.filedropper.com/mechjeb2-2420 the EXACT copy of mechjeb used for all 6 tests. Inside that spoiler as you can see are links. For full information, see page 881 post number 8807. Here is what happening if you are not up to date. I am getting odd glitches with MechJeb. I have been told multiple times I am doing something wrong, that the issue does not exist. Well, riddle me this: if what I am doing is wrong, see: using a visible feature of the mod, namely: Launch to Rendezvous, Launch into Plane of target, Engage Auto-Pilot, of course not in any particular order other than how they came to me as I type, how am I doing something wrong? Further question is: IF, the following procedure has worked from KSP .21 thru KSP .25: Put rocket to launch on the pad, hit M, select a target, hit M to return to seeing the pad, then clicking launch to rendezvous THEN Engage Auto Pilot OR reversing those last two steps as either direction of button presses would work w/out fail for 6 versions of KSP/MechJeb how is this suddenly not viable now in .90? Further Further question: IF the button: Launch to Rendezvous is NO LONGER a viable function, why does it yet remain? Would not logic dictate that, if such a function no longer is valid, it would be removed? Its like building a car today with not only an electric starter but a hand cranked-wrist breaking starter. Granted that comparison is a bit over the top, but the point remains the same, why have an invalid function still there, still very visible? The glitches I am seeing are varied, but, are happening. The glitches are in no particular order: Auto-Warp failing to disengage, Launching into an incorrect inclination regardless of what the ascent guidance states, Launch Clamps pre-firing <this usually goes with the Auto-Warp failing to disenge. I could list more, but, to do that, i would need to make this post far longer, so, instead, I will direct you to another post of mine: same thread as this, page 863 post number 8628 and page 853 post number 8526 for a FULL litany of the issues I am encountering. A word of warning, both of those referenced posts in this paragraph are very very long posts, and contain yet more links to files. A fellow player, who will remain nameless messaged me with the following message: "I have the same issue as you do (or did). Mechjeb auto fires even if I do not hit the timed launch option. I also have a problem where my planned orbits move all over the place with larger rockets so it might not be entirely a Mechjeb issue but I do not know for sure. Anyway, did you ever find a fix? Didn't feel like reading where everyone was bashing you for a legitimate problem just because they don't have it." I have obviously removed this persons identifiers from this post out of respect for the player. IF said player sees this post and my use of the message they may feel absolutely free to state who they are. With all this said, I seek anyones help on this. Please, I beg you, I know my posts are long, link infested things. I have been suggested to not use mechjeb, but, that is not going to happen, as it is a key mod to my game, and I am sure you would not fly w/out mods you see as key or vital to your game, so dont suggest the same to me. I am willing to completely delete my game and start from scratch with new mods and the like if the issue is in my copy of the game, or delete the save file and start again with that, but, both are drastic moves, and I hope for a more...easy solution. Also, if it wasnt clear, I am not a programmer, so, asking me to alter code isnt a wise thing, as that can lead to me screwing something else up lol. I am at my very wits end with this, I have been chided, derided and maligned thru the course of this issue. All I seek is a resolution to this problem, what ever that may be. Please help me get back to enjoying a game I love. Regards and pleas for help, Higgs

The droopy nose has NOTHING to do with the delta wing of concorde. I found a picture of a view from the Concorde's Cockpit with the nose in the "droop" position. Not exactly a picture window view. The nose of the Concorde is exceptionally long and pointed. It has to be, as you did point out, Concorde was capable of supersonic flight, and the nose needed to elongated and pointed to cope with 1400+ MPH speeds. Take a look at the view: Like I said, this isnt because of the wing. its because the engineers had to compromise with the aircraft and flight crews needs while actually on the ground or coming in on final approach. They could have chosen to NOT do this, but, then, you would have had a LONG aircraft with almost NO visibility, and absolutely NONE for about 15 feet from that window out ahead of the aircraft.

Sarbian, expect a PM in response from this post of yours. Respect and Frustration, Higgs

1. so THATS how those spoilers work. Never have been able to get them to function lol. 2. given the time table in which i have been seeing issues with MechJeb brevity isnt my friend anymore. Ive found that I just need to bludgeon my issue with as many details as I can think of. Does this make for some...LONG posts? absolutely. 3. me and "dev build" mechjeb variants do not get along with them usually trying to microwave my saves. I had one nerf a save which stunk. And, for the record, 2.4.2 that was given on filedropper, was the version I was using direct from the curse webpage. at this point Jacke, I am nearing the: I just give up" phase of all this as it has hamstrung my ability to play. You do make one good point, and I sincerely HOPE that all of what I am experiencing is a facet of what you said: that there is a tremendous amount of things that got whacked with the change stick. if it ISNT part of that, it needs to be hunted down, regardless of just how rare this is proving to be. did it? if it did, thanks jacke!! all of this being said, is the error 1. mechjeb 2. my persistent save 3. my copy of the game? 4. something other?

Hello again. Long Post. I wanted to test MechJeb again after being away from it for about what 11 days give or take. Here is what I did prior to starting the 6 tests you see below: I deleted MechJeb 2.4.2 from the game. Deleted its dev variant. Deleted the zip files as well. I then went and re-down loaded MechJeb 2.4.2 and placed it into the game as per install instructions. I also, will re-list the version of KSP for these tests below this introduction as well as mods that are installed. KSP and the mods as listed are the most up-to-date versions I can locate for KSP 0.90.0.705. I was attempting to see if my prior issues would occur. Those being: Failing to launch at the correct time, Pre-firing the Launch Clamps, Getting Locked into Auto-Warp. I was able to varify only a few of these, and two of the issues happened only ONCE out of 6 times. I want to go on record here, stating, that, there is an issue with MechJeb, as this was a fresh install of MechJeb and some of the bugs once again occurred. Below you will find: 6 Tests, their notes, and the related Output Log for that test. Below the tests and their respective logs, you will find a link to my vessel, a small imgur album OF said vessel. Below THAT, you shall find a copy of the persistent save file these tests were conducted in. Below THAT, you will find a copy of the MechJeb 2.4.2 that was used for these tests. My request is this: Is my save itself borked or possibly the game? If it is either, a full restart of the save and or game would be sad, but, would be done. If 100% needed, I can ask Steam to provide me with a fresh copy of the game, and I can re-install my mods and go on with my life in KSP. If this is in fact an issue with MechJeb, I hope it can be found and repaired as it is my fear that this will propagate further down the road and perhaps become a big issue at some point. To those who would suggest I learn to fly w/out MechJeb, I state this: Why should I? I can in fact perform all the required actions for a mission, just not as smoothly as MechJeb, but, prefer to use MechJeb. To me, MJ is as vital to my personal enjoyment of the game as what ever mod<s> YOU see as vital components to YOUR space program. If your a fan of FAR and I asked YOU to learn to fly w/out it, you would rightly laugh me right out of the conversation. As such, my use of MechJeb is akin to your use of what ever mod<s> YOU prefer to use. Second On Record Statement: I realize that my issues are exceptionally rare, with only one or two other players speaking up and saying they are seeing similar issues. Just because these issues are NOT replicating for you in YOUR save files does NOT mean they are NOT happening in MY save file. I am trying to provide all of you with as a detailed account of my findings tonight as I can, as well as provide all the relevant files to aid in coming to some sort of conclusion and action plan for resolution of this and its similar issues. I am seeing this happen, and it is frustrating as it is making the game unenjoyable and unplayable for me. I do not wish to be forced to wait for .91 to come out and then HOPE that these issues somehow are resolved when Sarbian or r4m0n upgrade MechJeb to 2.4.3 <assuming thats the logical numbers progression for the next update of KSP when ever that is>. KSP 32 Bit for Windows. 0.90.0.705 BETA Mods: MechJeb 2.4.2, Romfarers Lazor Docking Camera, NovaPunch, Procedural Fairings. Again, all mods updated to current versions for 0.90.0.705 KSP Beta. 1. First Test: Target: Polar Orbtial Sciences One. Mission test MechJeb 2.4.2. Test flight 500km Polar orbit targeted to station. Launch To Rendezvous. MJ Prefired Launch Clamps and stayed in AUTO-WARP thru launch window. Terminating Auto-Warp resulted in a launch but so much time had elapsed that being on course to the target was not going to happen. Reverted to VAB, then to Main Menu. Closed KSP. Logged first output log. Test One Output Log: http://www.filedropper.com/outputlog1 ----------------- 2. Second Test: Target P.O.S.O. Mission test MechJeb 2.4.2. Test Flight 500km polar orbit targeted to station. Launch into Plane of target. Results: Launch into Plane proved to work...this time. Launched smoothly...for the most part...perhaps I was overzealous with my launch clamps, as it caused it to buck wildly as it cleared. After Launch tower clear, launch went as expected and fairly smoothly. Discovered I need some RCS tanks on the test vehicle, but, after 2 tests, with 1 full mission profile, I think, I will not add them in order to keep things all equal. Should be noted that with each iteration I am shutting the game down completely. Test Two Output Log: http://www.filedropper.com/outputlog2 ----------------- 3. Third Test: Target: K.I.S.S. Mission test MechJeb 2.4.2. Test Flight: 500km equatorial orbit targeted to station. Launch to Rendezvous. Results as was expected, MechJeb failed to perform a Launch to Rendezvous. I chose my K.I.S.S. which is in an equatorial orbit at 250km. To stay even with tests 1 and 2, I launched to 500KM or rather, targeted that altitude. Of note: There is an issue with LtR command. In all prior cases before KSP .90 no matter the target a LtR command would alter the orbital inclination box to match the targets orbital inclination. Now, it is not doing so. Perhaps the issue, or atleast ONE is with the coding of that particular function of the 2.4.2 mechjeb? That i suppose is for the coders to figure out. Suffice it to say, the next 3 tests will be interesting. Also of Note: Auto-Warp engaged and disengaged as per mod design. Test Three Output Log: http://www.filedropper.com/outputlog3 ----------------- 4. Fourth Test: Target: K.I.S.S. Mission test MechJeb 2.4.2. Test Flight: 500km equatorial orbit targeted to station. Launch to Plane. Results as was expected MechJeb performed a full mission profile from launch, to orbital insertion, rendezvous to 100m from the target to a deorbit. As with tests 1-3 once the test was concluded, a revert to VAB was performed, followed by a quit to main menu then full shutdown of the game. Log was obtained and stored. Test Four Output Log: http://www.filedropper.com/outputlog4 ----------------- 5. Fifth Test: Target: K.O.S.C. Mission test MechJeb 2.4.2. Test Flight: 500km inclined orbit, 43.47 degrees inclined, targeted to station. Launch to Rendezvous. Results as expected, the LtR failed to alter orbital Inclination box. Ship did launch, and as expected got hung up on the launch "tower" and flew oddly, but, MechJeb recovered and I allowed the flight to go to stage sep and gravity turn, however launched into the prior tests inclination. Given that Launch To Rendezvous is now as of KSP .90 failing to alter the inclination box, this was expected. Test Five Output Log: http://www.filedropper.com/outputlog5 ----------------- 6. Sixth Test: Target: K.O.S.C. Mission test MechJeb 2.4.2. Test Flight: 500km inclined orbit, 43.47 degrees inclined, targeted to station. Launch into Plane. Results after 6 tests total and the third using Launch into Plane were as expected. Full launch profile, orbital insertion and rendezvous to 100m of the target were as completed as expected. I initiated a deorbit burn, then reverted to VAB, then main menu and finally closing down KSP completely. Test Six Output Log: http://www.filedropper.com/outputlog6 ----------------- I want to state on the record: There IS an issue with MechJeb 2.4.2. There is no denying this. The issue that I can confirm at this time, is this. In prior KSP versions for MechJeb from KSP .21 thru .25 MechJeb would perform any flight operation you asked of it, regardless of what button or combination of buttons pressed there in. It would, if you chose, any of those stations and orbital inclinations from my 3 tests above as targets for orbital inclinations, would adjust the parameters for MechJeb accordingly. If I chose Launch to Rendezvous lets say, using the Polar orbital station, it would adjust the orbital inclination to match the targets inclination and launch accordingly. Now? It does not. I think this is an error in MechJeb to not do this. Launch to Plane now, oddly seems to function as LtR used to. This begs me ask: If Launch into Plane now functions as LtR did, why still have LtR on the mod as now, a launch to rendezvous requires some tweaks user side to work as desired. This isnt a big issue, but, it is something to take note of never the less. Also, I have as yet to reproduce prior reported issues, but, I will continue to track and record as I go along. My test vehicle is 100% stock with the single exception of MechJeb 2.4.2 being bolted to the side of the capsule. I have an RTG burried in the capsule itself for power. I have now provided with this post, 6 (SIX) varying output logs, each is provided with its particular test. Included below this, is the vehicle as well as the related persistent save file. What I ask now is this: what can be done to repair this issue. Sadly, the steps to reproduce the Auto-Warp lock, are unknown to me, as with each test, I did the same exact steps: Chose my launch vehicle inside the VAB, hit M, selected my target for the test, hit M to return to the visual of the vessel on the pad, hit the Launch to Rendezvous/into Plane (depending on which iteration of course) and then hit engage autopilot. ONLY ONCE this time in 6 tests did it Auto-Warp lock with a launch clamp pre-fire and that was test 1. I can upon request perform these tests again using the steps: engage autopilot THEN tell it which launch mode to use. Vessel Craft File: http://www.filedropper.com/mechjeb242experimental Picture of Mechjeb242experimental vessel: as you can see, I perhaps over did the struts and clamps, but, I wanted to make absolutely dead on certain that it wasnt going to sway in the SLIGHTEST on pad. IF you use this thing to test my tests, be warned: it is TOUCHY leaving the pad with all those blasted clamps. The persistent save file that the above tests were conducted in: http://www.filedropper.com/persistent Please take special note: IF you wish to actually USE this persistent save, you MUST have: MechJeb, Lazor Docking Camera, Procedural Fairings and NovaPunch installed or the file may act in undesirable ways and contaminate the bug hunt. The copy of MechJeb 2.4.2 that was used for these 6 tests: http://www.filedropper.com/mechjeb2-2420

Steve, wiping my game is a drastic step. One, for tonight, I am unwilling to take. I would like to state on record: I dont need a .25 copy to demonstrate proper behavior, as proper behavior can be shown by words in this case. Target any object you have in orbit. Tell MechJeb while on the launch pad awaiting launch, that you wish to go to an orbit that is ABOVE your target. Say your target is 300km circular, Polar. Tell it: 500km, then click, dealers choice: Launch To Rendezvous and engage autopilot, OR Launch into Plane of Target <either are acceptable launch criteria> and watch as the following occur: MechJeb <this is assuming you are say 90 degrees off plane from your target> engages auto-warp, bringing the KSC into a favorable position relative to your targets orbit and position with in that orbit. MechJeb keeps slowing auto warp down as the count draws to t-0. Finally at say t-10 seconds it cuts to 1x normal time scale and the clock runs to 0. MechJeb then <the following assumes: auto-stage has been enabled, launch to say rendezvous for this and your climbing to a 500km POLAR orbit> initiates launch. Reaches your gravity turn assigned altitude. MechJeb triggers your staging at the correct times and now, you are coasting to edge of atmosphere as it has finalized your AP to around 500KM give or take a bit for vehicle oddities during flight. You achieve AP and mechjeb has oriented you into the correct position for circularisation burn. With this done, your launch profile has concluded and MechJeb functioned exactly as advertised, anticipated and expected. The above held true for all versions between .21 KSP and .25 KSP. For me sadly, this after multiple reverts to both launch and vab is not possible. and again, with the 380 dev build, not even THIS was possible. Page 853 post 8526 contains several output logs and a persistent save. a page or so back has new output logs and a more current persistent. to use my persistent: mechjeb 2.4.2, novapunch, lazor docking cam, proc fairings.

For the record. I am in Steam Version 0.90.0.705 and have tried MJ 2.4.2 and Dev Build 380 i think it is. For the second record, Mechjeb that is compatible for .25 FUNCTIONED EXACTLY as EXPECTED. Issue lies with MJ 2.4.2 and Dev Build 380. Trying to duplicate this set of issues on a MechJeb and KSP NOT of versions 2.4.2 and KSP 0.90 is a task that is not needed, as, I have stated many times, in the litany of posts where I list the versions in which MechJeb functioned exactly as predicted and expected are not relevant to the issues I am seeing in .90 with the current dev build and MJ 2.4.2. Thanks for trying Star, I really mean that. side note: i KNOW my issue is exceptionally rare and seems to be effecting only me. I have given multiple copies of my persistent save, multiple output logs. All i want to know is, is this issue because of a corrupted save on my end? I honestly do not know. Is this something because of the new parts in KSP? again, I do not know. Is this something in the code of mechjeb? again, I do not know. I am not beyond unwilling to totally nuke my copy of KSP and start from just opening the box again, IF the issue is ON MY END, but, I cant know that if you folks dont help me. I KNOW you folks are not seeing and are having issues even trying to REPLICATE the issues I am seeing, but, that does NOT mean they are not happening. Why would I be putting myself out on display if they were not happening? I am honestly wanting help. Please help me out.

It would seem I am FORCED into reposting my most recent issue with MechJeb in the blind hopes that Sarbian or someone with computer programming skills can find my issue with mechjeb. http://forum.kerbalspaceprogram.com/...v2-4-2/page853 THIS is where you can locate the initial batch of output logs as well as a copy of my persistent save as of THAT date. here is where you can get a fresh copy of my output log from last night: http://www.filedropper.com/outputlog_6 here is where you can get a fresh copy of my persistent save from last night: http://www.filedropper.com/persistent_3 With the reposts of my saves/logs out of the way, I begin again with reposting my most recent issue with the Dev Build 380 i think it is. I begin this again, by stating on record, I have used procedures that I know to work and have worked for mechjebs that are or rather were compatible with KSP versions: .21, .22, .23, .23.5, .24, .25. Those procedures as far as the current issues at hand: Launch to Rendezvous and Launch into Plane of Target. 1. IN ALL PRIOR VERSIONS, regardless of orbit, inclination or any other factors, going to the map, selecting a target, and then giving the 2 commands: Launch to Rendezvous and Engage Auto-Pilot, would for the record, fill in orbital inclination and then fly the appropriate launch profile into the proper plane and orbit. Inclined, Elliptical, polar, equatorial, retrograde, prograde did not matter. It would find and fly said path. .90 and mechjeb 2.4.2/dev build 380 it is sketchy at best if it does this. 2. IN ALL PRIOR VERSIONS, regardless of orbit, inclination or any other factors going to the map, selecting a target, and then giving the 2 commands: Launch into PLANE of Target and Engage Auto-Pilot, would for the record, fill in the orbital inclination and then fly the appropriate launch profile into the proper plane and orbit. Inclined, Elliptical, polar, equatorial, retrograde, prograde did not matter. It would find and fly said path. .90 and mechjeb 2.4.2/dev build 380 it is sketchy at best if it does this. 3. I can or rather could, get one to two flights in where things would act as expected. But, multiple reverts into VAB or back to the Pad for fixes or retries would degrade the functionality of MechJeb. When I ran the DEV BUILD 380, regardless of what I targeted, and as of lately, trying to sort this out, I kept choosing my station in POLAR orbit <an album to follow this list, and before you tell me it is doing what I told it to do, because orbital inclination says 0 degrees, please remember your mechjebs and what it does when you select a target for a times launch, it is SUPPOSED to rewrite that box. The dev build does not, at least for me> it would fly an equatorial orbit, or in the case of the pictures, TRIED, had a sketchy staging issue and the thing got wonky and flew wonky. FOR THE RECORD, I chose my polar orbit station, CHOSE LAUNCH INTO PLANE OF TARGET then engaged the autopilot. it saddens me to have to repost this particular issue. I also state, I am sick of being told I am in the wrong with how I am using the mod, that this is somehow MY fault. The issue is real. Just because YOU are not having this happen does NOT mean that I am making this up. I have come to believe that we are all here because we love this game, and that we come together to HELP each other.

Jacke logs and persistent save have already been proffered. Page 853 post 8526. If a rebuild is what i need to do so be it, but before i go to that extreme i would like someone with coding skills (sarbian or r4m0n seeing as its happening with mechjeb) tho the issue is starting to crop up less but has not fully dissipated to see if something shows in those files. Thx again

the HIGHEST ever recorded G-Force WITH SURVIVAL happened in Ft Worth Texas in 2003 with an Indy Race Car Driver surviving 214G's of deceleration. Citation: http://en.wikipedia.org/wiki/Kenny_Br%C3%A4ck

@kowgan it has happened in a new save. like i said, i think something is hiding in the code of either mechjeb or my persistent or both but, i lack the skills and knowledge to find it, which is why i keep coming back here

i would like to ask again: does anyone have ANY idea what is causing my issues with mechjeb? the long run down of everything, including output logs and a copy of the persistent save is available here: http://forum.kerbalspaceprogram.com/threads/12384-PART-0-90-Anatid-Robotics-MuMech-MechJeb-Autopilot-v2-4-2/page853 it is post number 8526. I deleted the craft from kerbalx. the output logs/persistent however are still valid. I am getting mechjeb to function right for periods, then, it goes psycho on me as listed in the rundown at that link. I have 0 clue what is going on. I am tired of this issue. I just want to play this game and be happy, but, this issue is not a happy one. For the record, I am not a programmer, so, explaining things to me by showing me lines of code may as well be speaking to me in chinese or arabic for all the good it will do. Look, I will boil my question down to the following: 1. Is my copy of MechJeb some how borked? <assuming this sorta thing shows up in the output logs or save file> 2. Is my PERSISTENT save borked? <assuming that can be determined by mucking about in it> 3. Is it some combo of the two? 4. Did downloading MechJeb 2.4.2 twice on accident do something to the first download <the one I actually installed, also, my lack of knowledge of code may make coders laugh at this question, and good on you if it does, im at a loss here> 5. please help <give sad sad sad sad puppy dog eyes>

Plenty of power.

Once manhandled into orbit the thing performed as expected. It's not resolved yet, it has something to do with being on pad

Serbian can you explain WHY in MY copy of KSP mechjeb is doing the things it's doing? OBVIOUSLY it's behaving for YOU but for me, it's decidedly not behaving and exhibiting all things I have mentioned? I know why that rocket flew apart btw, over powered SRBs combined with inadequate strutting. But NONE of this speaks to why, mechjeb did the following: 1. Premature launches either hours or seconds (varies by try) prior to window. 2. Stays stuck in Autowarp thru MULTIPLE LAUNCH WINDOWS 3. Starts glitching for ME after multiple reverts 4. Is not glitching for you look have access to my persistent save what am I missing? Is my save borked or is my copy of mechjeb borked or is mechjeb borked? THAT is what all this boils down to. What is and WHERE is the issue in all this.

I know how it is SUPPOSED to behave. I ALWAYS let mechjeb handle it all. Last night it just kept warping nonstop past each window. Today after multiple reverts mechjeb started launching the above pre window.

You folks called me crazy, said there is no issue with mechjeb. Well, I am happy to say: YES THERE IS. I have concrete PROOF in picture FORM. This is an imgur album. One picture shows you my ship, which is ALL STOCK with the ONE SINGLE exception of MECHJEB. The rest show the target in a POLAR ORBIT, yes, this is a NEW save, and the target, is a 2.5m probecore, 2 2.5 meter STOCK batteries, a STOCK 2.5 meter SAS wheel, a STOCK ORANGE TANK, a Main Sail Engine at 350KM POLAR ORBIT. The pictures speak for themselves. Now, PLEASE HELP ME FIND THIS BUG AND ITS SOLUTION. Steps: 1. Loaded Game 2. Made a NEW sandbox Save. 3. Made a simple target to use, launched it to 350KM POLAR Orbit. Consists of the description above. 4. Made the Test Rocket, description is in the album. 5. Did a test launch, everything went well. 6. Reverted to LAUNCH <as this seems to CAUSE the issue> 7. Launched AGAIN, everything SORTA went well. 8. REVERTED AGAIN TO LAUNCH. 9. Laughed as MECHJEB GAVE UP WAITING FOR FULL TERM, Launches Prematurely. 10. Reminds people of the order in which I clicked buttons: LAUNCH TO RENDEZVOUS, ENGAGE AUTO-PILOT 11. Makes Imgur album, posts below. 12. Makes THIS post. 13. Embeds album. 14. waits for someone to help find this bug. Now, I am not TRYING to be rude, but, I am SICK of being rebuffed, treated with disrespect as people claim that either it is MY ship, or ME. I have undeniable PROOF there is an issue. Now, OBVIOUSLY this is NOT occurring for EVERYONE, but, it IS happening for ME. THERE IS a PROBLEM with MechJeb. My ONLY guess is it has SOMETHING to with the game going to BETA mode. I am NOT a coder and thusly have 0 clue. But to outright dismiss me, call my crafts pieces of <expletive word was implied by a diff forum member> and then mock me some more, by saying I am doing something wrong, is insulting and hurtful. I am having an issue that is causing me to NOT be able to play a game that I love. I am beseeching ALL OF YOU for help, instead I am treated like scum or ignored or something else. There is CLEARLY something wrong with MechJeb, and I am TRULY SORRY if my finding this issue has insulted you, but, do not be derisive to me for it. Help me solve this. We all love this game. I am willing to BET MY ENTIRE GAME ON IT. But, again, to be anything other than helpful in this matter is, well, not helpful, and it is not the way of the community in which I hold in such high esteem.

I will ask again, even going in launch plane then engage why does it not shut autowarp down