Liquid

Seeing as we're going to be stuck with the original KSP for a while, could Squad at least fix the longstanding bug that stops Linux users from loading the hi-res part textures? https://bugs.kerbalspaceprogram.com/issues/24306 We're getting screwed badly enough with the KSP2 team not bothering to release on our OS and current game looks kinda dated as is, it'd be nice to at least have the proper textures until the next one comes out.

The in-game controller support has always sucked and always will, because the devs just don't give a crap about it. Even if you got it working as intended, you'd soon run into annoying limitations that will keep forcing you back to the keyboard. Your best bet is to use Steam's own gamepad configurator to map it, it's somewhat complicated due to having a lot of options, but it guarantees you'll be able to get about 95% of the mappings you want, the way you want them, even including more complex things like modifiers and mode switches. To use the configurator, go to Steam > Big Picture mode > [Name of game] > Manage Game > Controller configuration. It's possible to do this outside of Big Picture mode, but that version of the tool is buggy and frustrating in my experience. Don't worry, once your mappings are saved you won't have to use Big Picture mode anymore, it's just while you edit the controls. Feel free to shoot a message if you want a hand, the options there can be overwhelming if you don't already know what they do.

I see the problem, you probably saw the minimum requirement of 3GB RAM and thought your 4GB machine should be more than good enough. Unfortunately, you didn't take into account the nature of integrated GPUs like the Intel HD 6000. VRAM means video RAM, basically just memory reserved for graphics/video operations. When you have a discrete GPU like the one that slots into a desktop machine, or the ones found in higher-end MacBook Pros, they use dedicated VRAM on separate GDDR memory chips on/near the GPU board/chip itself, faster than and separate to the main RAM. When you have something like the Intel HD graphics 6000 1536MB, the 1536MB part refers to the 1.5GB of your main RAM that it's using as VRAM. So your 4GB of RAM, minus the 1.5GB that the Intel iGPU uses as video memory, equals 2.5GB, which leaves you 0.5GB under the minimum requirement. Considering that the OS itself also needs memory, you probably have less than 2GB left to play with, and that's probably the source of your crashing. As is the trade-off with such thin/light machines, MacBook Airs have everything and it's uncle soldered to the motherboard, so there's no way to change the CPU or RAM (shoulda went with the 8GB one). The game only needs 512MB of VRAM, so your best bet would be getting the iGPU to allocate less RAM as VRAM, but as far as I know there's no supported, official way to change this (though there may be unofficial ways to do it): https://support.apple.com/en-ie/HT204349 Integrated GPUs use shared memory (from RAM) Discrete GPUs use dedicated memory

