NoMrBond

Squad has subsequently hired BlitWorks to substantially revisit the porting work they'd paid for once already, it's not like they've hung the console users out to dry and washed their hands of it, even if the timeline feels unacceptable, or even punitive. Submitting PSN and XBLM updates costs a bundle (think ~five figures per platform per patch), plus takes a great deal of paperwork with bureaucratic approval to push through which means PS4/XBOne users can't get the kind of rapdi-fire/ad-hoc partial/beta/pre-release updates Steam/SquadStore users have recently gotten (if they opt in to help with the QA/QC portions of the release), GOG users have the same issue (no pre's) due to similar platform specific approval process. It's happening, possibly (almost certainly) not as fast as either Squad or you would like, but it is happening.

Unity uses the CPU branch of PhysX, not the GPGPU (CUDA) branch. Your CPU's single thread FP performance will be the main determining factor in physics sim speed. KSP's default graphics are pretty light on the GPU (mods like Scatterer/EVE/SVE/SVT can nail it pretty hard though).

Continuing the theme of weird requests... any chance of making the 64 bit player the default when launching from Steam, or a way to make that selection permanent (without resorting to %command hijinks in the launch options) Even having the 32/64 picker show up when you launch from a steam shortcut would be nice, currently you only see this if you launch from the library list inside Steam which is a bit inconvenient. And yes I know you can make a direct x64 player shortcut, but if you launch the executable directly you don't get the Steam overlay (or the option for Steam screenshots) etc

Will the Russian themed missions launch from Baikerbanur? Because if you're gonna build an R-7 themed Vostok, well, lets go all the wayyyyyyyyyyyyy

Thanks @TriggerAu Fingers crossed for KSP 1.4 running on Unity 5.6 so we can launch a Vulcan using Vulkan then

Talking of squishy things... any chance of the world cup soccer balls making an appearance in 1.3?

Sure, but currently it's on 5.4.4 while 5.5.2 is available I mean, I'm assuming it's going to stay on 5.4.4 otherwise the 1.29pre would have come out on 5.5.2 since it's probably way too late in the piece to implement that The 5.5.x branch has some nice stuff (I'm looking at the line/particle system upgrade mostly, but the FBSS and compiler upgrades are also nice)

Will KSP be making the jump to Unity 5.5.2 during the 1.3 update process or will it be remaining on Unity 5.4.4?

One of the defining technologies (for the Saturn rocket) was the use of Hydrolox for the second (S-II) and third stages (S-IVB) giving it a massively improved payload to orbit vs. the Kerolox and Hypergol alternatives of the time. While the current LF/O and mono would stand in pretty well for the first stage (S-IC) and the LEM/CSM engines (respectively), will the MH-DLC have any concession for these lighter/less-dense yet more efficient cryo fuels?

Well we're about an hour out from the important announcement, does that make it guess o'clock? KSP 1.3 based on Unity 5.5.2? KSP 1.2.2. console release, also bringing Console KSP to regions currently without? More collab stuff like ARM/NASA, maybe with ULA (since EJSA and others were already making an official ULA pack for KSP), ESA, JAXA or SpaceX?

Please tell me you have a UPS now to isolate it from your abodes terrible power system

I was hoping that, given the programming manpower which Squad has picked up recently (the last three hires have all been experienced programmers with some serious shipped-game pedigrees behind them), that part of the 'secret' feature might be a broader code refactoring away from Unity's GameObject (which isn't threadsafe) to a custom implementation (I believe FromTheDepths also did this, however that's back on Unity4 so I'm not sure that still applies?) to leverage more advantage from multi-threading (if there's a realistic gain from the effort). If stuff is in QA now, I wonder when we'll start seeing release candidates for 1.2.3 (if it's bugfixes) or 1.3 (if it's a feature update)? They were looking for a lead artist too I think, I wonder if they've had any bites for that position, since having a lead artist in house is probably a requirement for the art/model overhaul which is capturing so much... hot verbage

If the KSC/Planetary (non-scaled space) textures/assets were moved into asset bundles, they could be dynamically loaded/unloaded as necessary

Unity Technologies itself (upon which KSP is built), also has a pretty nice roadmap broken down into five sections from live to (essentially) gleam in the eye type stuff. Oh how I wish the GC, .NET Profile and Runtime upgrades would move up a place or two though

The current wing selection is a bit small, not selection wise but can require a large number of wing elements to be stitched together While you can now hold them together better with AT:Autostrut's, this exacerbates the physics slowdown you already get with lots of parts. If you could switch up their size a bit (like the 2x2 panel is available), that could cut down on the number of wing parts by 75% (in some cases), and could be done with either MODEL{} calls or scale arguments, although having this accessible as an advanced tweakable rather than further discrete parts would be preferable (so as not to clutter up the parts selection).

Keen Software House had success putting the whole codebase for Space Engineers up on GitHub and accepting patches (pull requests) from the community, this didn't happen immediately or fully, but it did eventually become full open access (not open source). Maybe Squad could talk to Keen and see how's it working for them, and if they could gain any similar advantages?

A more advanced 0.625 engine option would be nice, personally I think a tiny RAPIER would be awesome, even if it ended up being something like the SCIMITAR/A2 instead of the full SABRE dual-mode capabilities. There are a few gaps in the parts lineup which would be nice to address. I don't mind filling those voids with mod/s, but not everyone is happy (or even able) to do so.

Greetings Robbonaut and Ziggy Patches and future plans too, neato!

Marce used to have the Blast Awesomeness Modifier mod, I don't know if anyone picked it up since Marce sadly left however

From memory Sarbian thought the particles were probably appearing (generating?) in the wrong layer (can't remember the specifics, if you search back in the thread, or maybe in the Smokescreen thread it shouldn't be hard to find) Smokescreen may gain the ability to force them into the correct layer in a later version (when Sarbian's time allows).

Squad are currently looking for developers with HLSL experience, hopefully they can find a shader wizard to carry out an overhaul I thought KSP was going to switch to Unity's Standard Shader, I guess it may not have gotten on with KSP's unusual camera hierarchy?

Got a huge community of modders you can call on too, run a competition separated by agency (i.e. make a Rockmaxx pack, pack must use colour palette X, Y & Z, is 2.5m parts etc), offer prizes, get your name in lights etc Would need to be firm about sides/profiles, node sizes, textures etc Squad's building up their programming & asset people though so maybe they'd rather keep it in house?

Official Kerbal Beards mod!

Do you have the EVAvisor texture in GameData\TextureReplacer\Default directory? The visor being total opaque can mean the texture is missing

Urg, the alpha channel is never handled properly for PNG's if you actually use the alpha channel, it's infuriating Instead of RGBA, stick with RGB and create a layer mask (alpha) and put what you want on the alpha channel in the layer mask, when you export to PNG it should work properly (from memory)