linuxgurugamer

Try planning on mid course adjustments. I generally break up an interplanetary trip into thirds, just because the floating point errors add up

New release, 0.5.3.3 Fixed MonoBehaviour to never go away, was preventing numbers from being assigned

New release 1.34.0.2 Fixed typo in name of shader

Ummm, it is there Still broken, working on it

New release, 1.4.0.7 Fixed location of config files Refactored all Quick mods to make the local paths consistent

When you wake up, and think that the real world is just a dream

There are smaller cameras. This mod is in a maintenance mode, no further work is planned

Nothing, it doesn't remember it's location. I'll see if I can do something soon, but busy with some other stuff right now

Thanks, I'll be working on this tomorrow night

I've released KST from beta, it's now uptodate: New release, 1.4.6.21 for KSP 1.7.3 & 1.4.7.10 for KSP 1.8.x Fixed issue of blizzy toolbar button sometimes not being there when the UI scale was not 100% Fixed issue of toolbar buttons (both blizzy & stock) not changing when clicked Removed old code which provided the textures for the Blizzy toolbar Minor refactoring of code in KerbalConstructionTime.cs in Start() to replace multiple If's with a switch Fixed small memory leak by replacing all the "new Wait4Second" with constants Fixed big memory lean (1-3 meg/sec) caused by needless changing of textures in the toolbar buttons Removed unused function: GetStockButtonTexture, not needed since the ToolbarController handles all of that Fixed the unable to resize Blizzy's toolbar when KCT icon is transferred to it Added AirLaunch configs

I have to fix a couple of toolbar icons first

For all interested parties, I've found the bug in Kopernicus which was preventing NH from running in 1.8. The fix has been accepted into the repo. So far, my testing on NH looks good

New release, 1.34.0.1 Fixed shader to use Legacy shader

Why should I explain how wrong you are when fact you are correct? Thanks, I'll get that fixed today

People, I stated that I will NOT distribute this to other players. It's fairly obvious what I am saying, yet I have already been contacted via PM by someone who wants me to send it to him. [snip] LinuxGuruGamer

@zer0Kerbal While it might be nice to also say that the from/to for transferring resources must be within a certain altitude of each other, I don't really think that's necessary. My issue was transferring resources from 2.5km on one side to 2.5km on the other side. I can live with a much smaller sphere and just hand-wave the resource transfer. You may also want to consider a blacklist of resources that can't be transferred. For example, EC, Ore, liquid hydrogen, etc

New beta, 1.4.6.21 for KSP 1.7.3 & 1.4.7.10 for KSP 1.8.x Fixed issue of blizzy toolbar button sometimes not being there when the UI scale was not 100% Fixed issue of toolbar buttons (both blizzy & stock) not changing when clicked Removed old code which provided the textures for the Blizzy toolbar Minor refactoring of code in KerbalConstructionTime.cs in Start() to replace multiple If's with a switch Fixed small memory leak by replacing all the "new Wait4Second" with constants Fixed big memory lean (1-3 meg/sec) caused by needless changing of textures in the toolbar buttons Removed unused function: GetStockButtonTexture, not needed since the ToolbarController handles all of that Fixed the unable to resize Blizzy's toolbar when KCT icon is transferred to it https://github.com/linuxgurugamer/KCT/releases/tag/1.4.7.10 Those of you who downloaded that test dll for the toolbar can revert the change

Of course. I did find one bug, confirmed by @Sigma88 when working on New Horizons, but in general, I don't ask for support for my version.

Is the range configurable? In other words, is there a way to only include vessels within 100 metere rather than 2.5km?

I submit PRs when I have changes for any/all mods that I update. For this, the only changes were needed to compile it in my environment

Inhave, but I don’t recommend doing it for the casual player. And, before you ask, I am not distributing it to other players. I did it for my steam on Twitch

Actually, wait until tomorrow. I have found the cause of a toolbar problem, which appears to be a cause of the memory leak. I neec to do some more testing and will then put out a new beta this evening.

You would have to ask @Lisias how it scales the antenna power, or if it even does

Please try with an unmodified version of the Toolbar

@Master39 Please try this. I don't know if it will help, but I did this for someone else who is having issues with KCT and the toolbar: It's a custom build of the Blizzy toolbar, unzip it into: 000_Toolbar\Plugins https://www.dropbox.com/s/k3rp42ab8shrmrv/aaa_Toolbar.zip?dl=0 It IS going to be spamming the log file, so be patient, and see if it fixes your problem.