MR4Y

Implementing more features and adding parts/features due to popularity hardly does anything to stabilize codebase. It just helps to preserve the alpha status quo. Still questioning why a modder has to provide source code of his own work.

Try to guess how many will not be in the main game or modified later and be in the game resembling nothing like the original design. That seems like a more interesting assumption/question to make.

Uh...huh. NASA had orange tanks for decades...

Wow...asteroids.... Not impressed. I imagine we're gonna have the exact same issues of large single part objects that happened when people made asteroids before. Plus, no n-body physics yet, so, high possibility of them being on rails as well.

I think it does, especially after 0.21, where the game would freeze for a few seconds during SOI transition.

Perhaps a better understanding on how the Kraken happens could help you trigger it on purpose.

I don't think the game should calculate physics for objects that are entirely static(i.e the entirety of KSC).

That would be no issue. As opposed to real life, you have no risk of Kessler Syndrome.

The problem is that shadows are NECESSARY for you to perform certain things on the game, like knowing when to burn during landing on planets with no gravity. Yes, you can land without any shadows on, but it's at least twice as hard. I would agree with you IF shadows were just something asthetic, but they're not.

Cause we all know, shadows are so much harder to do than real time physics calculations, procedural terrain generation and physics calculations per part, right?

Reinventing the wheel is one thing. Using other people's work and claiming as your own or calling it a feature is another. Let's see the pattern: 1- User suggests feature XYZ. 2- Forums/Devs shun it aside/call it impractical/tell it will sacrifice fun(or gameplay, or nostalgia). 3- A mod with the suggested functionality is made. 4- The so denied functionality is now implemented into the game. So far: 1- Capacity of filtering vessels, destroy debris and define vessel category and object (Haystack) 2- Capacity of saving parts of vessels and using them later. (Subassembly Loader/Saver then Subassembly Manager) 3- Career mode with "resource mining" (I forgot the name of the mod that had missions and all that +`Kethane) 4- Tweakables (ModularFuels, TweakableEverything[along with other mods that allowed part file editing on the fly]) So, the formula seems clear. The odds of a suggested feature being "implemented" are higher if there's is a mod to where functionality can be copied and pasted into the main game.

However, that creates another problem. To do that, you'll have to do something akin to a DRM.

And here is where I draw my sword and keep my point. This is pretty much close to the current status of Minecraft today. Let's wait till someone develop it for us FOR FREE then Copy-Paste it and call an implementation. Seems pointless? Then why pretty much every functionality of KSP has a mod equivalent or has the exact same functionality of a mod, including the flaws and shotcomings? So, apparently, suggesting is not enough. You have to spoon feed the functionality as well.

No. I'm not gonna use a mod that might introduce random bugs in the game (that will receive no support later) to fix a flaw in the game. Essentially, the game punishes you for having low spec hardware.

But you don't have shadows with the render level below 'Simple', which makes landing really hard.

Uh...huh.... Encourage piracy.... If I, the developer, make earlier versions of my own game freely avaliable for download, how the hell am I'm encouraging piracy OF MY OWN PRODUCT? And, people will pirate whatever product tey want, regardless of your so called incentive or not. Worst. White knighting. Attempt. Ever.

The alpha excuse was widely used by any KSP evangelist and the staff over the years to shush people's complaints. And you can cleary see how things are changing just for popularity's sake, rather than make the game better. Multiplayer was a taboo subject for many, many years. Even the slight mention of it would lock topics and give warns to users. Now it's being "implemented" in the core game. How that feature makes the game any better and fixes the flaws it has? It doesn't. Being parked in the alpha status quo, at least for me, it's a sign of lazy game developers. Because, come to think of it. There are games with less functionlaity than KSP that are full releases already. KSP is being priced as a full release already(Don't be stupid to think that you can price an indie game that has no competition like an AAA title) and still is an alpha. The only thing that keeps KSP from being shoved aside is the lack of a competitor of the same genre. As soon as that happens, wait and see if the game is gonna last.

It's the base of R&D, or Ripoff & Duplicate

Well, considering all the "planned" features for 0.24, I suggest that the barrier will be reached in that version. KSP is not Large Address Aware as well, limiting it's usage to 2GB of RAM maximum.

That applies only to your country. A half decent pc here is more expensive than a console. A decent PC is 2 to 3 times more expensive.

I'd say that the KSP forums, including the staff, are specialists of swiping discussions and complaints under the rug when they happen. Maybe something that was learned observing Apple's forums. As for the game, it has become overrated over the years. I still wonder how an unfinished game reach that kind of status and automatically makes its faults be considered "normal game behavior" or "minor hassles". This is a good indicator of a game becoming overrated: when you trade funcionality and improvement for nostalgia (needless to remind that tke tech tree is based on release version and not logic)?

Exactly. You'll make free assets that will later be edited, or even edited out as SQUAD wishes to fit in the game. I now have even less interest than before.

Instructions are still unclear/blurry/incomplete and you still have multiple fixes for the same problem. The link only solves one third of the problem.

No, they can't, unless they are Large Address Aware(which is not something you can simply turn on). If they're not, they can only access a maximum of 2 GB, regardless of the operating system being 64 bits or not.

*cough* This...is a *cough* video game. Before even considering that, the techtree needs to be fixed. I still wonder how you can develop working NERVA engines before you make auto folding ladders.