I'd also like to see some basic KSP mods on the consoles, but getting the game in a playable state is probably a bigger priority. I've a feeling that the challenges surrounding mods on console have a lot more to do with "but then how would we sell DLC" than the "totes insurmountable security and technical challenges" that are often hinted at by the console manufacturers. They've peddled the same kind of lie about console-to-console cross-platform play several times until Psyonix (developer of Rocket League), proved that it was load of hogwash that had more to do with business/marketing policies than anything technical (the bean counters believe it would hurt sales if people could play with friends on other platforms... #4thesharholders). Not that unlikely as there is precedent for it, Bethesda already got permission from both companies to allow mods for Fallout 4 available on both consoles, so it's clearly not impossible. In typical Sony fashion, they were simply too inept to get it working (probably also why KSP for PS4 STILL isn't out in Europe over a month after the launch date), but it's been available to XBone players for a while now. Even if mods only worked on the console that supports it, that's no reason not to go for it. It'd be good for everyone including Sony, as the embarrassment of their competitors having features they don't, will help motivate them to stop letting down their customers.

I don't own an XB1 so I can't comment on what options it has or hasn't, I just made the post so players have some options rather than none. While the restrictions on the remapping apps might be annoying, it's ultimately up the game developer to give players decent control layouts and options. Both MS and Sony have rich APIs to allow that and nobody stopped Flying Tiger from using them, so maybe ask them why they didn't.

Why would it have to include other games, you know you can quickly toggle the custom mapping on/off in the quick menu, right? See the picture below if not. About the "R2 issue", I'm not sure what it is as I don't have the console version yet, but I'd bet it's to do with deadzones and input-handling. I've had occasional trigger input problems on the odd PS4 game, it seems to be related to the deadzones being a bit too small for the slight variations in build quality of the controllers. Taking the controller apart and re-seating the triggers worked for me, but your mileage may vary and setting the deadzone or allowing it to be user-configurable is ultimately up to the developer.

Gotten used to? It just came out last week and isn't even out yet for half the world! I think the oddball control scheme and total lack of control options are a major drawback too and is why I'm holding off buying it, but I'm just trying to give people some options instead of none. Input is one of the most important aspects of a game and not being able to comfortably control it ruins the experience. Lacking the ability to even invert the look is just downright sloppy, especially given that they had plenty of time to waste on the hilariously pointless six-axis accelerometer gimmick. I just hope someone up the ladder realises that the complaints about the controls are not like the usual unwarranted noise and fix it before the reputation on consoles sticks. All they had to do was leave the existing bindings editor alone and adapt it to the console APIs, BOOM everyone is happy! Doing that might not be a cakewalk but it certainly isn't... rocket science (that gag will never get old).

RAM is not going to be the weak link. As radonek advised, check the size of your KSP directory on disk and it's RAM usage will be less than that. Even with 75 mods it's probably not even near 8GB, let alone 16. I wouldn't bother upgrading the RAM, 16GB is huge and you'd be very unlikely to see any benefit from upgrading.

Yeah man, pin away. Anything to help my fellow console peasants!

Hi all, As a longtime KSP fan who was very disappointed with KSP's dodgy control scheme and lack of configurability on consoles, there's no doubt that Squad/Flying Tiger must know how fans feel about the control scheme by now, so I'll try to add something more constructive here. So as it turns out both consoles do allow some buttons to be remapped, and while it may not be a huge help with many of KSP's context-sensitive controls, it might still come in handy for some. PS4 - Dual Shock 4 (scroll down to Button Assignments) This tool is fairly basic and doesn't allow inverting axes, duplicate mappings to the same button/function, anything with the touchpad, or any other options besides basic "like-for-like" input swapping. Xbox One Standard Controller Xbox One Elite Controller This one seems a little better than the PS4 equivalent, but seems have a few artificial restrictions in place that mean you have to have the pricey Elite controller to get the most out of it.

I know how to do it, but I'm not gonna drop $40 that Sony reserves the "right" to steal at any time, by banning the account and refusing to refund it's purchases (that's their SOP to those who use secondary accounts to avoid their regional shenanigans). Even so, I'm not exactly in a hurry to play it anymore given the "picked out of a hat at random" control scheme.

I'd hope for that too if it weren't for the lack of acknowldgement from Squad regarding the quality of the console version's controls, along with no official word that there are any plans to fix them. As you said it won't make up for the failed release, but that little discount I mentioned would go a long way in showing that they care about it at all.

Nah, some platforms can get it right. Steam and Xbox seem to be handling KSP's simultaneous worldwide releases just fine. That line of thinking can be used to justify literally anything. "Microtransactions are standard operating practice. Get used to it..." "Garbage PC ports are standard operating practice. Get used to it..." Logic that can justify everything, can justify nothing.

False dichotomy. The options aren't between awful controls or no game at all. Having a configurable control layout is also an option. There's also a huge difference between "not perfect", "the controls are terrible with no way to change them". The former is nearly impossible to achieve, the latter is fairly straightforward. What are you, a bad argument generator? Wanting to be treated equally to others has nothing to do with entitlement, it's the exact opposite of entitlement, genius. And there's the old "you can't criticize anything you don't have a PhD in" non-argument. Sorry but you've never written a line of code in your life, afraid you can't have an opinion on anything to do with software development.

Excuse the bluntness but you are wrong. It's easier to build off existing code than to wipe everything clean and start again. Part of the reason to use an game engine (like Unity) at all, is to abstract away the differences between the platforms, making it easier to port code/features cross-platform. Rebuilding a new system that is worse than the old, makes no sense when the old system can just be re-used and applied to the new platform.

After looking forward to the PS4 version for literally years, I can't believe how disappointing and utterly botched the release seems to be. 1: I'm in the EU, my American friends are playing the game since yesterday. Why can't I play it too? When can I play it? I have my suspicions about what happened and know it may be out of both Squad's and Flying Tiger's hands, but if that's the case, you need to throw Sony under the bus and state that explicitly. Staying hush-hush about who's responsible for marginalizing an entire continent as second-class citizens isn't good PR, it's the kind of behaviour that people expect from companies like EA. Some things are out of your control, simply telling the fan-base what happened is not one of those things. I think a small discount to European PS4 customers (when it eventually does release here) is in order, as a show of good faith. 2: Where are all the control options? Everyone knew the control scheme needed special attention if the game was to work on consoles. It's easy to understand that designing such a complex control scheme on a limited input device is hard to get right, but with this in mind, it's also glaringly obvious that the only control scheme that can work for everyone is a user-configurable one. That means custom bindings and some decent options for tweaking the controls. Fortunately this is already there and only needs adapting to different platforms, unfortunately neither Squad nor Flying Tiger want to go with the obvious no-brainer that works for everyone. The game doesn't even allow inverting the vertical camera control for god's sake! How does anyone work in the games industry and not know that some people are "invertees" who will never be able to comfortably enjoy a game that doesn't allow this incredibly basic feature? Rather than leave it there and adapt it to the console's input APIs, Flying Tiger instead opted to remove it from the existing code entirely, while wasting everyone's time with pointless gimmicks like the accelerometer controlled mouse cursor. "I wish I could control this cursor by tilting a gamepad" - said nobody ever. And did nobody at Flying Tiger get the memo that both the Xbox One and PS4 allow full keyboard/mouse support? Sure, the game must work with a controller to be on consoles, but why does that mean they had to go and remove the already existing/supported KB/M input? The platforms support it, the bindings are already designed and chosen, why remove the only thing that gives players an alternative to the clumsy gamepad layout? None of these control issues are a "console thing" as plenty of "PCMR" types would love to paint this as... this is squarely a KSP thing. Several console games support custom button bindings, several of them support keyboard and mouse, several of those are on built on the same Unity engine, all of them support inverted camera controls. There's no real excuse here, the companies involved simply didn't care enough about the game to do the most basic, important part of it any justice. 3: When can console players expect to be able to enjoy this game with reasonable controls? Are they forever doomed to be stuck with the biggest turkey of a control scheme ever, while nobody at Squad or Flying Tiger will even talk about it (ironically for fear of bad PR)? Is there any plans to do what was obviously the right move from the beginning (just leave the existing controls the hell alone and add to them to properly support controllers)? Myself and a few friends really want to play this on PS4, but can't justify throwing money down the toilet until we can be guaranteed that we can actually control the damn thing comfortably. C'mon guys, these are amateur-hour, rookie mistakes anyone could see coming a mile away. Making those mistakes is bad enough, but don't be that company who sneers at what the fanbase wants, never even acknowledging any controversy.

Unity might theoretically be platform-agnostic, but in practice we already see quite a few platform-specific bugs. As for performance being sufficient, the PS3 has 512MB of RAM. Not just VRAM but total RAM, shared by both CPU and GPU, I just don't think that's enough without a serious overhaul. Don't have time to hunt down a reference right now, but would say that IPC isn't a good measure because it fluctuates between the type of application being run. My overall point is: less power than high-end PC parts, is not the same as "not enough power to run KSP". I run KSP on an Intel 2.93GHz Core 2 Duo (dual-core), which is actually above average according to the Steam hardware survey. All a console has to do is beat the average really, which they do. They still run AAA games in 1080p at 60FPS and that's what counts. KSP would be a cakewalk for newer consoles as long as the physics could be offloaded to other cores or preferably the GPU.

Lots of misinformation floating around in this thread... for a start, yes consoles allow downloadable games; last generation had many, very successful digital-only releases (Minecraft, Trials Evolution, Toy Soldiers, etc.). The current generation allows every game to be downloaded digitally, on the same day as the retail release. Anyone who doesn't know this is either living under a rock or not very interested in the gaming industry. Just because the components in consoles may not be quite as powerful as desktop counterparts, doesn't mean they magically become useless crap. A current-gen octo-core, 1.6GHz console CPU is still in the range of a quad-core 2.5GHz - 3GHz CPU, nothing to scoff at and certainly beats the ass off any dual-core CPU (which the majority of Steam users still use). As for GPUs, consoles are generally a notch above what most PC players are using and with the latest generation, same goes for RAM. Consoles can and do allow mouse and keyboard input and yes this functionality is available to game developers, Counter Strike: Global Offensive allows it on the PS3. It's entirely up to the developer, if they think their game works well with a mouse and keyboard, there is console platforms that will accommodate them. That said, the PS3 is very likely not sufficient for KSP, for a few reasons: - It's CPU uses the IBM Cell architecture - KSP was built for x86. - It only has 512MB of RAM - KSP loads all assets on launch and they take up more than 512MB. - It isn't a very powerful machine overall, being built long before development on KSP was even started. The PS4 and Xbox One on the other hand... - Both use an x86 CPU architecture. - Both have 8GB of RAM. - Are pretty damn powerful as far as cheap computers go, and were built fairly recently. All gaming platforms have their pros, cons and target audiences, acting like a fanboy/elitist only shows ignorance of the industry. Attempting to speak for the console market, saying that they'd never appreciate something like KSP, is similarly stupid. I'm primarily a console gamer, who loves me some KSP, would certainly buy it on a console and have convinced at least 5 other console gamers to buy it, who also love the game. People pay cold, hard cash for all kinds of games on all kinds of platforms, anyone who can't accept that will just have to #dealwithit The major hurdles to getting KSP working on next-gen consoles are parallelism, input and licensing. It would require Unity to allow physics calculations either on multiple CPU cores or an AMD brand of GPU, something that I don't think it supports yet. It would require either a keyboard and mouse, or a major overhaul of the controls and GUI. As far as I know neither console allows unfinished "early access" games so it'd really only be possible for the 1.0 release. Despite these challenges, I'd love to play KSP on my PS4 and it would allow a much wider audience to enjoy the game so I hope it happens.

As a "master-race purist" who's flown hundreds of stock Mün missions, using Mechjeb would probably make this harder! (disclaimer: though I personally prefer manual flight, Mechjeb is still a great mod and r4m0n is a great programmer)

Looks like a nice balance between replication and utility, I like how you made up for the lack of a wider first-stage tank with the cluster of smaller ones. I agree that plastering loads of useless crap on a craft just for the sake of replication is silly. You'll always get historical-accuracy-nazis who'll try to find a flaw with anything, as KSP clearly isn't meant to recreate exact replicas, who cares about such petty opinions (if such two-word, drive-by comments can be called an opinion at all).

Never had any trouble with the big docking port, it's got a texture that you can see during placement. I stopped reading right there. Squad cannot be held accountable for people's lack of patience and unwillingness to check their work. Agreed, looking at that quote it does look like case of "change your game to pander to reckless clowns!".

Alienating users just because they don't use the same OS as you is petty, childish and self-defeating. Macs are just another brand of PC and Linux has more users than you think, especially in the KSP community. You don't need Java for Android or a mac for iOS, because a web app will run on all these platforms, like Olex' interplanetary calculator for instance. Web apps can also run without an Internet connection after being downloaded. It's not 1995 anymore, Mac and Linux use is rising, mobile web users already outnumber desktop users and the most popular OS is a Linux one (Android), any programmer who can't adapt to this evolving landscape will just be left in the dust...

Hey guest91111, while it's nice of you to take time to make tools to help others, your distribution method is lacking; hardly anyone wants to download and run random executable files from the Internet, and with good reason: - the source is not viewable, so that .exe could be doing virtually anything, like installing malware. - no description or screenshots, the only way to find out if you want it, is to download and run it. - not cross-platform: leaves out Mac, Linux and mobile users. Your approach demands too much trust from the user, and takes too much time and effort to even sample your program. These kinds of utility tools are better suited to web apps, where anyone with any OS, can just click one link to sample it, without much risk of malware, and if the program doesn't live up to their expectations, they just close the browser tab. If you haven't learned Javascript yet, I highly recommend it, it will be a breeze if you already know C++ or C# and will allow you to distribute these tools as much more user-friendly web apps.

There's no shame in admitting that you simply don't have what it takes to make orbit

, one of my favourite scenes. The forum doesn't host users' screenshots as far as I know (bandwidth concerns), I'd recommend hosting them on imgur.com and linking to them. Avatars must be 64x64 and profile images can be 100x100.