Game Discussions Star Citizen Discussion Thread v12

Well if you think you can sink one of these.

SK6ee18.jpg



With one of these.

OFtb6y3.jpg


Go for it, i'll watch :D

Yeah, the SC version of a carrier would be this

XcjXFth.png



Not this:

store_slideshow_small_zoom.jpg


which is more like:

WBASLHZA2RDCNI7HQSCTIECFOA.jpg
 
And that's another thing i don't like, although I guess sovapid might disagree with your statement here.

A good pilot in a small ship should be able to take out a poor pilot in a big ship. A big ship should not be an "I win" button and if so, it just means SC is more pay to win than ever.

While I agree that a "big" ship should not worry about a single fighter, I'm sure we will have disagreements on what a "big" ship is.

I don't think any of the ships in game are really big right now. Any of these ships should be worried about a single fighter. A single fighter shouldn't just smack down the bigger ships in game right now, but that big ship should not be invincible. Like the video I posted of the Hercules earlier. I think that is ridiculous.

Start getting up to an Idris or Javelin, sure. Single fighter should not be a threat.

Like so many things in SC they are redefining terms. In this case capital ship. Capital ship is the largest ship in a navy. Not in SC. Got a bunch of little (relatively) peewee ships that are labeled as "capital".

i4Y9i9R.png
 
Real life != game

But if a plane with air to ground missiles couldn't severely damage a ship i'd be quite surprised. And the Japanese in WW2 found ways for small aircraft to damage ships, even if the solution was a bit extreme.

But ok, you think its right that small ships can't damage big ones. i think its pretty sucky and just confirms SC as a P2W game. ;)
The meta for beating close air defense is to overwhelm it with targets aka missiles. Preferrably launched from long range with many planes. Expect casualties or missing the sweet window to launch a strike that saturates the defenses.
 
I believe the networking / data propogation is something AWS handles well which was one of the reasons why CIG switched over to Lumberyard.
"AWS" cannot handle anything really, because it is an umbrella label for a broad set of vastly diverse services. Saying that "AWS" handles something is like saying that "Infrastructure" is taking care of it. Doesn't convey any concrete meaning, does it?

EC2 instances are pretty slow to spin up and you are always competing with other customers for their availability. You can reserve them in advance, but it will cost you dearly. In the context of server meshing this aspect will be crucial because waiting several minutes for a new instance to "mesh" is really not an option in a real-time game. While it is tempting to look at cloud infrastructure as something infinitely flexible, it is far from it. Every service has certain rigid aspects built in.

Plus, there have been no clear confirmation so far that CIG were using Lumberyard. There is an alternative hypothesis that they manured about doing so for the purpose of the Crytek lawsuit. They have a Lumberyard license but it is not obvious it is being utilised. And the terms of the settlement with Crytek were such that CIG bought another license for the CryEngine anyway.

Lumberyard so far has not been a success story:
 
Plus, there have been no clear confirmation so far that CIG were using Lumberyard. There is an alternative hypothesis that they manured about doing so for the purpose of the Crytek lawsuit.
For what we know, they are not 'using' LY only licensed it to get rid of Crytek.
The logo have also disappeared on the launcher some patch ago.
 
So you're saying SQ42 may launch with a Cryengine splash screen? ;)
Just with the CIG logo.
I think they bought full right usage and property (don't know how to explain it in english) on the CE engine in the last trial to be completly free of LY and CE.
I think the engine for CIG now is just 'star engine'.
 
Many of these scams were spending more than they took. Incidentally that is usually one of the ways for the affair to end after a while.

Most of the main executives in those cases were getting very handsome pay checks, stock options and bonuses though.
some how during my 59 yrs on earth I missed the part that the rule changed the now the coin has way more than 2 sides lol. I wonder when that happened? I must have my grand kids teach me google.
 

Viajero

Volunteer Moderator
some how during my 59 yrs on earth I missed the part that the rule changed the now the coin has way more than 2 sides lol. I wonder when that happened? I must have my grand kids teach me google.
Fully understood ;) But you can still ask your grand kids to teach the author of the video you mentioned how to google though!
 
Lol

