I've seen a number of posts saying that people are contemplating or planning to stay here, even when Voat returns.
I'm doing my due lurking dilligence and trying to get a feel for the site myself, but I thought I'd ask in case I miss something.
Is it just the responsive admins and the lower traffic? Or are there other things that make this place superior?
Thanks.
Switching to the Amazon version of CryEngine basically meant that CryTek was going to lose out on CIGs hard work,
Ehh, Cry was a dead company until we infused them with cash. Lumberyard was then a dead project before we had sign off for Star Citizen. Switching to LY didn't necessarily hurt Crytek, SC had already hired away their few remaining engineers that knew how to use the engine. I stopped getting any knowledge of internal Cry workings a few years ago so I can't really comment on the last 3 paragraphs.
There is some inaccuracy in the first part of your post, but it's not wrong generally. I work on LY and was there during the acquisition of Cry and worked on the engine before we acquired CryEngine. I can answer many questions about Cry/LY if you have some.
Thank you for your insight into the situation. I'd be curious as to the differences between Lumberyard and the original CryEngine as I'm a bit iffy on those. From what I can tell, it seems as though there are better development tools to work with in Lumberyard but I'm more of a network/server guy so I can't fully grasp the framework differences that get mentioned in the SC forums. The modifications that CIG implements do blur the lines between their own tech and Lumberyards existing tech. I am aware that Amazon gets access to many of the tech that CIG is creating for use in the Lumberyard engine as part of their agreement.
Now, I know the situation was a bit embarassing for Crytek and I couldn't weigh in on what the deciding factor was in the lawsuit. Frankly, I believe Crytek may just want the tech that CIG managed to create using their former engineers. CIG did make it sound that Lumberyard did provide them with a more streamlined approach to content creation and backend modification but I can accept that as being a bit of PR spin to sell the switch to the consumer base. I have no idea how much of that came from CIGs internal development and how much was from Lumberyards development.
I'd be curious as to the differences between Lumberyard and the original CryEngine as I'm a bit iffy on those
It's tough to summarize as there have been 100+ engineers dedicated to rewriting the god awful code CryEngine is while adding new features. Some highlights may be:
There's a lot more, but I did want to call out that CryEngine is honestly the worst codebase i have ever seen. The guy that forced the acquisition of it was fired. It's been nothing short of a nightmare to deal with.
So, here is the story on that. Originally, Cloud Imperium Games (makes of Star Citizen) were using CryEngine 3. At the time, Crytek (the parent company of the engine) was in freefall as they had been forced to lay off workers and sell IP just to make bills. At the time, they couldn't even pay all of their employees. Because of this, they had a very useful contract with Cloud Imperium Games. They ended up selling one of their Cry Engine versions to Amazon in order for additional money. Amazon took this tech and made Lumberyard which was essentially an upgraded/streamlined version of CryEngine.
After Lumberyard was released, CIG decided to go ahead and use Lumberyard instead of CryEngine 3 because they would be entitled to better support and a better product in general. This didn't make Crytek very happy as Star Citizen was really starting to gain headway and it looked like the project could be a way to resolve financial issues. The contract which CIG held with Crytek basically said "We'll use your engine for Star Citizen, Squadron 42 (the singleplayer component), and we'll provide Crytek with bug fixes and updated tech that we find." Switching to the Amazon version of CryEngine basically meant that CryTek was going to lose out on CIGs hard work, so they are trying a lawsuit over language in the original agreement.
Realistically, one of the main reasons for the lawsuit is that CryTek states that their engine wasn't supposed to be used for Squadron 42 (the SP component) despite the fact that it is clearly listed in the original agreement between CryTek and CIG. Many people believe this is a losing fight but Crytek is hoping to get something out of the lawsuit because CIG will not wanted a lengthy court case on their hands while they develop Star Citizen. It's effectively a patent troll level technique since there isn't anything that specifically binds CIG to ONLY use CryTeks engine. In fact, the lawsuit doesn't really touch on that point too much. It's really just about Squardron 42 and the right to use the engine for it.
In additional fuckery, CryTek has recently lost their CEO only for the CEOs brother to take over, IIRC. Some consider this a legal manuever as the lawsuit wouldn't be winnable in the long run and a scapegoat might be useful if/when CryTek has to back off. In any case, it is my belief that this lawsuit will not hinder development and when a judge finally makes a decision it will be in CIGs benefit. But that may take a while as legal actions are sometimes resolved much slower than common sense would dictate.
I may have glossed over some things but that's the general idea behind the situation.