Pecan

Steam recognises files as "corrupt" if they are in any way different from its installation set. Loading the game writes date/time stuff to logs and in the course of things will update the persistent save file. That's enough to 'corrupt' them as far as Steam is concerned so if you're just seeing one file corrupt there is, actually, nothing wrong.

Fudge that is probably more trouble than it's worth but something else you can play around with :- Use an action group to activate/shutdown engine, then you can set and control the throttle as you wish without any actual burn, then 'blip' it on/off using the action group. The obvious problem with this is you're relying on disabling the engines ... which you're bound to forget, crank up the throttle because nothing's happening, then remember and woooosh! If you're anything like me, anyway.

I don't expepct to suffer any damage. Go ahead, I'll be fine thanks *grin*

Which has wrecked the thread as a source of information about Tylo landers.

Sometimes drifting around all that empty space can get lonely. Jool did it for me, where even a simple journey from the edge of the SOI to low-orbit means dodging all the rocks whirling around *grin*.

Tylo is by far the hardest vacuum body for lander design. You know that. You can design an uncrewed lander. Are you sure you want a single vehicle that has i) a crewed lander AND ii) a separate rover AND iii) all the science gear? Suggestions: A. A rover that can launch back to orbit. Then the actual landing vehicle is a simpler uncrewed stage. B. A separate drone science-pack. Since you have a rover you can drive to and meet the drone once your crew are down. For an actual design - how many crew?

Docking on the ground is much harder than in space, because of all that lumpy solid stuff :-) Believe it or not I started building stations in orbit because bases on the ground were so difficult. Good luck.

Please explain, I don't know what it is - and there'll probably be others who come to the thread that don't either.

My invariable 'end goal' is a permanent network between every planet. As such it makes sense to keep transport vehicles in space that never land, just shuttling between planets to transfer fuel/cargo/passengers to specialised, reusable landers that never travel beyond orbit. (Reusable landers at Kerbin are also generally known as SSTOs). More as a convenient place for things to wait and meet than anything else the ships all dock above each planet at stations. Since I'm using standard ships for everything the mass that can be launched in one go and hauled between planets is limited (how much depends on the playthrough but I usually find 40t is sufficient for even large loads). Construction up to the interplanetary limit, if above the launch limit, would be in Kerbin orbit. Above it then by definition it would be in the alien one. What I almost never do is launch landers, stations or components that take themselves to another SOI.

> Logos - you're ok with those, from the statement UomoCapra made but, yes, in general it's better to be safe than sorry so using custom ones is better. > Toilet - I was light-heartedly pointing-out that it's not nice to make a company's pictures look like poo! (Again, just an 'in general' permissions thing. Not imply that you were or would). > Endorsement - if a company 'endorses' your video/comic/book/whatever it gets their 'official' blessing. It's somewhat like their mod recommendations where they are saying "we recognise this as a good and worthy thing". NOT endorsing something is an example of where a company has to protect itself by saying they are officially nothing to do with it even if some of it looks like their product. Obviously, Squad haven't seen what you're doing so they can't straight-out say they approve of it although if it becomes terribly famous in the future there's nothing to stop them then looking at it and saying 'yes, we like it'. As always, think of the terrible legal things that *could* happen to Squad/Take-Two in the worst case. Someone, somewhere, sometime might find something in your work that they don't like and sues them because they 'authorised' the whatever. > Mods - yes, you're right about needing permission from them too but those are usually much easier to obtain or, at least, the process and who to talk to is much clearer. In most cases the mod licence gives sufficiently blanket permission (although it's always nice to ask; mod developers like to know that people value their stuff enough to use it). > Plan - You are doing entirely the right thing and we can only hope that you do follow-through with your plans. You can't get permission unless you have the idea and you can't complete without the permission and you'll probably have to go around the circle several times as the implementation changes the idea, which needs different permissions, which affects the implementation, etc. etc. It's how anything gets created *smile*. Have fun.

It's enough but possibly in the wrong place. If the relays are in the plane of the solar system then there will inevitably be times when they are blocked from any other planet - by Mun, for instance. Give yourself a different perspective by putting them in polar orbits and think of looking 'over' and 'under' the intervening bodies rather than trying to see through or around the clutter. You may also like to consider a highly-eccentric polar orbit, with apoapsis near the limit of Kerbin's SOI and periapsis as low as avoiding collisions permits. In such an orbit your relays will spend the vast majority of the time far above, or below, the system plane and have a view only possibly blocked by the sun. You already know how to get around the sun :-)

