TeddyDD

As keks said earlier such a tool will probably be created over time. If all goes well will be several (for different IDE and standalone) The only problem I see here is that when writing such a tool would be needed support from web developers of mod websites (API that allows to upload mods) I'm not sure if Curses has something like this

1.At the beginning probably not, but over time may see the benefits of this solution. 2 and 3. Most important mods first appears on the forum. In practice, maintainers must check only forum. We will not upload mods to the repository. We will upload only small files containing information about the mods. Mods will be downloaded from its orginal location. The repository will be used by mod install/update tool.

Thanks to this program I was able to perform flight Kerbin > Eve > Duna And it was awesome Thanks Arrowstar

That's what I was thinking from the beginning. The ONLY standard of what we need to introduce it a standard packet metadata format. Then people will be able to use it in their projects (eg mod managers, packet generators, or even mods). -Package format should be discussed and approved by all interested persons. -It should be carefully thought out, so we did not have to modify it soon because it could cause a incompatibility of different tools. -In addition, these packages should be based on any known format, so it was easy to parse it in different programming languages ​​(I think about json or yaml but maybe you have better suggestions?) I'm curious what you think BTW. Sorry for my English if I made any mistake

On the contrary, I do not use SAS to rotate the vehicle

I assume that there will be people willing to help. If the package creation will be a simple of course. I think part of data in the json file can be generated automatically by the tool for creating packages. Maintainer will have to enter only some information. Another thing is my idea helps to avoid problems with licensing. As long as mod is on hosting with direct links Distributing a package with information about mod is not redistribution a mod itself

I'm workin (rlly slowly) on something similar. But my idea is little different. I do not think we can force modders to use any standards. My idea is to use json files with all mod informations and directory structure (example: where in zip is GameData dir) and direct link to download mod (dropbox etc.) This is quick dirty example of package json file http://pastebin.com/1FWeC82Y

Yeah, but then everyone can fork your modified repo from you and then there is a conflict with the rules of github. Anyway I guess you're right. Propably I interpreted it wrong. Too bad. In any case, I support this initiative. In my view, closed mods have no chance to survive in the long run.

His (Majiir) license is against the rules of github.com You can safely ignore it. You have the right to fork the repository and do with it what you want. Enjoy.

Today I failed I tried to recreate Ares to Mars mission (Kerbin > Duna with Eve flyby) But my lander hasn't enough parachutes. Or I'm too stupid for Real Chutes

Mayby someone with mac and mathlab could compile this stuff from source

0.15 version. MechJeb The great feeling of loneliness. That was awsome.

This program is one of the most amazing things I've ever seen on this forum. Thank you sir! BTW. I followed the tutorial in pdf and my hypothetical orbit passed 100 kilometers below the surface of Vall xD I still have lot to figure out in this program

You lucky devil. Even the 32-bit version did not want to work for me.

Im using Linux Mint and Windows 7. KSP works on Linux like crap. I love Linux but for now is way better to install Active Memory Reduction and play on Windows :|

62 dirs in GameData. Not too much IMO

I love this stuff...

