nanobot

So if not troll, then why write all caps, and then quote the list of "don't-ask-features" as requested features?

Troll?

In my opinion this is a must-have for stock 1.2. After seeing your mock-up, the standard text rendering suddenly looks so unprofessional.

I'd like to give 6.4x scaling a try -- does somebody know if "Stock Visual Enhancements + Scatterer + Planetshine + Distant Object Enhancement" works there?

I see... turns out that in the mobile webpage you have to scroll all way to the bottom a short notice in the Announcements subforum would be appreciated...

Wait, 1.1.1 is out? And nothing announced in the forum? I already found it ridiculous that I found out that 1.1 is out only because the prerelease forum was locked, and now 1.1.1 by this thread... or I am completely blind

A zip file of a bunch of files, individually upated, presumably combines the advantages.

Calm down, guys. Pretty sure you all started playing the game at some point, and that likely without any mods at the beginning, so the game is playable by definition. The term 'unplayable' really becomes overused. I was about to write 'KER', but regex' comment about MM made me think. MM is that one mod that now everyone takes for granted. Which usually means 'good work' in the IT world

I used Linux for the sake of 64 bit, and will compare the performance of OpenGL vs. DirectX before deciding if I switch back to windows. If there is no notable difference than it's Linux, because I'm too lazy to reboot. Oh, also I have to check if the CKAN client works on Arch now.

I do not plan to bother with stock resources as long as Karbonite is maintained; the same way i prefer FAR over stock aero. The mods just seem to be feature-richer and still built of professional quality. What are the advantages of stock for mining over Karbonite, if any? Can MKS-lite be compared to Karbonite, or does it just add more resources?

They should just have said they prepare the internal codebase to allow a free IVA movement feature later, aligned the models etc. Then maybe nobody would have complained...

I also do not use Curse, but I suppose Squad acts reasonable for a company, and that many people here oversimplify things. They cannot officially rely on a one-man-driven platform which could go offline whenever one guy wants to (like now). Even by recommending it officially there might be some legal pitfalls, I guess? Curse on the other hand has in some form guaranteed things like bandwidth and server uptime ... I mean by a real contract and stuff. It is one worry less for Squad and helps in concentrating on the game itself. It could be worse, like outsourced forums (or none at all).

In the worst case they will to have to go over the entire specification and check every feature again to make sure nothing is lost. But yes, the 1.0.5 changes could have been pulled into the 1.1 branch regularly (obviously not the other way around). Either way, now they know better for Unity 6 ;)

No. The width of the internal representation of this number has nothing to do with the word size of the processor architecture. It is common to choose floating point numbers as 32 or 64 bits (on any architecture), and integers as 32 bit, only sometimes also as 64 bit. This could be easily fixed in the program code Maybe you should write an official bug report? Also I am not convinced that a single physics object can span across multiple cores. The current dev article also does not mention it.

I did in fact a fresh download of CKAN yesterday, that is of v1.10.3, to finally try KSP 1.0. After a restart the installation of mods runs through, but fails with the same exception after two or three more mods. It however works to only install one mod at a time. After the exception window pops up, the downloads in the background still finish (quite plausible when the name of the bad method is CKAN.NetAsyncDownloader.ModuleDownloadsComplete) but they do not install and stay with a "0 kb left to download" message. When the popup is dismissed, the program crashes (unhandled exception). Therefore I also have done many restarts of the program which did not change the behaviour.