Day and night time change in VAB and SPH ???

[Xzabath]

I heard that day and night were supposed to be seen in the VAB and SPH, I do not see it, is this a setting or did this not go live?

[zxczxczbfg]

Unfortunately, the SPH/VAB both only use daytime in 0.21, but we eagerly await the day in which that will change. Day/night DOES change in the Space Center view, though.

[skyace65]

Unfortunately, the SPH/VAB both only use daytime in 0.21, but we eagerly await the day in which that will change. Day/night DOES change in the Space Center view, though.

thats because the buildings when making something isn't a live view of the world while the space center is.

@ OPand i don't remember them promising time change with the SPH and VAB before the update

[Bean]

The spacecentre view doesn't load any craft that are at/around KSC, which is a bit disappointing, though it would reduce lag

[TheChizzaberry81]

I still think the idea of making it change while building would be cool. There is lights in the hangar and the VAB, but it's daytime always so they don't make much of a difference. It's just memory that might be a problem, especially with a not so super computer like mine.

Edited January 1, 2014 by TheChizzaberry81

[MalfunctionM1Ke]

I heard that day and night were supposed to be seen in the VAB and SPH, I do not see it, is this a setting or did this not go live?

I think you are mixing something up.

Before the new KSC was implemented, it was always daytime outside the KSC.

Now you will have day and nighttime outside the KSC but it is always daytime when you are inside the VAB & SPH.

As I heard B9, who created the new KSC, is no longer working for Squad. So I dont think that the Cycle will be implemented soo.

[Firov]

I think you are mixing something up.

Before the new KSC was implemented, it was always daytime outside the KSC.

Now you will have day and nighttime outside the KSC but it is always daytime when you are inside the VAB & SPH.

As I heard B9, who created the new KSC, is no longer working for Squad. So I dont think that the Cycle will be implemented soo.

Wait. They already eliminated Bac9 too? And he was just recently hired too.

Nova, Bac9, Claira. With all these purges I'm beginning to think SQUAD went to the Stalin school of business management.

[sal_vager]

Claira still works for Squad, Bac9 left of his own accord as he wanted to work on other projects

[Firov]

Claira still works for Squad, Bac9 left of his own accord as he wanted to work on other projects

Really? Well, that's good news at least. I mean on Claria's status. Too bad about Bac9, but if it was his choice and not SQUAD forcing him out then that's okay too.

With the communications blackout, a bit concerned. SQUAD should do another blog post listing the developers/introducing new developers like they did a month or two back.

[Liowen]

Really? Well, that's good news at least. I mean on Claria's status. Too bad about Bac9, but if it was his choice and not SQUAD forcing him out then that's okay too.

With the communications blackout, a bit concerned. SQUAD should do another blog post listing the developers/introducing new developers like they did a month or two back.

Time writing up a blog entry, or staying focused on the game? Personally business matters should stay in house as it is not anyone's business but those employed by SQUAD, until there is need for it to be made public. The game should always be thought of first, and personnel dealings second. It is seemingly people are thinking they are entitled to know everything in a business, but in reality they are getting third and fourth hand hear say. All this does is create false information and post going off track, much like this one has, over information that is not needed in the post to begin with.

[Firov]

...

I think you misunderstand.

First, for context, please view this forum post. http://forum.kerbalspaceprogram.com/content/187-An-Update-on-the-Team

Time writing up a blog entry, or staying focused on the game?

On the surface this is a valid concern. But just how far does this line of reasoning extend? Should Harvester no longer make his usual blog entries? Should the developers and SQUAD staff avoid the forums at all costs? And how about those developer videos/interviews? That's got to be a huge waste of time right there.

No, the fact of the matter is, part of the reason KSP has such a dedicated following isn't just because it's an incredible game. It's because the developer isn't some faceless EA clone. They've historically not been afraid to communicate with their customers and fans, to reveal future features, to answer community questions (within reason), etc. They've even hired modders from the community to be part of the development staff. That's special right there. That's not something any ordinary developer is going to do. Unfortunately, you seem to want them to retreat into an impenetrable shell. To become a cloistered order, a faceless developer slamming out code from the confines of a small windowless box. But to have that happen would be a huge loss not just to the community, but arguably to SQUAD itself.

All this does is create false information and post going off track, much like this one has, over information that is not needed in the post to begin with.

And that's why it's not a bad idea to have a brief blog post like the one I linked to, just having the developers say hello and introducing new members of the team to the community. So they can generate even more positive PR while shutting down any rumors and/or false information.

Please realize, I'm not talking about personal, or even necessarily employment details here. I don't think anyone cares when Harvester showers, or what the pressure in his car's front passenger tire is. Just a very brief meet and greet like in the previous blog post.

Finally, this isn't a "demand" on my part, and I have no authority to "demand" anything of SQUAD anyway, even if I wanted to. People seem to be getting that confused. It's a "would be nice". Especially since they've shown a willingness to communicate with us on that level in the past.