ldd KSP.x86_64 linux-vdso.so.1 => (0x00007fff933fe000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f14d4413000) libGLU.so.1 => /usr/lib/x86_64-linux-gnu/libGLU.so.1 (0x00007f14d4194000) libGL.so.1 => /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 (0x00007f14d3f35000) libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f14d3c00000) libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007f14d39ee000) libXcursor.so.1 => /usr/lib/x86_64-linux-gnu/libXcursor.so.1 (0x00007f14d37e3000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f14d35df000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f14d33c2000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f14d31b9000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f14d2eb5000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f14d2c9f000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f14d28d6000) /lib64/ld-linux-x86-64.so.2 (0x00007f14d4738000) libglapi.so.0 => /usr/lib/x86_64-linux-gnu/libglapi.so.0 (0x00007f14d26b0000) libXdamage.so.1 => /usr/lib/x86_64-linux-gnu/libXdamage.so.1 (0x00007f14d24ad000) libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 (0x00007f14d22a6000) libX11-xcb.so.1 => /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 (0x00007f14d20a4000) libxcb-glx.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0 (0x00007f14d1e8d000) libxcb-dri2.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-dri2.so.0 (0x00007f14d1c87000) libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f14d1a69000) libXxf86vm.so.1 => /usr/lib/x86_64-linux-gnu/libXxf86vm.so.1 (0x00007f14d1863000) libdrm.so.2 => /usr/lib/x86_64-linux-gnu/libdrm.so.2 (0x00007f14d1656000) libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x00007f14d144c000) libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007f14d1247000) libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f14d1041000) ldd KSP.x86 linux-gate.so.1 => (0xf773c000) libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xf7631000) libGLU.so.1 => /usr/lib/i386-linux-gnu/libGLU.so.1 (0xf75ab000) libGL.so.1 => /usr/lib/i386-linux-gnu/mesa/libGL.so.1 (0xf7551000) libX11.so.6 => /usr/lib/i386-linux-gnu/libX11.so.6 (0xf741c000) libXext.so.6 => /usr/lib/i386-linux-gnu/libXext.so.6 (0xf7409000) libXcursor.so.1 => /usr/lib/i386-linux-gnu/libXcursor.so.1 (0xf73fe000) libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf73f9000) libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf73dd000) librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xf73d4000) libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf7391000) libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xf7374000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf71c0000) /lib/ld-linux.so.2 (0xf773d000) libglapi.so.0 => /usr/lib/i386-linux-gnu/libglapi.so.0 (0xf71a9000) libXdamage.so.1 => /usr/lib/i386-linux-gnu/libXdamage.so.1 (0xf71a5000) libXfixes.so.3 => /usr/lib/i386-linux-gnu/libXfixes.so.3 (0xf719f000) libX11-xcb.so.1 => /usr/lib/i386-linux-gnu/libX11-xcb.so.1 (0xf719c000) libxcb-glx.so.0 => /usr/lib/i386-linux-gnu/libxcb-glx.so.0 (0xf7184000) libxcb-dri2.so.0 => /usr/lib/i386-linux-gnu/libxcb-dri2.so.0 (0xf717d000) libxcb.so.1 => /usr/lib/i386-linux-gnu/libxcb.so.1 (0xf715c000) libXxf86vm.so.1 => /usr/lib/i386-linux-gnu/libXxf86vm.so.1 (0xf7156000) libdrm.so.2 => /usr/lib/i386-linux-gnu/libdrm.so.2 (0xf7149000) libXrender.so.1 => /usr/lib/i386-linux-gnu/libXrender.so.1 (0xf713e000) libXau.so.6 => /usr/lib/i386-linux-gnu/libXau.so.6 (0xf7139000) libXdmcp.so.6 => /usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xf7132000) When I using optirun ./KSP.x86 (optimus) game don't starts but it runs from Steam. KSP.log here: http://pastebin.com/wjT7cxwK Thanks for your help

Thanks dude but if you mean this echo "090f377: 00" | xxd -r - KSP.x86_64 echo "090f37c: 00" | xxd -r - KSP.x86_64 did not help

I use Linux Mint 64 bit and update 0.23.5 (Steam) just don't works. The previous version worked very well (even 64-bit executable with mods) but after updating the game does not work. 64 bit version starts up but then turns off but after then crashes. 32 bit version stops to load on Mk1 cockpit model (I'm running clean install of course)

Hi dudes. I am a horrible lazy so I wrote a simple Perl script that downloads the latest version of the file with science. If differs from that in the folder with the game script updates it. Cons? You need to have Perl. But if you're lazy like me you probably have. Enjoy: http://bit.ly/scupdate (github gist)

Really nice I love lua

I hate the idea with stock accelerometer replacement but awsome update anyway :/

If you play with realistic rules and mods it is not so simple. Im thinking about sending one Kerbal in small can for a flight lasting 3 years.