Dementropy posted:

Fidelitious posted:

This is what confused me about the whole thing. Server meshing doesn't magically teleport the data you need around, in the end data still has to end up at each client.

BigglesSWE posted:

Yeah the design itself isn’t bad honestly.

I’m not into tattoos myself but the idea of inking a corporate brand on your body strikes me as sad.

disposablewords posted:

That is a major thing that keeps me from ever getting a tattoo. (Aside from the cost, which I would always want to put toward crap like books and video games first.) Almost any symbol or image I can think of, I can't guarantee I'll feel enough passion for in five years to want to mark it on my body permanently now. Especially if it's an image strongly associated with a company or IP because woo imagine making a permanent mark of brand loyalty.

Tippis posted:

The scenario as envisioned by CI¬G and the citizens is this:

You have a grandiose space battle with 5 Idrises, each with 50 people on board. Obviously, a single server can't handle all 250 players + 5 super-customised ships at once, so let's mesh'em-up! One server each for the idrises, only dealing with 50 people — easy peasy — and one server dealing with the space combat — also easy.

This conceptually (and even practically) works.

…except…

…then you start extrapolating what this means for the players involved, and the reasons why you even bother with the exercise to begin with.
The pilots must see the combat they're engaging in. They must therefore be present in the space combat server as well, in parallel, and anything that happens to them in one place must happen to them in the other. Conversely, the ships themselves must obviously be present in their respective shards as well as in the space combat, so that when they take hits, this is reflected inside the ship so people can run around and extinguish fires and change fuses and use repair guns and so on

And this holds true for gunners shooting into that battle, and anyone looking out the window — and why would you even bother if you can't even look out the window as see the space battle? So suddenly, the situation has shifted: 5 servers dealing with 50 players + 5 super-customised idrises each; 1 server dealing with the same super-customised idrises plus, oh let's say, 50 pilots, gunners, windowlickers, all of which needs to be duplicated (or sextuplicated) everywhere instantly, in real-time. We started out with 250 players and 5 ships not fitting into one server; we now have 300 players and 30 ships that need to be juggled by 6 servers… unless we actually want to see those other players, and not just the ships, when we look out of the window. After all, we're supposed to be able to fire from one meshed server across another and hit a player into a third. So all those players at the windows need to present in all servers. So… 5× 50+50 player + 5 ships for the internals; 5 ships + 50 players for the space combat; a total of 550 player and 30 ship instances to juggle.

But wait! Wasn't the appeal that you could seamlessly move from one ship to another and do boarding action with inevitable consequences? And that server meshing was supposed to make that possible? Well…

Two crews decide to board eachother, and everyone jumps out into the space combat. It must now deal with 5 ships, 30 crew still in their ships, 100 people floating in space shooting at each other, and of course, those 30 crew looking out at that mess must now get the information about those players. The situation is that each ship server has to deal with: 5 ships (2 of which are just floating, admittedly), 50 crew onboard, 100 crew outside the window. 750 player instances and 30 ship instances in total over 6 six servers, most of which are just copies of each other and need to be synced everywhere. We can't spin down the empty ships because the whole point is that they're about to be boarded any second now…

To effect the dream outcome of using server meshing to overcome the limits of a single server, we are rapidly approaching a scenario where we have 6 servers, each of which has to deal with the very situation we deemed impossible and which required the meshing to happen to begin with. We've increased the workload by 500% to arrive at the same place where we started, with nothing gained (other than at the Amazon billing department).


The only way for server meshing to work is to remove the very scenario it is meant to enable: sorry, you are not allowed to exit the ship or even look out the window — instance is full. Pool is closed. Keep repair-gunning that fuse box.

Fidelitious posted:

This is what confused me about the whole thing. Server meshing doesn't magically teleport the data you need around, in the end data still has to end up at each client.
The separate servers for different areas is fine when the areas they're handling are far enough apart that there are basically zero interactions between them, but once things are in interactable range you absolutely must have them on the same server or you're duplicating a bunch of communication and adding latency for no benefit. The intelligent scaling down of how much data is being sent between clients (full physics data for explosion vs. "this thing blew up") can still be done on the same server so no need for meshing there.

Dynamic servers is fine for your basic 'zones' where they can scale based on population or whatever, but there's a reason Eve uses TiDi for huge battles. And SC can't use that in a real-time FPS shooter context.

I guess Chris thinks he can defeat the laws of physics.

Renfield posted:

If I saw that tattoo, and didn't know about Star Citizen, I'd just assume he was a White Supremacist.

Renfield posted:

No one is thinking like a 1990s Games Gru, who "wrote" single player, off-line games.

Pixelate posted:

So the demo parped a bit...

quote:

There's a 'green authority' pico in the purple server.

https://www.youtube.com/watch?v=6jIaH_0ylCw&t=22s

quote:

* On the red server view a 'green' Pico gets shot into the streamed-out purple server (and falls down into the abyss).
* On the green server view it doesn't move at all.
* Another player then shoots the unmoved green Pico into the wall. On the green server this is fine.
* On the red server it teleports out of the abyss back to its original location so it can get shot into the wall.

https://www.youtube.com/watch?v=3UstOWL_oes

JammyB posted:

New Golgot100 short video showing the mesh bugs from the presentation.

https://www.youtube.com/watch?v=KLlREqobgj0

dr_rat posted:

Is one of the worlds in pyro at least a world that is always on fire (Oceans of lava would be close enough)? I feel like for a star system called pyro you need to have that at the very least.

I mean there is always the sun, but all star systems have at least one of those, so that doesn't count.

quote:

Pyro I is a charred black rock that is slowly discorporating into the system's star. There is little of interest here;

Monox (Pyro II) is a coreless planet that will, in time, fall into its star. ... for all practical purposes the world had become an empty husk. The planet is named for the abundant Carbon Monoxide in its atmosphere.

Bloom (Pyro III) is an icy terrestrial world with a breathable oxygen-nitrogen atmosphere. It is known as a haven for outlaws.

Pyro IV A rocky protoplanet that has been mined clean.

Pyro V is a massive yellow and green gas giant that's slowly pulling Pyro IV into its orbit.

Terminnus (Pyro VI) -This protoplanet suffers little damage from Pyro's distant star. The outermost planet in the Pyro system, this subdwarf would be unremarkable if it were not the home of Ruin Station.

bandaid.friend posted:

I fully believe in Chris Roberts' ability to deliver twice as many barren empty landscapes as in Starfield

trucutru posted:

Mmmm, let's see... nope! but there is an *ICE* planet

Xakura posted:

How? He took 10 years delivering what, 5? And starfield is 900 ahead.

slandergoose posted:

I wonder how SQ42 animations are gonna compare against this:

https://www.eurogamer.net/gta-6-has-patented-a-new-locomotion-system-to-make-highly-dynamic-and-realistic-animations

akkristor posted:

Star Citizen is supposed to have, what, 95 fully fleshed out star systems at launch?

They have two. And that's being generous.

In over 10 years, they have two of 95.


You know what, let's give them the benefit of the doubt and say that their 'pipelines' will save them a metric poo poo ton of time (that's 10 metric rear end-loads), and from today forward they can fully complete 1 system every month. Design, implementation, content, unique NPCs, unique cities on unique planets with unique biospheres. Everything they promised.

That's still over 7 years JUST to get the star systems they promised. At 1 a month. When they've not even completed these two in over 10 years.


And people thought Starfield was empty.