I'm waiting for the announcement that they're switching game engines again, or some kind of similar foundational shift that will add a dozen more years but promise much higher fidelity.
There is a theory they never actually switched to Lumberyard and claimed to do so only for the purpose of Crytek's lawsuit. I wonder if there was some kind of code discovery happening during the proceedings.I'm waiting for the announcement that they're switching game engines again, or some kind of similar foundational shift that will add a dozen more years but promise much higher fidelity.
Some of these analogs, like almond milk, work for me. But the yummy aftertaste of fatty milk is hard to beat.Oat milk...I shudder at the thought. I'd have to cover my milking cow's ears if I ever uttered it aloud too![]()
I can't make home made butter and cheese from oat or almond milkThere is a theory they never actually switched to Lumberyard and claimed to do so only for the purpose of Crytek's lawsuit. I wonder if there was some kind of code discovery happening during the proceedings.
Some of these analogs, like almond milk, work for me. But the yummy aftertaste of fatty milk is hard to beat.
There fixed it - let's keep proper English standards - it's all we got.Oat milk...I shudder at the thought. I'd have to cover my milking cow's ears if I ever uddered it aloud too![]()
One of the times I visited friends on the mainland, they politely asked if I had any special dietary requirements or food allergies...I said, "Nope...I'll just lie here on the floor and you just go right ahead and sweep it all in."There fixed it - let's keep proper English standards - it's all we got.
And what can you do? I just can't process it properly anymore. At least I got rid of the flatulenza now.
It's not a theory. They have switched the licence, not the engine. Amazon had aquired the right from Crytek to sell CryEngine 3.8 with a Lumberyard label. CIG used this CryEngine 3.8. So CIG bought the exact same engine they were using to Amazon with the Lumberyard label on it to get rid of Crytek.There is a theory they never actually switched to Lumberyard and claimed to do so only for the purpose of Crytek's lawsuit. I wonder if there was some kind of code discovery happening during the proceedings.
Far less troubles with grids, far less random deaths and far less 30 K since the last patch.
Some problems are resolved.
Recollections may vary...as they say. A lot of folks are having weird problems with the latest patch, some aren't. I'm not having too many issues at all bar the minor bugs, nor have I ever with the likes of deadly elevators, ship ramps or ladders...or glitching through floors etc. No idea why some have this issue and yet others don't. It's not like I'm running a NASA level PC or anything, nor is my net connection anything spectacular. If I'm honest...it's more like they're doing something wrong rather than I'm doing something rightYou can post videos of bugs and glitch, it doesn't change the fact that the game is waaaay more stable and have less gamebreaking bug since 3.13.0...
The underlying tech is more robust![]()
It's not a theory. They have switched the licence, not the engine. Amazon had aquired the right from Crytek to sell CryEngine 3.8 with a Lumberyard label. CIG used this CryEngine 3.8.
In fact, we are excited to announce that our upcoming 2.6 Alpha release for Star Citizen is running on Lumberyard and AWS.
We stopped taking new builds from Crytek towards the end of 2015. So did Amazon. Because of this the core of the engine that we use is the same one that Amazon use and the switch was painless (I think it took us a day or so of two engineers on the engine team). What runs Star Citizen and Squadron 42 is our heavily modified version of the engine which we have dubbed StarEngine, just now our foundation is Lumberyard not CryEngine. None of our work was thrown away or modified. We switched the like for like parts of the engine from CryEngine to Lumberyard.
In addition to the mode of development for Squadron 42, CIG’s flip-flopping also has plagued this case from the start with respect to whether CIG “switched” to Amazon’s Lumberyard. Initially, CIG stated to the public that it had switched from CryEngine to Lumberyard. CIG’s Memorandum ISO Motion for Bond, ECF 57-1, at 3 (“On December 23, 2016, CIG publicly announced its switch from CryEngine to Lumberyard.”). Crytek brought its lawsuit premised, in part, on this understanding. Because it suited CIG’s litigation positions, however, CIG later admitted that it did not actually switch to Amazon’s Lumberyard. CIG’s Reply ISO Motion for Bond, ECF 74, at 8. Rather, CIG was still using the CryEngine code itself, just under a separate license from Amazon. Id. The issues have now evolved in such a way that CIG once again claims that it has switched to Lumberyard. CIG’s Opposition, 3 (“[Crytek] misleads the Court . . . by falsely claiming that CIG did not switch to Amazon Lumberyard”). CIG’s repeated reversals make it extremely hard to litigate the parties’ disputes in an organized fashion or to even decide what discovery is necessary because CIG’s litigation statements are discarded at its convenience.
Similarly, the Court’s analysis on Crytek’s credit claim rested on CIG’s now refuted assertion that it had actually switched to the Lumberyard engine. Id. at 4 (“It is enough . . . that CIG switched the copyright and trademark notices only after it began using Lumberyard instead of CryEngine.”).
So CIG bought the exact same engine they were using to Amazon with the Lumberyard label on it to get rid of Crytek.
Any confusion no doubt stems from Chris obscuring that fact at the time:
A confusion which was eventually probed by the court case:
Eventually getting CIG to reveal, that yes, they were just using an old Cryengine build still...
Yes. It's just a shame for them that acquiring a fresh Cryengine licence didn't seem to invalidate the prior deal, so they just ended up with two. And then Crytek inconveniently survived their massive downturn.
Not sure it quite planned out the way CIG wanted![]()
You can post videos of bugs and glitch, it doesn't change the fact that the game is waaaay more stable and have less gamebreaking bug since 3.13.0...
The underlying tech is more robust![]()
That's why it doesn't work...You're all spreading FUD anyway, its called StarEngine and its been modified so much its no longer anything like either Lumberyard or CryEngine. Its got Chris' magic touch all over it!
I just see it in game with my friends. We have far less troubles to get long sessions with teams and organizing events.Just repeating the assertion doesn't actually constitute evidence![]()
Could be the result of moving away from database processes running inside server instances (shivers).I just see it in game with my friends. We have far less troubles to get long sessions with teams and organizing events.
And I've not seen a 30K since my last 20 hours of playtime, I've never played so long without a server crash.
Since the game has been in Alpha for over 9 years, that should be the absolute bare minimum, but your experience is not everyone's experience. I don't trade anymore, and I don't mine, because I've lost millions of aUEC on 30Ks over the past 4 patches.I just see it in game with my friends. We have far less troubles to get long sessions with teams and organizing events.
And I've not seen a 30K since my last 20 hours of playtime, I've never played so long without a server crash.
Aye, it's fine for faffing about pointlessly with mates or standing still laughing at glitching NPC's in space stations...but playing the game is a disaster. It's the only game I've ever played that I've ended up several million credits worse off due entirely to game bugs and server crashes after weeks of grinding...this isn't some short term issue either...this has been going on for yearsSince the game has been in Alpha for over 9 years, that should be the absolute bare minimum, but your experience is not everyone's experience. I don't trade anymore, and I don't mine, because I've lost millions of aUEC on 30Ks over the past 4 patches.
Nope...only had one in the last 3 days but otherwise it's just the usual bugs. Trading not working since they broke the restocking chain in 3.11, mining not working due to server desync and lag with this patch...the servers might not be 30k'ing...but the desync and lag is the worst I've seen it for several patches. It might be due to the clusterfarce ship sale event...we'll see once the shouting and selling is over and all the temporary newbies go back to playing Fortnite I guessYou still have regular 30k in 3.13.1 ?