|
|
|
|
|
|
Dann mach das beste draus, eine caterpillar zum beispiel.
Bei dem pott hab ich das erste mal echte probleme mit den proportionen um nirgends anzuecken, die übersichtlichkeit vom cockpit ist eher meh und sobald man auch nur einen felsen leicht küsst, fliegt das teil in die luft. Die asymmetrie und ungwohnte cockpitposition weit hinten tun ihren teil dazu bei, aber den stummelflügel am andern rumpfende vergesse ich viel zu oft.
|
|
|
|
|
|
|
|
|
|
|
|
da wundert es mich ja. unsere autos haben heutzutage annäherungssensoren. warum nicht dann auch fucking Spaceships?
|
|
|
|
|
|
|
|
|
|
|
|
komm jetzt nich mit realismus
|
|
|
|
|
|
|
|
|
|
|
|
Naja, stells dir einfach wie bei der ausparkszene bei starship troopers vor *smooth**smooth**shiiiiiiiiii**smooth*
|
|
|
|
|
|
|
|
|
|
|
| | Zitat von Lunovis
Dann mach das beste draus, eine caterpillar zum beispiel.
| |
Hab ich doch schon längst :>
¤: gerade nachgeschaut. Für die Caterpillar hab ich im November 2014 gepledged. Mehr als 2 Jahre von Concept bis fliegbar  bei den Capitals ist es natürlich noch extremer ...
|
|
[Dieser Beitrag wurde 1 mal editiert; zum letzten Mal von Meister Zopf am 25.12.2016 12:03]
|
|
|
|
|
|
|
|
|
Mit meiner neuen Graka (GTX 1070) krieg ich auf "Very High" locker 100fps bei 3440x1440 im Free Flight. Sehr geil Herr Greil! Jetzt muss das nur noch im PU so sein  Eventuell bringt der Amazon Deal diesbezüglich sogar was.
|
|
|
|
|
|
|
|
|
|
|
fazit 2. weihnachtstag:
viel zu viel los, crusader ist laggy as shit, gefühlt läuft der client auch nicht wriklich flüssiger. werde dann die nächsten tage mal nochmals kurz hineinschauen aber bis dann ist das spiel wohl aufgrund des hohen andrangs unspielbar.
|
|
|
|
|
|
|
|
|
|
|
|
Im PTU lief es mit n, m und o super, aber jetzt sind die Server unter den Massen von Free Flight-Leuten vermutlich wieder hoffnungslos überfordert.
|
|
|
|
|
|
|
|
|
|
|
Jemand ne Ahnung, was für alternativen für pp_rebindkeys zur Verfügung stehen? Irgendwie bin ich zu blöd, das rauszufinden.
Ist da was passendes für T16000m bei?
|
|
|
|
|
|
|
|
|
|
|
| | Star Citizen as of 2.6 is now on the Lumberyard Engine... Wait, What?
As of Star Citizen Alpha 2.6, Star Citizen & The Star Engine (which is a heavily changed CryEngine) is now integrated with Amazon's Lumberyard Engine, here is a quick run down of the improvements and changes that accounts for as well as a selection of useful links & the Original Posts from Chris & Erin Roberts from CIG & F42.
Lumberyard is a 3d Game Engine built upon the CryEngine designed to make use & take advantage of the Amazon’s Webservices (AWS), Servers, Storage and Compute Power.
It’s an extremely developer and fan-centric cross platform engine with native integration of Twitch as well as being geared towards MMOs & Large numbers of players.
It is crossplatform so it's possible to see games on PCs, Consoles, Mobile Devices and VR Headsets, Vive, PSVR, Oculus & OSVR.
CIG have already moved over and integrated the Star Engine with Lumberyard. The Transition was almost invisible as the Engines are based on the same baseline.
We should see benefits to Servers, Pings, Deployment, Ergonomics for modding amongst other things as well as a huge amount of improvements to the current engine & possibly more accessible VR.
Lumberyard allows CIG to have an extremely scale-able network, server and deployment platform.
Expect faster more stable servers, better pings, more players in a given area from Star Citizen in the near future because of this change.
Lumberyard is a collection of tools, some of which Star Citizen will use, others it will not OR they will use their own bespoke ones, Lumberyard gives them more power and options.
It's also possible the Star Citizen will receive some additional core updates to the engine that will improve things even tho the Star Engine was extremely modified.
For Modders and people that want to get into Game Development Lumberyard is FREE so it could act as a very accessible gateway into the industry.
Lumberyard - Star Citizen Announcement
In The Star Citizen Newsletter Chris Roberts Announced the Release of Alpha 2.6 & The Change Over to Lumberyard had been Completed:
"We are now basing Star Citizen and our custom technology development on Amazon’s Lumberyard Engine. Since the beginning of the project, we’ve had to make a huge number of changes to the CryENGINE code and tech to enable us to deliver Star Citizen. While the original CryENGINE had great strengths in many areas like rendering and cinematics the needs of our game were well beyond what came ‘out of the box’. So we have, over time, changed significant parts of the engine for our technology, such that only a baseline of the original engine truly remains. In the future we will continue to make significant changes to AI, Animation and Network code and systems.
When Amazon announced Lumberyard back in February 2016, we were immediately interested. While based on the same baseline technology as Star Citizen, Lumberyard is specifically designed for online games, utilizing the power of Amazon’s AWS Cloud Services and their Twitch streaming platform.
Amazon’s focus aligns perfectly to ours as we’ve been making significant engineering investments into next generation online networking and cloud based servers. Making the transition to Lumberyard and AWS has been very easy and has not delayed any of our work, as broadly, the technology switch was a ‘like-for-like’ change, which is now complete.
As an added benefit Amazon AWS data centers are spread around the world from North America to South America, Europe to China to Asia Pacific, which will allow us to better support the many backers across the globe as we scale up Star Citizen.
Finally, Amazon has made Lumberyard freely available for anyone building their own game. That means that technically-inclined members of the community can have a better view 'under the hood' of our game than ever before. It's also a great path for anyone interested in game development professionally; I fully anticipate that in the coming year we will be hiring programmers who have taught themselves using Amazon's Lumberyard resources!
As we move forwards, we are confident you will see great benefits from our partnership. Amazon will bring new features to Lumberyard to assist in creating online persistent games, adding great support for their products like Twitch (which we use extensively) and of course investing heavily in engine research and development for years to come. We could not find a more stable and reliable engine partner than Amazon, so with this partnership we are sure we have secured the future development and continuing technical innovation for Star Citizen."
Star Citizen Switches Engines
Over at wccftech, Adrian Ip contacted Erin Roberts Head of Foundry 42 UK about the Lumberyard "Switch":
"As you’ve (correctly) surmised, any suggestions that the engine switch would have a major impact on our development couldn’t be further from reality. Lumberyard is completely based on Cryengine, yet with a lot of improvements. As a consequence, we do not have to change the fundamental core engine at all which is why this change has had absolutely no effect on our development of Star Citizen.
The advantage of Lumberyard is that we get great ongoing support on the cloud / networking side from Amazon as well as great tools support while continuing uninterrupted development on what we have built up over the last 4 years. As we’ve tried to explain many times before, we have pretty much rewritten 50% of what we licensed 4 years ago now, even in core systems from CryEngine. What is great is that everything we have reworked, also now seamlessly integrates into Lumberyard, and the engine switch has not required any extra engineering time. We are actually very lucky that this opportunity presented itself to work with a powerful and committed company like Amazon that is investing heavily in its tech. This collaboration will effectively allow us to do more for our community going forward without costing us really anything in terms of engineering time or otherwise, so it is a win-win situation and good news all around."
Lumberyard for those interested...
On The 25th December Chris Roberts Posted a Forum Thread on the RSI site:
"Lumberyard and StarEngine are both forks from exactly the SAME build of CryEngine.
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. 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.
Going forward we will utilize the features of Lumberyard that make sense for Star Citizen. We made this choice as Amazon's and our focus is aligned in building massively online games that utilize the power of cloud computing to deliver a richer online experience than would be possible with an old fashioned single server architecture (which is what CryNetwork is).
Looking at Crytek's roadmap and Amazon's we determined that Amazon was investing in the areas we were most interested in. They are a massive company that is making serious investments into Lumberyard and AWS to support next generation online gaming. Crytek doesn't have the resources to compete with this level of investment and have never been focused on the network or online aspects of the engine in the way we or Amazon are. Because of this combined with the fact we weren't taking new builds of CryEngine we decided that Amazon would be the best partner going forward for the future of Star Citizen.
Finally there was no ulterior motive in the timing of the announcement. The deal wasn't fully finalized until after the release of 2.5 and we agreed with Amazon to announce the switch and partnership upon the release of 2.6, which would be the first release on Lumberyard and AWS. If you have been checking out our schedule updates you would know that we originally had hoped to release 2.6 at the beginning of December, not Friday the 23rd!
I hope this clears up some of the speculation I have seen. We are very excited to be partnered with Amazon and feel this move is a big win for Star Citizen and by extension everyone that has backed the project."
Useful Links & Articles on Lumberyard & Star Citizen
The Article From Redacted - https://www.redacted.tv/star-citizen-lumberyard-info/
Star Citizen Newsletter About Lumberyard - https://goo.gl/qk4Tvf
Star Citizen Switches Engines - http://wccftech.com/star-citizen-switches-engines/ by Adrian Ip, wccftech
Lumberyard for those interested... - https://forums.robertsspaceindustries.com/discussion/364217 by Chris Roberts, CIG
STAR CITIZEN, LUMBERYARD, AND YOU - http://imperialnews.network/2016/12/lumberyard-and-you/ by WolfLarsenSC, INN
Amazon Lumberyard FAQ - https://aws.amazon.com/lumberyard/faq/
Lumberyard Blog - http://aws.amazon.com/blogs/gamedev
What device platforms does Lumberyard support?
Lumberyard currently supports PC, Xbox One, PlayStation 4, iOS (iPhone 5S+), and Android (Samsung Note 4 and equivalents). Support for broader mobile hardware is coming soon, along with additional support for Mac and Linux. Please note that Sony and Microsoft only permit developers who have passed their screening process to develop games for their console platforms.
| |
via /u/BOREDGAMER_UK
|
|
|
|
|
|
|
|
|
|
|
|
Ich finds gut. Wenn der Kram jetzt noch stabiler laufen sollte wär damit allen geholfen. Und dazu noch gute Werbung für Amazon und die Engine, evtl. pusht Amazon das Ding dadurch ja auch finanziell als Vorzeigeprojekt. Win-Win würd ich sagen.
|
|
|
|
|
|
|
|
|
|
|
|
Wollten die nicht ursprünglich mal private Server ermöglichen?
|
|
|
|
|
|
|
|
|
|
|
|
Sie wollten ermöglichen dass das PU privat abläuft - ja. Das wäre ja theoretisch immernoch möglich, ob sie private Multiplayer-Server ermöglichen wollten weiss ich grad nicht mehr. Wäre aber mal ne Frage für die Premium-Kunden hier, ich hab da ja leider keinen Zugriff.
|
|
|
|
|
|
|
|
|
|
5 crashes um in irgendein game mode zu kommen, der mich dann nach netmal 10s wieder rauswirft.
und sowas wird halt vor weihnachten mal fix rausgehauen...
|
|
|
|
|
|
|
|
|
|
|
|
Läuft hier soweit alles, nur die Latenz und FPS sind wieder unter aller Sau.
|
|
|
|
|
|
|
|
|
|
|
|
FPS pendeln sich bei mir nach anfänglichen Laderucklern fix ein. Die hatte ich mit der alten Version weniger, die hat dafür bis man im Level war länger geladen *schulterzuck*
|
|
|
|
|
|
|
|
|
|
sagt mal, wie ist das eigentlich mit der versionsnummer und sq42 geplant?
soll sq42 "fertig" sein, während sc insgesamt noch irgendwo im alpha- oder beta-stadium hängt? oder bekommen die dann zwei verschiedene versionsnummern?
|
|
|
|
|
|
|
|
|
|
|
|
sind doch am ende 2 verschiedene Programme, bei denen einzig die achievements von sq42 übernommen werden.
|
|
|
|
|
|
|
|
|
|
|
Polaris Broschüre inner Post gehabt. Wusste gar nicht, dass da was kommt.
|
|
|
|
|
|
|
|
|
|
|
Meh. Das is ärgerlich. Kriegt man Oculus DK2 eigentlich noch verkauft?
| |
| |
With the new Lumberyard Engine and its easier to use integration functions, will we be seeing more talk of possibly moving back toward VR support for this game? My Dream is Star Citizen, a VR Treadmill and a VR Headset.
| |
Sorry to say, do not hold your breath for this. Ignoring the render tech for VR itself (which given the work we've done, would definitely be a read-and-rewrite job, not a merge-this-file job), making a game properly VR compliant takes a lot of work at the design and testing level regardless of the engine used. We'd probably need to get the framerate up a bit higher too, come to think of it.
| |
|
|
|
|
|
|
|
|
|
|
|
|
einerseits schade, andererseits steckt vr halt auch einfach noch zu sehr in den kinderschuhen.
|
|
|
|
|
|
|
|
|
|
|
|
Sollen lieber trackir Support fertig machen.
|
|
|
|
|
|
|
|
|
|
| | Zitat von ]Maestro[
Sollen lieber das Spiel fertig machen.
| |
|
|
|
|
|
|
|
|
|
|
|
Ähh, ja, das auch.
Und das Flight Model wieder auf 2.5.
|
|
|
|
|
|
|
|
|
|
|
|
Sie sollen mal eher das FM an reale Bedingungen anpassen was G Kräfte und Aufschaltdistanzen angeht. Ich mein, interstellare Raumfahrt aber nicht über 4km auf schalten können. Wenn man Bordgeschütze nur bis 4km benutzen kann, okay ist sinnig. Aber Torpedos? Die sollten eher eine Mindestdistanz von 4km haben
|
|
|
|
|
|
|
|
|
|
|
|
Komm jetzt net mit Realismus. Gameplay geht da vor. Sonst keine dogfights. Oder willst du Gefechte nur über Entfernungen von lichtsekunden spielen, die dann mehrere tage dauern.
|
|
|
|
|
|
|
|
|
|
|
|
Nicht Licht Sekunden aber mehrere hundert km für Torpedos die dann aber zwar schnell aber träge sind würde schon reichen
|
|
|
|
|
|
|
|
|
|
|
|
ja, das wär geil. große reichweiten aber machen das dogfighting kaputt, und darum dreht sich ein wesentlicher teil. ich reg mich bei Elite auch über meine laser mit 3km reichweite auf- meine Gatling geschütze reichen weiter. oder mein 160t schwerer sensor, der nicht weiter als die menschliche stimme reicht.
|
|
|
|
|
|
|
|
|
|
|
|
Du musst das komplette design berücksichtigen. Auf schalten und Faf sind ja nur die eine Seite. Stör und Tarn Maßnahmen machen auf große Distanzen auch viel mehr Sinn. "Dogfigth" ist mit dem neuen FM Tatsächlich viel besser geworden, gerade aber für torpedos, Raketen größer S2 und die ganze Signatur Mechanik, ist diese Nahdistanz mist. Da fliege ich auf Sicht mit Bordkanone und brauch das geraffel nicht mehr. Hoffentlich bleibt es nicht nur beim arcade Nahkampf. Eloka hat gerade im Weltraum seinen reiz
|
|
|
|
|
|
|
|
|
|
|
|
hm. da geb ich dir recht. nur so machen sniper, stealth überfälle, spionage etc sinn
|
|
|
|
|
|
|
|
| Thema: Star Citizen & Squadron 42 VIII ( Best damn alpha sim ever ) |
![[UFP]Sobrek](./avatare/Sobrek.gif)
![AUP [2XS]Nighthawk 04.05.2015](./avatare/upload/U37801--schlafmutze.png)
