blu3wolf

Additionally, you might want to consider the effects of venting fuel from a station - jetsam is going to build up around the station. Easy to disregard that though, same as the thrust component of unbalanced resource dumps, and the animation for it, or the heat build up from dumping EC.

Applying a potential difference across a conveniently located resistor grid.

Windows command prompt is case sensitive, so you will have to make it ckan.exe install MagiCore=1.1.1 Note the capital M and C in MagiCore.

Does Kerbin feature overhangs of any sort? Id be inclined to assume AGL rather than AMSL would be a lot more difficult, if even possible.

There is already such a mod, that nibbles your reputation every day. I forget the name, though...

ah no.... two essential mods

well, that should work. Did you run that command from the same location ckan.exe is? If you didnt, this time navigate to the location ckan.exe is saved, hold Shift down and right click somewhere in the window. Select Open Command Window here from the right click menu. Run that command in the window, and it should work.

Due to a bug in the CKAN client, updated mods compatible with the current version, which have dependencies that have not updated to the current version, are not displayed. KCT is dependent on MagiCore, which has not updated. KCT is on CKAN, but cannot be installed without installing (through command line) first its (outdated) dependencies (just MagiCore), then itself. If MagiCore gets a new release on GitHub, KCT will show up in CKAN again.

From the sounds of things, it isnt. Or is that only with Linux?

It would be used for mission planning? I use notes mostly for the ships log. Noting down how the mission progresses according to the mission plan, etc. Of course, the mission plan is generally completed before KSP is started, so theres that XD

Does the 1.1.2 compatible version of MagiCore work with KSP 1.1.3 also? This would appear to be why KCT isnt displaying in CKAN presently.

In fact its on CKAN at the moment, but it is marked as only compatible with 1.1.2 as the max version. Seeing as CKAN is referencing the .version file in your install for that, (which says the max version is 1.1.3) Im not too sure what the hold up is. Is a .version file meant to have both version and min/max version information?

I too, was confused at first. This looks like it will become a must have for many folks installs.

Well, there exists the Ships Log template. I think that is implemented in code, though. What sort of templates might you use?

CKAN bug, mods dont show at all if they are up to date, but a dependency isnt. If the mod and all dependencies are out of date, it shows (just not under the Compatible filter). If the mod and dependencies are all up to date, it shows under Compatible. Its just when the mod is up to date, and the dependencies not, that they hide completely.

Looking forwards to more CactEye!

Its indexed, but it wont show up until its dependencies are all updated, due to a bug in CKANs display logic (should still be in the all filter, but is not). At this point I think that just means KIS needs to be marked as compatible.

I am pretty sure Lock On didnt simulate FBW. Still! Question answered, thank you.

I know, Im horribly late to the party. Im curious which military FBW mechanics you were looking at? I know there is some notes leaked onto the net about LM FBW implementation for the F-16. That particular one can do a coordinated turn when in autopilot HDG SEL or STR SEL modes.

If you want to travel to outer planets, or even Jool, you will perhaps rethink that pausing your timewarp every month to do manual stationkeeping, is not part of the fun

Ah, I was thinking you meant to not have an autopointing thing. Also worth noting for targets is that unless you use hyperedit, your KSO satellites will drift over time - not an issue for short term missions, but with years of timewarp, the relay directly overhead will end up on the other side of kerbin. Even satellites in the real world have to expend stationkeeping propellant to deal with their orbit not being perfectly synchrnous on a timescale of years. Its hard or impossible for me to propose issues with MJ integration, as Ive never used it.

The issue being, with RT for instance I can intend for the probe to go out of contact, without worrying about it losing settings during the dark period. If you intend spacecraft pointing to be a game mechanic, its going to have issues when on rails to off rails - because the craft will not have rotated during its orbit to point at its target. If it goes behind a planet, then it will have lost its pointing when it regains a line of sight - and unless it happens at random to sweep over the correct LoS, which is at that moment transmitting, its unlikely to regain stabilisation. Its one reason why regaining contact with probes in the real world, that have been out of contact, is so unlikely - impossible if they have lost their pointing system.

I dont think that would be an easy first mod. Optional MJ integration is not a bad idea. Having the probe spin ramdomly when it loses connection is a terrible idea. The original versions of RemoteTech actually had an antenna that would orient itself, to point at where the signal was coming from. They removed that part of the code. Not sure if it was a performance problem, or gameplay problem, or something else entirely. Your precise controls idea would prevent me from ever trying it. The reason this limitation exists in reality is due to low bitrate and speed of light delays. So, maneuvers are programmed in advance - just as in RemoteTech. As far as the losing connection and automatically trying to reconnect goes, that works if it has a single, wide angle dish to connect with. On the other hand, if it has say three of them, and one of them is a tiny angle, almost any rotation at all will rotate the high power dish cone off its target. Not to mention you could have trouble dealing with that when it goes on rails. Even RT has problems at high timewarp.

15 minutes of required knowledge does not an advanced tool make. It is a tool for all users, not just advanced users.

Exactly what would me releasing a mod have to do with any of this? That aside, CKAN harmed as many folks as did Sarbian.