JPLRepo

Yes. Try at least reading back the last page or two. In this. Are its on this page. https://github.com/KSP-RO/TacLifeSupport/issues/63

Yeah it is. And it got answered here already:

You mean @illectro I asked for more info and didn't get a response. He can always PM me. Without logs.. what do you guys want me to do? I'll look into it, but I am on holidays as I said and would rather be at the beach. I'll see if I can reproduce myself, or whether I update the dev version in the meantime until I get back. Unfortunately, as I am halfway through doing the other things mentioned. I could look to fix the tracking but then introduce half a dozen other bugs for the incomplete changes. I could look to cherry pick the changes to only fix this problem, but that takes time, so again, not time I currently have until after the holidays.

Not familiar with that pack but assuming it's using Kopernicus it should work. You are running the dev version of this mod then. What do you mean by "track"?? Planets visible as a dot, with no orbit lines in mapview/tracking station sounds completely normal (as that is the starting state for undiscovered celestial bodies) until you find them using a telescope. Make the planets completely invisible as per previous comment. I am about mid-way through adding this to the mod: - An Observatory expansion for better information about undiscovered bodies. - A better system for finding undiscovered bodies. - Contracts for undiscovered bodies So to answer your question all of the above ^, then tested and working.

Probably, no reason why they can't.

Not unless you do a code change and send me a PR

Sounds like another USI incompatibility issue.. I have been getting a few of these lately with a few of my mods. Seems USI has made changes to the way it works a lot lately, and it's getting a lot harder to keep up with all the changes in USI. I am currently on holidays, So I can look at this in the new year when I get back.

It does nothing unless another mod has been designed to use this mod. It depends on how the other mod implements it.It can be just a simple overlay type setup like the stock ones (but depends again on the mod and what overlay they have created). OR it can support proper shaded transparent windows, again depends on the mod using this mod.

Nothing in logs... Assume you mean the telescope is not finding any bodies? Targeting them and pointing at them, then firing and nothing is happening? I did find a bug in the last dev version I did, and I did want to get a version out before I went on holidays from day job (Which I am now on). But I'll see if I can get something out in the next day or two as a new dev version for you to try.

What DLL? There is a Dev version here: https://github.com/JPLRepo/ResearchBodies/releases/tag/V1.9-Develop I am hoping to get a new version out today my time before I go on holidays.

Progress update.. slow and steady. I haven't made anywhere near as much progress as I would have liked. I'm going to work towards getting an update out with just a few of the contracts features to begin with and progressively build on it I think.

Is this directed at me? Read the OP about CKAN.

There is still a bug with rescue kerbals contracts... (when they are to be rescued from EVA/Surface). Forgot about that use case. https://github.com/KSP-RO/TacLifeSupport/issues/63 Accept these contracts at your own peril until I can fix. I think this is a hangover from way back... when TaranisElsu used a spreadsheet to create the part parameters. I'll round them for the next version to avoid future issues.

You will have to take that up with the author of that mod.

As I posted the other day guys. Hang in there. I've been working on it over the weekend. I hope to get this mod in shape within a week. Already fixed several bugs (including the planet occlusion for the TB-75) and got the first contract working. Now that I have that framework done for the contracts the other contracts should be quick and then there's a few other peripheral things to do, like the Observatory UI.

Glad you figured it out... had a hunch it was docking port related.

None. I'm assuming the message you are referring to is the AVC version checker when KSP starts up, and as you have said you are still running 1.2.1 it will continue to tell you to upgrade to 1.2.2 because that is how AVC works. If you don't want the message and remain on 1.2.1 then go to the ThunderAerospace\TacLifeSupport folder and remove MiniAVC.dll and TacLifeSupport.version and the message will go away. And, it won't let you know when TAC LS is upgraded again either.

You have to create new OverLayMasks for the stock parts to only allow the windows to be see through. No one ever has.. as it's a fair bit of work.

FYI. The 2.5M Sabatier is broken due to a typo in the config file. I'll do a fix next few days. In the meantime you can add the missing "}" if you are savvy enough. https://github.com/KSP-RO/TacLifeSupport/issues/62

Bingo!. How about @The Raging Sandwich

Props (stock) will only work if part of an InternalModel.

Transferring food works fine for me. Bit more info on what you are doing what your vessel looks like, etc. And possibly a log. Are you transferring across docking ports and you have crossfeed enabled?

In that case initialize your Event before MainMenu (although I haven't tried)... as most use cases for this would be after MainMenu.

Yes. Unless you reference it first it won't initialize. And the first time you Fire it it won't work.

V1.4.4.0 published for KSP 1.2.2. Fixes a bunch of stuff. See changelog in the OP.