#STAR CITIZEN 2.6 RELEASE DATE 64 BIT#
#STAR CITIZEN 2.6 RELEASE DATE CODE#

Gameplay feels really вЂfloatyвЂ™ in that nothing is tight about aiming or getting your lump of a body to move around.Really nice вЂzero GвЂ™ areas that remind me of вЂShattered HorizonвЂ™ (such a unrecognized classic that gameвЂ¦).

Levels are a bit вЂchoke pointвЂ™ orientated on the вЂhack/defendвЂ™ maps, but I suppose that makes sense.It still obviously seems early days, but initial impressions are: Internally it is StarEngine.I played вЂStar MarineвЂ™ for 30 minutes or so and itвЂ™s, um, вЂinterestingвЂ™. So no worries about the future of Star Citizen, we will deliver the best game with the best technology, doesnвЂ™t matter how it is called. The general direction of Amazon in regards to a stronger focus on network technology helps a lot though. More important is that the majority of the CryEngine knowledge back to FarCry is at CIG now, which is invaluable and makes a switch like this easier and safer. We are pretty good at handling the rest of the old CryEngine codebase, which CryEngine, Lumberyard and StarEngine have in common

#STAR CITIZEN 2.6 RELEASE DATE CODE#

Everything else is relatively easy to merge, thanks to the same code base + adding independent Lumberyard only features is straightforward too, especially with the help of Amazon developers.

We heavily changed or have completely rewritten CPU/GPU side rendering, memory management, multithreading, entity/game object handling + added tons of engine features wich neither CryEngine nor Lumberyard have. The Lumberyard builds we used had the same CryEngine 3.7 base with the main changes on the Editor/Tools side. StarEngine was based on CryEngine 3.7 (last big integration) with cherry picked changes from CryEngine 3.8 (mainly some Animation/Serialization fixes/improvements). It seems just as likely though that CIG is using the tumultuous decision to put backers minds at ease by relying on a more stable and equally reputable company like Amazon, at least compared to recent financial troubles for CryTek. There are a lot of ways in which this new development environment could improve the final quality of CIGвЂ™s final product. The justifications for the change are complex and multi-faceted, from AmazonвЂ™s focus on network stability and future-proofing, to the recent troubles at CryTek surrounding staff.

#STAR CITIZEN 2.6 RELEASE DATE 64 BIT#

All of our bespoke work from 64 bit precision, new rendering and planet tech, Item / Entity 2.0, Local Physics Grids, Zone System, Object Containers and so on were unaffected and remain unique to Star Citizen.вЂќ We switched the like for like parts of the engine from CryEngine to Lumberyard. None of our work was thrown away or modified. 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. 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). вЂњWe stopped taking new builds from Crytek towards the end of 2015. First, he says, вЂњLumberyard and StarEngine are both forks from exactly the SAME build of CryEngine.вЂќ Yesterday, Chris Roberts addressed both issues. Just before the holiday weekend, Cloud Imperium announced that both Star Citizen and Squadron 42 are using Lumberyard, AmazonвЂ™s robust game engine, and in fact have done so for вЂњmore than a year.вЂќ LumberyardвЂ™s only been public knowledge for about 10 months and change, and Star CitizenвЂ™s devs havenвЂ™t mentioned it at all, which got players buzzing about transparency along the way, to say nothing of the folks puzzling over the CryEngine base Star Citizen was originally said to be using.

Star citizen 2.6 release date