Game Discussions Star Citizen Discussion Thread v12

"and reduce infrastructure costs"
Lol 😁
Why lol ? With static servers, having 1 or 100 players in a server zone oblige you to launch the server. 3 zones next to each other with 3 players use 3 servers. With dynSM, you can have 3 zones served by a unique server (when 1 player by zone) or 3 zones served by 3 servers (when 100 players by zone).
 
If they ever expand the Pyro PTU to everyone they'll need to double their server costs (a bit more than double as there is the replication).

CiG really need dynamic meshing for themselves - there isn't much advantage for players over static meshing.
100 player for Stanton = 1 server for 100 players
200 players for Stanton+Pyro = 1 server for 100 players
 
oh LA ...

edit:
Static Meshing

100 players for Stanton = 1 server
100 players for Stanton + Pyro = 2 servers
100 players for Stanton + Pyro + Terra = 3 servers

Dynamic Meshing done right
100 players for Stanton = 1 server
100 players for Stanton + Pyro = 1 servers
100 players for Stanton + Pyro + Terra = 1 servers
?
Dynamic meshing will be used for small zones (an Idris, missions bunker, a floor of space station, players event, etc). There is no use for dynSM for a whole system.
 
1698419784617.png
 
oh LA ...

edit:
Static Meshing

100 players for Stanton = 1 server
100 players for Stanton + Pyro = 2 servers
100 players for Stanton + Pyro + Terra = 3 servers

Dynamic Meshing done right
100 players for Stanton = 1 server
100 players for Stanton + Pyro = 1 servers
100 players for Stanton + Pyro + Terra = 1 servers
No, that would mean with Dynamic Meshing player numbers dilate! Crobbers want it the other way round!
 
So, is it the Pyro as it will come to the PU or a Playground-not-Pyro? There was some indigestion on the Spectrum that this new system is very different from the promised Pyro. It is smaller, has more stations and no lava planet.

Starfarer owners had their dreams of refuelling players in Pyro squashed without any word of apology.
The lava planet was scrapped. I guess they couldn't make it flow...
 
....
Static meshing is not the goal but a step toward dynamic meshing. Dynamic SM will allow the system (in theory) to define on the fly the boundaries where nothing is happening, the number and the size of the zones. In the demo, instead of having 3 servers from the start, you could have one server for all, and when too much players are coming, the system will separate the zone in 2 servers. And afterthat separate in 3 zone if more players are coming. If successful, this will improve servers performance and reduce infrastructure costs.
So instancing then.
 
Why lol ? With static servers, having 1 or 100 players in a server zone oblige you to launch the server. 3 zones next to each other with 3 players use 3 servers. With dynSM, you can have 3 zones served by a unique server (when 1 player by zone) or 3 zones served by 3 servers (when 100 players by zone).

Edge cases aren't the best point of comparison friend. You can create any scenario you want from those...
 
Players are merrily documenting the ways in which the F8C is OP ;)


IMO, the top speed is the worst part of the ship. It can basically dip from any engagement by shift-w. I would rather see it somewhere between 1100-1200. The rest actually feels pretty balanced for it's role.

Shield needs fixing to be front and back half's instead of bubble.

Seems a bit too nimble for a heavy fighter.

I think it should carry also S9 Torpedos and should have EMP + QED. Otherwise the ship is unplayable and underpowered.
 
....

So instancing then.
Not really.
For exemple, you have a space station with 20 players in and around it. The station is managed by a dyn server which always exist (because there is always players in it).
Arrival of an Idris with 30 pirates players. The Idris use it's own dynamic server that will exist inside the zone of the station server as long as it's stay around it.

Exemple 2: you have a dyn server for a space station that usually manage 50 players in and around the station. A player event is taking place with 100 players, you can split the usual dyn server by 2 servers : one for the outside of station, one for the inside. You can also split the inside of the station with one server for each floor of the station.
 
Edge cases aren't the best point of comparison friend. You can create any scenario you want from those...
You call them edge cases because they can't be handled properly by static servers. There is no need of dynamic meshing if you want to manage your server load in a standard way with hidden loading between physically isolated zones.
 
Back
Top Bottom