******Official Star Citizen / Squadron 42 Thread******

In fairness to the clouds and the system that goes with them then weather comes in which will directly affect gameplay be thar flight or FPS mechanics etc.

So the first stem is getting what thet have so far in. Then to link that up to the driven atmospherics now they know the dynamic cloud movement and construction works etc.

It's the first step in what we saw at the end of that video/concept gameplay at CitCon. As a single thing it doesn't add anything gameplay other than visuals.

Noting also though that things like the shadow and cloud system would affect the NPCs vision system they showed too if it gets dark enough so there that too.
I understand that, but if we are all honest with ourselves should that really be a priority as let be frank, there is sweet FA to do still. Thats priving it don;t crash 30 mins into the game.
 
Right , I'll put it as plain as I can.

Resource allocation optimisation !

The other teams have all the resources they need, they only thing they need is time to do their work.

This is like getting angry at a bus driver because the cheesemaker hasn't got his latest batch of bree out the door.

And where would those working on the clouds and rivers do then? Work on server meshing?

They wouldn't be able to as it's quite a different field.
 
Last edited:
I understand that, but if we are all honest with ourselves should that really be a priority as let be frank, there is sweet FA to do still. Thats priving it don;t crash 30 mins into the game.
I mean flight inteaction should to some extent. Flight in atmosphere where it adds challenge and such would be good whilst doing those simple missions or say dog fighting whilst in a storm would be pretty epic be that the bounty chasing or using it to escape from.

There are some things to do, they just break often cause where at. That will ne same till at least 1.0 at earliest anyways.

It isn't I don't think the verse is empty or nothing to do, just cause how spotty it runs it males it hard to do etc.
 
The thing is, whilst the respective teams are adding all this there is still the base that is't even remotely stable thus compounding issues further
Go read a couple of pages back where i explained how adding feature a b c, polishing it and then adding Feature D and all of a sudden Featre B is broken post.

Also go watch that video that was posted by humbug.
 
The thing is, whilst the respective teams are adding all this there is still the base that is't even remotely stable thus compounding issues further
In fairness they have enough team there to do the updates that will provide stability. The systems take time and are complex. They are clearly working on such stuff with the base though. And you can only have so many cooks in kitchen. Imagine having instead of just you or you and one other to install a roller door you added another 8 people there. They couldn't help or be effective right.
 
The thing is, whilst the respective teams are adding all this there is still the base that is't even remotely stable thus compounding issues further

Oh I agree but the teams that do all the base stuff are working away in their respective departments but it's a slow process.

If they weren't making 2 games we'd likely have everything by now but they've spread themselves too thin IMO.
 
Last edited:
In fairness they have enough team there to do the updates that will provide stability. The systems take time and are complex. They are clearly working on such stuff with the base though. And you can only have so many cooks in kitchen. Imagine having instead of just you or you and one other to install a roller door you added another 8 people there. They couldn't help or be effective right.
As said, this guy pete needs to watch the video humbug posted only a page or two back that explaiins all of this...
 
This past couple of weeks has been absolutely awful.

Phase one of the missions took several days to complete, including a six hour session with no successful completions. Stranded pilot was either dead on arrival, never finished repairing his ship, or randomly blew up after a long period of time.

Phase two worked really well for me, only had one mission without assets spawning.

Phase three. I'm up to seventeen hours trying to complete this. All the usual issues. Idris doesn't spawn. Idris does spawn but the mission aborts for no reason. Or nobody is doing the mission on that server so it's impossible. Even completed a couple with no completion registered.

And now I can't even leave New Babbage in any region. US, EU, AUS, all the lifts don't work.

Ships don't get stored where I land, or I end up in a different place after.
 
This is the point I mean, Hell, half the time the lifts don't even work :cry:

Further adding complexity is not helping is it.
Fair fair but I don't think the cloud complexity are the issue with the transit refactoring they haven't completed which needs doing ASAP!! They are already working on that though so it's in hand.

Like the mission refactoring they just finished and in 4.0 so now it's a seperate service off the main server which should add stability to gameplay and missions and tracking etc.
 
This is the point I mean, Hell, half the time the lifts don't even work :cry:

Further adding complexity is not helping is it.
You just highlighted what others have said you are incorrect about.

There is literally a seperate team working on the transit refactor. So even if you tell teh cloud people to stop there work, how are they going to help the team already working on fixiing the elevators?
 
This is the point I mean, Hell, half the time the lifts don't even work :cry:

Further adding complexity is not helping is it.

Lifts, Trams, Trains etc... are all 1 team doing the transit refactor. Stopping the planet tech people from doing their work won't make the transit team any faster as it's different disciplines.

Kind of like network engineer and concept artist, Stopping the concept artist from doing his job isn't going to speed up the work of the network engineer.
 
Last edited:
The words "fly by" come to mind .

Both seem to be missing my point. so will just leave it as it looks like I've hit nerves .

You haven't hit nerves at all, I just think you don't understand how development works.

Stopping 1 team from working, Which is what you essentially want, Isn't going to magically speed up development of all the other stuff.
 
Back
Top Bottom