Search results

Well, infinite RAM is my problem.

People I ask all say that lacking of feature updates for months or even year is the exact reason why they gave up playing. And I'm not talking about one or two people, I'm talking about one or two dozens whom I've seen in some chats. I would even be grateful for just one tiny thing - a radial...

If you consider something cool it doesn't mean everyone should do the same. 1.5 killed my interest to rovers and some already deployed ones too. Yes, it brought clipping, but I don't use it much, only when I can't do without it. Also 1.5 brought some problems like parts showing from under the...

I don't know for sure how much the update changes anything until I can try it.

Oh, you're of that kind who believes in updates :D

Update is a lie :)

It will look just like the blueprint editor, only different buttons for groups assignment.

Yeah, KSP way of opening the same editor both in assembly and in flight seems good to me.

Yes, you actually get it. I mean separate tanks, but added to this virtual group which makes them do their job simultaneously when one tank from the group is tapped. Like the RCS - they're all one group. Tap one - activate all. The same idea for virtually grouped tanks and other parts, but you...

You didn't get it. I literally said that you just tap one grouped tank and the others are activated with it. Then you tap the destination tank just like you do it now, but fuel transfers from all grouped tanks, not only from which you tapped.

Yeah, you cann connect them, but I'm talking about side boosters and about simultaneously refuelling multiple tanks, not making it one.

Nah, I don't like automatic flights.

It's not really staging, but it can be used like that.

I don't know how sr2 works, I just came up with this concept on my own.

Okay, so the idea is: after selecting some parts in the editor show one more button - "create a group". The effects I suggest: Every part in a group responds to any other part activation, for example you tap on one solar array or engine or parachute and they all do their job simultaneously. Also...

I'm not saying it will make it come quicker. I'm saying it will make people see the work is actually going on and that will ease the waiting.

Just saying - it would be easier to wait if people see some progress updates. Weekly for instance. Or less frequent. The point is that we don't see any work and some progress updates on what's the situation would give us some clue about development state.

No progress updates or new peeks yet?

Then he should have asked the others if they want a trailer or would a changelog be enough.

I still prefer changelogs and manual examination to trailers.

Btw why is he doing the vid so long? People make SFS stories on YouTube faster :confused:

The only thing that bothers me is that I don't need a trailer but I have to wait for it anyway.

Dunno, I like participating in betas of projects I like. It's a pity there's no way for me to participate in SFS beta :(

Never heard of 1.4 beta at all.

Why would anyone need the least efficient?