linuxgurugamer

Can you please download 0.7.0 and manually install? I'm wondering if the bad version might have messed up some settings in the save file

The Tantares engines you are using (RD-107 & RD-108) have a very unusual vectoring range, one direction is 0, the other direction is 10 degrees. Apparently GravityTurn has problems controlling a vessel with these engines. The earlier (1.8.1.2) version did decouple the first stage properly, a second test of 1.8.1.4 showed that the radial decouplers are being triggered properly, I think I had missed the Auto Stage setting in the first test. Both versions had problems controlling the vessel.. Just as an FYI, MechJeb was able to control this vessel very nicely. So, @chris-kerbal & @antipro I'm going to have to ask that you do two things: First, zip up the entire save folder and get it to me, and then zip up your whole GameData directory (without the Squad folders). Something is happening, and I cannot replicate what's going on. Send me the links via PM please. It's going to be a big file, but at this point, it's the only way I can think of to try to replicate the problem. If I'm lucky, the save file by itself will let me replicate it, but I'm at a loss as to what's going on.

So I managed to get all necessary mods installed, and did a test launch with this. It was a strange launch, kind of wandered all over the place, and I did see that the radial decouplers did not automatically decouple. But it did make it to orbit. I'll compare against 1.8.1.2 later to see the differences. Also, you and @antipro, could you test against 1.8.1.3? Would be helpful to know if that was ok or not. Thanks Edit: @antipro I saw that you had tested against 1.8.1.3. Could you make those craft available again for download?

Could you do it as an exported modpack from CKAN? Would make it easier for me to get set up, other wise I'm going to spend a while setting up

@Beale I’ve had some reports about vessels made with this having problems with GravityTurn. I’ll be looking into this in the next day or so, but was wondering if you might be able to point me into a specific area where your parts may differ from stock parts?

There are apparently multiple versions and parts to the Tantares mod. Which ones did you have installed?

You are too fast, I was just checking the first post :

You can bide them without doing the permaprune. I think the command is ctrl-rightClick while hovering over a part to bring up a menu where you can specify blocking a part. In the editor (VAB or SPH), hold the Alt key while clicking on a part. A two line menu will be shown, giving you the option to block the part in the scene you are currently in (VAB or SPH), or block it entirely:

Hmmm. Looks like im going to have to recompile for 1.11. Not going to happen right away, I have to finish up a bug fix on 1.10.1 first. I’ll see if I can get something set up soon; I may be abe to do a simple buils and provide the dll in a simple zip in the next few days.

No, lets just agree that I was blunter than I should have been, and maybe you read more into what I said than was meant. Other than Tanteres, what other mods do you have installed? Im going to set up a new install with just Tanteres in order to try to replicate this problem.

I apologize if you've taken offense, my comment was (IMHO) fairly clear. CKAN Metadata is just that, metadata for CKAN. If you look at CKAN, it list the mod version the way the mod author specifies it; until you mentioned it, I didn't even know it was a thing. I do intend to find this problem, but I need to replicate it first

New BETA release, 6.0.0.5 Fixed missing science (there was a text filter blocking it) https://github.com/linuxgurugamer/KSP-X-Science/releases/tag/6.0.0.5

Thanks. I was actually able to replicate it myself late last night. No idea what's wrong yet, although I did merge in a PR from someone else. The good new is that I recompiled the older version, tested it and it works, so I have both a working and non-working copy, once I get a few hours to work on it, I should be able to get it figured out.

This is helpful. This is not. I have no idea what those version numbers you list are. I vaguely remember the author may have used that version number format, I do not. And its odd that you used this format, because in earlier posts you did refer to the version numbers that I use. And I did try your vessels before, so don’t think I am belittling your report. I’ll take another look at this issue. It’s very odd that your vessels work for me but not for you, even in a clean install

Too heavy?

That's very odd, this has nothing to do with graphics of any kind

The patch listed in this post seems to fix the problem, it does appear to be an issue with Kronometer and is being looked into:

Thank you, I'll pass this on to @flart

New release, 0.7.1.1 Reverted keycode change in 0.7.1, was locking up the keyboard New release 0.7.1.2 Fixed revert properly

This should help. But if you can test the previous version, it would be helpful.

You will contact him? I did open a ticket on the Kronometer repo on Github, let me know if anything else is needed.

Can you get me the coordinates (latitude/longitude) for those locations, please

Last day was day 365. It's a bug, but since this is JNSQ, which uses Kopernicus, which uses Kronometer, the real question is where the bug is. My money is on Kronometer, but I'll let the people who know better figure it out. It's pretty easy to replicate, just open a JNSQ save file and change the UT time in the FLIGHTSTATE stanza to just a bit short of 1 year, a good value is: 15767990 which is (if I got my math right) 1 minute before the end of the year

So the real question is, does the previous version do the same thing?

Which is why I opened an issue for Kronometer on Github, I saw that it was a possible culprit after I made the other posts