They got: "a perpetual licence for CryEngine from game development platform provider Crytek GmbH"

Guess we'll see eh ;)
Can you help me with the doc ? Where I can find this line ? Hard to read for a french guy...
And about the "use" or not of the CE/LY, I thought that every company have a legal obligation to display the logo of the engine used ? If CE/LY logo is not displayed anymore, what does it mean ?
 
"AWS" cannot handle anything really, because it is an umbrella label for a broad set of vastly diverse services. Saying that "AWS" handles something is like saying that "Infrastructure" is taking care of it. Doesn't convey any concrete meaning, does it?

Yes it is a broad stroke term. Here I'm referring specifically to distributed computing and the propgation of objects between distributed processes. These are not trivial to self-roll reliably, and are likely why AWS is being used. Whether it's a good idea or not is an entirely different question.

EC2 instances are pretty slow to spin up and you are always competing with other customers for their availability. You can reserve them in advance, but it will cost you dearly. In the context of server meshing this aspect will be crucial because waiting several minutes for a new instance to "mesh" is really not an option in a real-time game. While it is tempting to look at cloud infrastructure as something infinitely flexible, it is far from it. Every service has certain rigid aspects built in.

Someone else mentioned that data transfer between distributed processes in AWS tends to be slow but robust - you'll get it, don't know when. That may actually be more of a problem than spinning up/down a process.

When you're talking about 'server meshing', what you're actually talking about is (for the vast majority of the time) probably more accurately called instance balancing. You're not firing up new processes, you're typically telling a couple of already extant process to expand or contract its operation based on information from a third process that provides a structure of sorts. It's not infinitely flexible as you say - ideally you want processes to be colocated as far as possible that are 'gamewise' linked, and core processes close to the player base (what in most games are regionalised shards). Dunno if AWS supports that (I'd assume so to some extent as it's a pretty obvious requirement for high-demand distributed processing) or how that'll work with a 'one game, one 'verse' approach is... well I think it'll be a sticking point.




Elite's 'slow BGS' is a pretty elegant solution to this IMO. Regionalised instance servers and a server authoritive structure and I think it'd be pretty damn good. Expensive in data centre costs though.


Plus, there have been no clear confirmation so far that CIG were using Lumberyard. There is an alternative hypothesis that they manured about doing so for the purpose of the Crytek lawsuit. They have a Lumberyard license but it is not obvious it is being utilised. And the terms of the settlement with Crytek were such that CIG bought another license for the CryEngine anyway.

Lumberyard so far has not been a success story:

I never really understood the whole court thing being what it was. Some of Cryteks claims were outlandish. CIG could have just bought that license.
As for lumberyard - I never used it (after my time). I would have thought working with Unreal Engine may have worked better, but I think it was picked because the Crytek guys that CIG bought in would be familiar with it, as well as having the network hooks to AWS.
 
Can you help me with the doc ? Where I can find this line ? Hard to read for a french guy...
And about the "use" or not of the CE/LY, I thought that every company have a legal obligation to display the logo of the engine used ? If CE/LY logo is not displayed anymore, what does it mean ?

'Outlook' section at the end. And it doesn't say any more than that.

It's a good question, but it also begs the question: Why not a Star Engine splash then? ;)

My suspicion is that, as a result of law court attrition, and SC's perpetual limbo status in terms of release, nobody cares right now...

Or at least, none of the parties are interested in testing those waters. CIG aren't going to slap a 'Star Engine' tag on it and risk more legal shenanigans. Cryengine were either routed in the legal fencing completely (and have signed away any rights there), or have settled and aren't seeking any more redress on reputational loss grounds. (IE have provided a perpetual license with low stipulations, taken a cut of earnings in some form, and mainly washed their hands of the whole affair.)

Whatever the case, will still be interesting to see the splash page for any final product ;)
 
The frak you on about re AWS. It's a computing platform, not Skynet.

It provides some off the shelf services for stuff like DB, storage and general purpose computing that may or may not be a good fit for what you're trying to do. The rest have to be custom built. There are no "processes" other than the code you write to run on their servers. Yes, that means CIG have to do the bulk of the work. Shocking, I know.
 
Back
Top Bottom