If by patient you mean constantly checking to see whether the update has arrived, then I too am patiently awaiting the arrival of the update on GOG.

Not updating until most of the mods are ported AND stabilized. IMHO there is no benefit in performance upgrade and fixed part limit bottleneck in Vanilla (unmodded). And 1.1 is basically a migration from Unity 4 to 5, which will require mods to do extra work to port. If you are not on x64 Linux, meaning you had only 32bit executable available - there is little point to use x64 without mods anyway.

GOG is really not the one bottlenecking here. It will be the classy mods.


Edit: The UI floating bubble feature is awesome, click once - and part dialog will be accessible, no matter how fast vehicle starts to rotate. But, with time warp mod it was possible to reduce the time scale to 0.001 to land the click no matter what. So...

Over on the KSP forums, even stock players are reporting significant performance gains when doing things like launching ships with high part count.

Most of the modders have been hard at work migrating to 1.1; heck, I have to keep looking for older, 1.0.5 versions. So, it's looking good.

I don't want to be a contrarian, but that's going to be be very much dependent on the individual use case scenarios. Not everyone has extensively modded KSP installs. Personally, I would happily go back to vanilla right now in order to access v1.1.

Any news if this has landed yet?
I like GOG and I'm guessing they lack the manpower of Steam etc hence the delays.
Galaxy is heading in the right direction but i think in future I'll have to stick to buying new/regularly updated games on Steam and stick to buying old games on GOG that will get rare/infrequent patches.
While its not really an issue as i'm in work, I'll be off home in 3 hours and would rather not have to wait several more days for a patch everyone else is already playing.

I don't think this is an issue of scale per se. The main issue here is the procedure for publishing updates is one that is automated on Steam, but requires the direct involvement of GOG staff to publish it here.

I don't know if this is to maintain quality control, or whether it's a lack of investment in the automation process. Either way though, I'm not all that happy with the way GOG handles these things. If it's a quality control issue, they should at least allow publishers the benefit of the doubt, and only step in to require approvals when a developer drops the ball. If it's a lack of automation, then I'm even less equivocal about the flaws in the system.

GOG and Steam are not the same. GOG installers use a standardised wrapper whereas the installation process on Steam is much more under the control of the developer. It's not like those differences make this an insurmountable problem, merely that the work put in to make the tools that will overcome these issues needs to be done.

Yeah i like the steam delivery system, it really only downloads the files that have been changed. I think galaxy is heading that way but certainly some of the patches still seem too big like I'm downloading the full game again rather than what's changed.

I understand with steam being involved in the experimentals they have a bit of a head start, maybe the publisher is more to blame for not ensuring all partners are ready to go at the same time rather then enact a get it out there ASAP mantra which leads to the split across platforms.

Oh damn, just one simple word written wrong ruins the whole answer :/
Misunderstood. I mean, the delivered performance is not much needed in unmodded installs, and x64bit also not much needed in unmodded installs. It will take significant time to move to 1.1 for mods, due to internal engine changes and squad code changes. There is purposely vanilla installs and regular installs. Regular installs are modded. I know features in KSP, which were influenced by mods - like aerodynamics model. Squad are still doing it proper way, they make sure the core is stable and efficient, over feature bloat.

There is little point to install 1.1 on x64 without mods. Typical performance with stock parts was already sufficient except for massive rockets and airplanes, and stations built with regular clampotrons. But again, modded gamers have KIS/KAS, DPAI. KJR etc and need no all-at-once rockets.

GOG typically checks if release quality standards are met, thats what usually causes delay. For example, Metro LL Linux version was not released by GOG because they found it to be not stable enough. Steam released it no problem.

Personally, none of that is my main interest in the KSP 1.1 update. While I am curious at the long-term potential of the 64bit executables as a mod platform, I am most interested in the changes wrought by the introduction of the new Physx version that was part of the Unity 4 to 5 transition process. If I had the Steam version, I would have been testing all that out now for the past several hours. Heck, days if you count access to the pre-release version on the beta channel through Steam.

I'm not especially ticked off or anything. I've learned through this and other games I have on GOG that there's a toll to be paid when awaiting access to new game content compared to Steam. I am however disappointed that this issue has persisted for a long time, with no effective solution. I really hope that GOG can find a way to do game content updates better in the future.

I understand as the retailer they don't want to be selling a faulty product as its them that's responsible for refunds etc.
But you'd think if valve can do it and push the blame onto the developer then surely GOG can.

Edit: Hopefully as GOG is based in Poland we will see some movement on this now that its daytime in Europe but i don't suspect I'll see the patch today in Australia which is a shame.

I appreciate that's the company line, but realistically there very little QA that GOG can do in the additional day or so between when a patch comes out on Steam and on GOG. Even at the reduced labour costs in Poland (compared to Valve in Washington State), it's doubtful they could afford to do a great deal for each and every version of every product sold.

The primary reason that there is a delay through GOG is because they post the releases themselves rather than giving that control to the individual publishers that control. GOG employs a standardised installation wrapper. Doing this is almost certainly the cause for the delay. One would have hoped that they could make it so that updates could go through Galaxy immediately, while the updated installer gets put together and posted. Either that, or they make it so that the GOG-wrapped installers can be automatically built and posted without these delays.

Finally! Now i have to hammer the F5 button straight 2 days.

Yeah i've checked back and it seems both the last few patches have all taken a couple of days to make it onto here.
I've tweeted them and had a reply that they are hoping to get it available today (In Poland i assume) if it passes QA so if we are lucky we should have it within 6hrs.
If they reject it then who knows.