TeddyBearBonfire

As ever, I'll likely buy months after release. I always wait to see what the general playerbase thinks of a game, and I've never really understood the issue people have waiting years for a game and not being able to wait a little longer and know what they're getting for their money. Average player reviews interest me much more readily than those of dedicated gaming sites or youtubers (though the latter are of some interest at least). Conceptually I'm pretty confident I'll like the game—how far wrong could you go with the basis of what KSP is? So mostly it'll be a case of seeing just how well-taped-together the game is—performance issues, bug prominence, and such. It usually doesn't take long after a game's release to hear about any major unexpected missteps as well.

Nope, yod coalescence can occur not only across syllable boundaries, but even across word boundaries (e.g. ‘got ya’ -> ‘gotcha’).

This is literally just a dialect thing. These are just different yod-based sound changes. North-American dialects of English tend towards yod dropping in this instance, wherein the ‘y’ sound was removed from the older pronunciation of such words (resulting in something akin to ‘doona’). Some dialects of English in England tend towards the older sound wherein the ‘y’ sound that often sneaks into many words with a ‘u’ is still pronounced (so you could write the sound as something like ‘dyoona’). Further still are those dialects which have a different sound change in such instances known as yod-coalescence, wherein neighbouring sounds in a word change for a more relaxed pronunciation. This happened particularly with the sounds (not necessarily the letters) ‘d’, ‘t’, ‘s’, and ‘z’; the former two are fairly variable from one group of dialects to the next, whereas the latter two are much more ubiquitous throughout English (e.g. ‘pleasure’, wherein the sound would be more akin to ‘pleaz-yuhr’ had it not experienced yod-coalescence such that it is now nearly universally ‘plea-zhuhr’). Often these sound changes take place across a language, but to different degrees. Yod coalescence, for example, can be seen in US English in the word ‘educate’, but not in the word ‘dune’. In my own Scottish English, words such as ‘dune’ do indeed exhibit this sound changes, so I pronounced that ‘d’ with the same sound as the ‘d’ in ‘educate.’ In fact, this reminds of an amusing time in the US when I had to repeat myself several times to a guy working in a shop that I wanted a Mountain Dew before I realised what was going on and he was perceiving me as asking for a ‘Mountain Jew.’ You'd think it'd be contextually pretty obvious, but nevertheless. (And yes, as it happens, in Scottish English, or at least in my dialect of it, ‘dew’, ‘due’, and ‘Jew’ are homophonous; ‘dune’ and ‘June’ are nearly homophonous save for the vowel length). But anyway, the point is, how you pronounce ‘Duna’ is very plainly dependant on your form of English. Anyone arguing that there is an absolute correct pronunciation that doesn't account for such dialectal differences is just a little lacking in the linguistic understanding department (which is fine, if a bit of a shame—it's a woefully-misunderstood area though, so that'll happen).

KSP1 isn't going to be fixed unless it's rewritten from the ground up by a team that knows what they're doing from the start from a technical perspective. If only there were such a possibility.

I'll never understand why there's such a thirst for shoehorning in random content creators for no real reason. I have nothing against any of the youtubers being suggested (quite the opposite), but I really don't find the idea of them within the game appealing. If there is voice-over, it should be much more characterful, befitting of the spirit of the Kerbals.

You could buy 1000 copies of KSP and you still wouldn't be any more entitled to KSP2, no matter which company any of that KSP money went to. At the moment, KSP2 is some public news that uninvolved people such as us can share some joy in, but nothing more as far as those outwith the companies involved are concerned. Buying KSP or random merch is not an investment, but a purchase—it starts and ends there, as far as the products you're entitled to are concerned.

I expect that it's how such people guard themselves against disappointment. They argue for the likelihood of negative outcomes so that were such an outcome to occur, they can have their "told you so" moment, and bask in some semblance of victory; on some (probably subconscious) level, they'd rather presume the worst than take the risk of having their hopes dashed.

Intercept Games aren't responsible for KSP1 or its console ports. This won't have any impact on that one way or the other.

Unless they mislabelled it, this is Eeloo. The image is named as such—look at the file names in the URLs: https://www.kerbalspaceprogram.com/wp-content/uploads/2020/06/Eeloo3-1024x859.jpg https://www.kerbalspaceprogram.com/wp-content/uploads/2020/06/Eeloo1.jpg And given how much attention they're paying towards real life data for aesthetics (going off things like the fuss they made about pink drive plumes derived of how it should appear in reality), it might be that they've changed the aesthetic a little based on the planetary composition. Pure speculation on my part, but it'd be a credible reason to my mind.

Latest version 0.1.6.1 is giving an error on game startup (upon reaching main menu), KSP Installation Validation Error (or something to that effect, don't have it to hand), and says the files should be in <KSP Installation Directory>/GameData//SHED (double slash prior to SHED is quoted). I've just reverted to 0.1.6 and it works fine. For both versions I'm using KSP 1.8.1, CKAN says 0.1.6.1 is still suitable for 1.8.1 so I'm presuming that's not the issue. Just a heads up anyway. 0.1.6 performs perfectly fine for me atm

Something that's always been a bit of an annoyance to me is the inability to see a side-by-side comparison of two parts in the VAB or SPH. This sort of addon is very popular in the MMO community for stat comparisons between items/equipment, so I thought maybe it'd be easier to find than it seems to be! Does anyone know of any such mod I might've missed (or even a stock option, if I've missed it?)? I envision something like when you right-click on a part in the VAB, and it stays on-screen even when you move the mouse away, it would go a step further and stay on-screen even when you mouseover other parts (I don't really care for the specifics of how it functions if it just makes it easier to view stats side-by-side than my current snipping tool method ).

Noticed an extremely minor (negligible?) issue, and not one specifically with the mod, but with the CKAN listing, which is that the forum link in the mod's metadata is bad. This link is given: http://hhttps//forum.kerbalspaceprogram.com/index.php?/topic/178973-141-dang-it-continued/ Obviously, it's pretty easy to get the real link from that, but if you care to have it fixed, there you go.

Nice! Just got back into KSP after a few months absence, so its great to come back to progress on two of my favourite mods. EDIT: CKAN claims the two are actually in direct conflict, prohibiting me from installing both Kerbalism (3.0.2) and NEOS (0.8.0). The little extra info with both checked on trying to quit CKAN is viewable here: https://drive.google.com/open?id=1Y4XpFCr6Slag9lkgWvJTFhhkyjZGB48A Will try a manual installation and see if all appears well, if it's maybe just a misidentified conflict. In reality, it's probably my fault for coming back to the game. I think my presence in KSP is the antagonising factor EDIT 2: Well, I can confirm that the fix for that old issue definitely works despite this supposed incompatibility. I installed NEOS via CKAN and manually installed Kerbalism 3.0.2, and all seems to be working so far. No idea what the nature of the conflict actually is so far.

The closest I'm aware of is kOS' tag system—it allows you give parts unique tags via the right-click menu, but on the tag input pop-up it also shows the .cfg name of the part—not quite as simple as a hover-over, but it's there and accessible both in the VAB and in flight. And you can basically ignore the rest of the features of kOS and just use that feature.

Oh, is that what's going on? I was wondering about that, so the science never actually goes back into the pod but stays attached to the part itself (I was wondering why I couldn't review it in the pod like other science). And that would explain why Kemini contracts still work—because it's not designed to stay attached to any particular part? Or am I going down the wrong direction? I just want to satisfy my curiosity by this point