NoMrBond

Fair point, I should have tested it correctly before skipping straight on to musing Will sort out a clean KSP install and do Scatterer-only/RealPlume-only/Scatterer+RealPlume

Sorry, I've taken a few shots here (imgur isn't saving the order for some reason, I may just record a video) imgur.com/a/6mEWA The plumes seem normal until ~14000m altitude or so and then start getting bright/white/blobby Perhaps this is when the plume expansion is kicking in

Scatterer seems to act on the particles produced by SmokeScreen (under RealPlume), which possibly isn't intended (it certainly makes them look super-bright/blobby if your point of view places them above the atmosphere, especially transecting the horizon) Is there a way to get Scatterer to not effect the thrust/exhaust particles, would SmokeScreen need to generate those particles on another layer for this?

Just working through the installs myself so the Stockalike Station Parts Expansion 0.4.1 is the one with the old module manager file

Kartoffelkuchen had a Raptor over here about three weeks ago now, not sure about its current release status however >

Is the probe core running out of power?

The issue is the license type, Romfarer released Lazor system under CC3.0-A-NC-ND, the -ND is No Derivatives From the Creative Commons site; NoDerivatives — If you remix, transform, or build upon the material, you may not distribute the modified material. Which is why I asked about relaxing the licence, as the -ND clause of the current license prevents any prospective maintaining author from releasing any updated work to others (including the community at large)

Alas Frybert I was at the pub enjoying the southern antipodean spring beergarden atmosphere, and blazing Sichuan noodle dinner I bet @Avera9eJoe up next!

It is time for the return of glorious fire! This is only meant to notify @Nhawks17 about the dependency update

The Unity update (to 5.4) involved significant changes to the particle system, as well as exposing new features (some of which I think Smokescreen had custom implementations for already?) for the system, so any update for Smokescreen may end up being quite "deep" to flex/hook the changes. After the debacle in the MJ thread, yesh, I'll just be extremely glad if there is an update, on whatever terms and on whatever timeline Sarbian feels like

Perhaps VendowShine?

What about getting the shader added to the game itself, if that was an option?

2.5 just came out with reflections restored, was this, I'm hoping, related?

RangeMachine is maintaining a fork of TR until Shaw comes back, maybe they could help?

Life support requirements for crew may be needed to balance this out (so you'd be trading off between probes needing CommNet connections and Kerbals needing supplies) At the moment there's minimal trade-off, dV is plentiful and Kerbals are perfectly happy to sit in a 1 man pod for a 200 year round trip to Eeloo without aging, or needing to be kept warm, be feed, stretch or, uhh,... output. Maybe you should also need to investigate a planet with probes before you can EVA there (get the temperature and pressure at least) It's a complex problem because whatever they do needs to feel like an internally consistent part of the game, without being a weird artificial roadblock or overly punishing.

This fantastic, thanks @DefiantZombie

I was suggesting it was more likely for the particle system to get some attention because Sarbian is onboard with Squad now, not less likely because a mod exists for it That said, you probably want to make any 1.2 specific suggestions down in the 1.2 forum, rather than the general suggestions forum

Smokescreen already lets you do this (if you're not mod averse) Otherwise 1.2 already seems to handle particles a lot better (if you haven't tried the 1.2 prereleases), plus Sarbian is doing development for Squad now, and Unity 5.5 has a significant particle system upgrade so... fingers crossed for KSP 1.3? (since it's too late to add features for 1.2).

I was thinking of the XLR87/LR87-3 for some reason instead of the H-1 H-1 is nice because you get S-3D to X-1 to H-1 to RS-27, uhh... I guess that's not really applicable to stock

Ungoof it, carpe jugulum! I suggest 256-290, for... uhh, no reason in particular. /cough

I hope the final revision of the upgrades system allows you to toggle/cycle between the various (clean / boat-tail aero cover / compact base) setups rather than having each one as a separate 'pick' in the SPH/VAB parts lists, that feels like it would get super cluttered super fast.

I am aware, I was suggesting that the difference could be addressed through the upgrades system so that the improved engine isn't locked to the current twinmounttank

I like the plan overall, although I would prefer it if the TwinBoar was split up into its component parts instead of being a single-purpose/single-unit aggregate part Separate them out into a nice mount (2.5m top to 2x 2.5m compact at the bottom, would then take any other Size2 w/ compact base), and the ARM 2.5m tank, the Boar is already there as a distinct part Make the 2.5m ARM tank an upgrade of the 2.5m Jumbo64 with a better mass fraction So to make the "TwinBoar" you assemble the upgraded 2.5m tank, the Twin mount (2.5 to 2x2.5c) and two Boar engines (which you've upgraded via the TechTree to access the compact mount).