You've had some very good answers here, including specific 'go ahead' from UomoCapra so you don't need to edit any pictures to satisfy them. Just in case it helps in the future here are some things to look out for: 1. The devil is in the detail. While many companies might not mind you using the 'shape' of their 3d models check the textures carefully. For obvious reasons company and game logos - such as the default KSP flag - are much more likely to cause objections. This is why a wire-frame model such as from vessel viewer is generally more acceptable. Kronal Vessel Viewer (https://spacedock.info/mod/1092/Kronal Vessel Viewer Continued), which I used, makes excellent 'exploded' 2d-views of rocket designs so is excellent for both displaying the construction and hiding the texture details. (That's actually the mod I was thinking of rather than wire-frame vessel viewer). Very specific imagery, like Kerbals themselves, can almost certainly not be used without permission - which is within the terms of the statement you have from UomoCapra. Otherwise they'd be very hard to edit in such a way that they weren't still obviously Squad's Kerbals. 2. Pay respect to get respect. If you're flying rockets from bottom to toilet (*gasp* you said you're too young, stop it!), or creating a similarly negative or insulting image, it shouldn't be a surprise that a company is more likely to disapprove. Keep in mind the impression of a brand that your own work is likely to imply/project. 3. Every product and company is different. Apart from the different laws in various countries some people/organisations will welcome wider exposure as free publicity, others will 'manage' their branding very tightly and hardly allow any use of their property (Disney are known to be extremely litigious). Note that copyright owners are required, by law, to protect themselves with certain forms of words ("We cannot officially endorse your project" and "you wouldn't be breaking any rules" in Squad's statement are examples). Understand that it's not personal, the statement they make for one person also has to protect them against everyone else, who might not be as nice as you. Beyond that the borders between "IP theft", "derivative work" and "original work" are extremely imprecise I'm afraid and differ around the world. Propensity to give or withold permission is even more variable. IANAL but I am an author.

Good luck with that. When I wrote my (free) book on rocket design Squad not only failed to give permission to use pictures but couldn't even come up with copyright-attribution text to say KSP belonged to them. Total no-hopers. Now it all belongs to Take Two you''ll at least be dealing with professionals but whether that's good or bad you'll have to find out. Here is what you have to do: A. Write to Take Two detailing each and every image you wish to use, in context. Await reply. Pay fee. B. Grace Hopper, "It is often easier to ask for forgiveness than to ask for permission" (just do it and, if you're low-profile enough they won't notice or will not mind) C. Process the pictures, either through in-game mods (such as vessel view, if it still exists) or proper image-processing software, to the extent that they become 'original works' and are therefore your copyright, not Squad/Take Two's. Let us know how you got on. PS: When I tried Squad made it very clear that YouTube videos were the only media they understood. They really liked people making videos as it gave them free publicity. Books were just completely outside their comprehension. They didn't like people making books.

Dres-hating is an important part of keeping the masses away. Every emperor needs an Imperial reserve and what better than the luxury and privacy of Dres's premium leisure facilities?

Ok, those needles are nice in the second version. Still not at all sure about white on off-white but they probably have good reason for it.

Please let us know which committee decided white-on-white would be good for the needles.

My first rocket (2013, 0.18 demo version) was Mk1 capsule, FL-T800 fuel tank and some small engine. It didn't have enough thrust to launch. My second rocket had a T30 and went up ... and back down. Then I bought the real game.

Nicely explained, tiny typo correction for you.

Just to add; Which side of the moon you arrive at requires exactly the same burn. If you time your #2 burn slightly later in your Kerbin orbit you arrive slightly ahead of Mun, and end-up orbiting clockwise instead of behind it and anti-clockwise. Even changing that within Mun SOI, once you get the encounter, takes a very minor burn. The main advantage of one orbital direction over the other is that, if you are landing, you want to be orbiting in the same direction as the body is rotating, for a slightly reduced braking dv.

There are five games I've played for more than 1,000 hours; KSP, Mount & Blade: Warband, Rimworld, Rome: Total War and Second Life. Rome: Total War was the first (it's the oldest) and Rimworld was, I'm afraid, the fastest in real-time to reach 1,000 hours game-time. Second Life is interesting in that I came to it late but was making a real-life living using it. Mount & Blade: Warband's claim to fame is that it doesn't have one! On the other hand I'll order Bannerlord the day it's announced (if ever). KSP is the only game I've written a book about. There is only one game I've spent more than 4,000 hours on. Guess which one it is.

Fair enough, I'll remember not to take any contracts in Sweden. As it happens the code I wrote in that session was very solid, simply because it had been written cohesively, in a single seamless chunk and without being pulled around or apart by several cuts. I've always found it's the pieces that have been gone-over several times, by different coders at widely different times that are most messed up.

Indonesian bosses must be very silly then, as I said. Generally companies that like achievement and profit don't fire people who do 30 days work in 3 days, at home, in their own time.

Sleep is over-rated ^^. Seriously, anyone should be able to go without a night's sleep without too much trouble. Going without for two is harder but it depends on what you're doing. One weekend I was on a roll and did a month's work* at home, emailed it in on Monday morning with test instructions and told them I was finally going to bed and would probably wake-up on Wednesday, be in the office Thursday. (Predictably, several people objected to me not coming in for 3 days. Equally predictably, they looked silly). When I did the 72-hour KSP sessions I was writing a book about it and wanted to get to specific points before going to bed. (*writing some database system. Not exactly exciting but inspiration struck, everything was fitting together nicely, it was good, interesting, elegant, fast and not something I wanted to lose by going to sleep).

Waiting half the orbital period would have done it.

Right-click them and spend a lot of money, IIRC.