JPLRepo

No. The IT guys are looking into it. But it requires recovering just those threads from very large backups then re-applying them to the forums.

Thanks for the feedback. I'll look at a pop-up then. Yes, I've been thinking maybe them completely invisible will work once I have the contracts in place (about 70% there). There will be a contract that is available at the new Observatory facility at the KSC that will scan the skies to find new bodies. There will also be a contract for doing the same thing with a telescope in orbit. So I think the totally invisible won't be an issue. Of course you could just point the telescope and keep clicking and hope you find one as well. The new version will not be just throwing funds at each stage any more. You will not be able to do that at all. You will have to complete research contracts or scan over a period of time with a telescope. Of course - all this only works in career games. For sandbox - well the mod isn't really designed to be played in sandbox anyway.

You can raise a request on the bug tracker (feedback). You do know Mu (Mike) does not work for Squad any more?

The shader is not in parttools. I am unable to divulge further details. Sorry.

V 0.12.8 released. See the changelog in the OP for the changes and details. EDIT: Probably worth noting here though the two biggest changes. Change to the way rescue kerbals are handled. Added EC consumption setting and functionality for EVA kerbal's lights. See the changelog for more info.

I have not used KW Rocketry in a long time. But as TAC LS operates correctly without it my guess would be there is something wrong with KW Rocketry that is causing this.If you can supply logs and that contain information about what version and other mods you have installed as well it may contain messages that may help to identify the problem. Without your log there is not much I can do for you. See the OP for info and a link for where to find your logs and how to supply a link to them. https://github.com/KSP-RO/TacLifeSupport/issues/71

Oversight. I'll look to change it. You can adjust the Specialist parameters in the part config. or turn it off completely by setting "UseSpecialistBonus = false"

TAC LS has a similar system available to players.

Work on re-texturing the parts has started. Feedback and thoughts welcome.

Thanks for the info guys. Hmm, it could be as you are using planet packs that the more distant planets do need more accurate pointing. The telescope works by looking within a viewing range (degrees) from where it is pointing. Obviously the further away it is, the more accurate you have to be. It might be the part config needs this parameter tweaked when Kopernicus and planet packs are installed. There are no pop-up dialogs, but a screen message should appear and a text message should appear in the ResearchBodies UI window when you discover a planet. But yes, visually in map mode nothing changes when they are discovered. I'm looking into actually not having the planet appear at all, but that makes it difficult to target (impossible) or know where to look. So currently thinking about how to tackle this problem. Having the name appear - that's some thing I can look at but I think is an issue because you only have a few status's for the planets in stock to play with.

Probably Tweakscale, or Everything.. but no logs, no help.

Thanks, but very little to go on there. Good news is I am back from holidays. So I will start looking into the problem and look to finish the full release in the next week.

I'll look into it. EDIT: I looked into this. It seemed unusual at the time that you said it would store up EC as it's produced... Because it doesn't. As the OP says, you MUST have the EC of 3000 to freeze or thaw a kerbal. I went back to very early versions - it never has done what you suggest. What it does do is consume EC per physics step of the amount defined in the part config by the field "ChargeRate". This is defined as 30 EC units for all the DeepFreeze parts by default (of course you can change it if you so desire). As long as your vessel is generating 30 units per physics frame then it will continue to consume 30 units until the 3000 is met. Are you saying this is not working as described above? If so, then it is not because of DeepFreeze but probably changes to the way resources are handled in stock from 1.2 onwards.

Your log file ^ is not shared public.

It does not change how solar panels work in the game. What you are describing is stock behaviour for solar panels. AmpYear does take this stock behaviour into account when displaying dark-side calcs, etc.

Quite possibly...

I'm not sure how you are getting these numbers. The default settings: MK1 in the VAB: The calcs are correct. Can you post your settings screen please, and other steps you are doing to produce this? Did you change the settings at all? https://github.com/KSP-RO/TacLifeSupport/issues/67

https://github.com/KSP-RO/TacLifeSupport/issues/66 Will be fixed next version. Not currently. Assuming they are external seats they are treated as separate vessels (EVA Kerbals). So what you are talking about is a special case. I'll have to think about how we could deal with this problem and get back to you. Edit: raised a github request https://github.com/KSP-RO/TacLifeSupport/issues/68

This is the time it takes for a kerbal to respawn if they die. Currently TACLS does not hibernate/comatose kerbals and then kill them. It's one or the other.

What help are you looking for with the little information you have provided? I'd suggest you supply log files from when the problem is occurring and someone might be able to provide you with some assistance.

Follow the support instructions for how to make your log files available.

This is just general advice as you have not supplied the full specs of each machine and there are many variables. But IF the only difference is the CPU I wouldn't expect there to be much of a difference between those two. Ask yourself this question: Is KSP the only reason for making this decision?

As you have not supplied any technical specs or log files for your laptop it is hard to give you any advice. Is it integrated graphics? How much memory? Have you tried decreasing the graphics settings in-game? As for reverting to a previous version, Steam does not support that. The best thing you can do with steam is backup each version when it is released. In that way you have each version stored for later reference if required.

Not heard of the bug.. and you think I would have? Well apart from this one I found http://bugs.kerbalspaceprogram.com/issues/9590 But that one was unreliable to reproduce and wasn't the same vessel (in fact it was reported that only the stearwing was affected, but not 100% of the time). Do you see anything in the logs when this occurs? Or can you supply saves and log files of this occurring and raise on the bug tracker? If reliable reproduction steps can be supplied along with logs and saves in a bug tracker report then a developer can look at it. Raising it on here, will not get a dev to look at the problem.

Whilst an error.log is mildly interesting. What would really help is if you post a link to your output log or ksp log files.