Glorious Wiki readers. We are adding the Midnight Magic video and livestream to the wiki. We appreciate your patience as we process the new and updated information!

Performance: Unterschied zwischen den Versionen

Aus Ashes of Creation Wiki
Zur Navigation springen Zur Suche springen
K
K (Text replacement - "{{Notes}}" to "{{References}}")
Zeile 10: Zeile 10:
 
* [[User interface]]
 
* [[User interface]]
  
{{Notes}}
+
{{References}}
  
 
[[Category:Development]]
 
[[Category:Development]]

Version vom 24. Juli 2018, 22:58 Uhr

Leistungsoptimierung beim Rendern von 1300 simulierten Akteuren unter Verwendung zusammengeführter Materialien und Netze in Unreal Engine 5 Nanite.[1] Nach dem Streamen wurde bestätigt, dass dieser Test auf einer RTX 3070 läuft. [2]

Was ihr hier seht, zeigt die neue modulare Erscheinungsbildkomponente, die zur Laufzeit beliebige Netze und Materialien zu einem einzigen Netz und einem einzigen Material kombinieren kann. Was zu sehen ist, sind über 1300 verschiedene Einheiten, verschiedene Akteure. Dabei handelt es sich im Wesentlichen um simulierte Spieler. Zuvor habt ihr das Beispiel gesehen, in dem sie einfach stillstanden. Es gab keine Animation, es gab keine Effekte, es gab keine Umgebung und es war tausendmal. Das sind 1300 abgespielte Animationen, abgespielte Effekte und die Umgebung, die in diesem Beispiel Nanite ist. Was ihr also seht, sind all diese Spieler, die sich bewegen und etwas tun, und ihr seht, dass die Bildrate auf Claytons System bei etwa 30 liegt.[3]Steven Sharif

Hier seht ihr, dass die FPS in der oberen rechten Ecke im Durchschnitt bei sieben oder acht liegen, also aus Rendering-Sicht nicht besonders gut ... Wenn sie jetzt zusammenführen, könnt ihr sehen, dass dieselben tausend Spieler dieselben Rüstungen wie zuvor tragen tatsächlich eine 300-prozentige Leistungssteigerung – 300 bis 400 – in der Leistung des FPS. Der Wert stieg also im Durchschnitt von 7 auf etwa 21, und das ist ein bedeutender Optimierungspunkt, der offensichtlich erst der Anfang der Optimierungsbemühungen ist.[4]Steven Sharif

Ashes of Creation lief während der frühen Alpha 1 Tests mit 50-60 FPS auf einer 1080 Ti. [5]

  • Bei Belagerungen oder anderen groß angelegten Schlachten kann automatisch ein „Standard-Spielerauftritt“ angewendet werden, um die Leistung des Clients zu verbessern. [9][10][8]
Ich denke, ihr werdet mir hier zustimmen, dass die Auswirkungen jetzt anders sind als in der Alpha-1. Wir haben das Feedback der Leute berücksichtigt, obwohl es immer so war, dass wir sie ansprechen wollten; und wir haben sie so implementiert, dass sie für Schlachten mit großen Spielern besser geeignet sind.[6]Steven Sharif

Unreal Engine 4

Unreal Engine 5 walkthrough.[11]

Lumen has done a great job in really bringing to to life this area. As you can see, there's light bouncing off of the surfaces and casting into the rest of the cave... I love how you can also see the detail in the costume and the cloth that we have now.[11]Steven Sharif

unreal-engine-logo.png

Unreal Engine 5 is the graphical engine for Ashes of Creation.[11][12] The game was originally developed in Unreal Engine 4.[13] Migrating to UE5 early is expected to save time the long run compared to upgrading closer to release, or post-release.[14][15]

What it provides in my opinion as person who enjoys PvP is it adds additional dynamics to what is possible from your opponent or from yourself. You know, if there is a ledge and jumping off that ledge is going to deal a lot of damage to me when I hit the ground and that puts me at a significant disadvantage, maybe I have an option to jump off the ledge at a point where I can mantle onto the side of a cliff or something. Now the give and take there is I won't be able to use my skills while I'm mantled. I won't be able to react easily, but I didn't have to take the fall damage per-se. Or if there's an obstruction and I'm going to take a significant reduction in speed so that I can crouch and make it past that, and now I have a effective line of sight has been obstructed as a result of that decision. I think it adds interesting elements to the battlefield and the key here is going to be making sure that it's not cumbersome- that it doesn't feel opposite of the flow of combat.[18]Steven Sharif
Lumen is going to greatly improve the visual fidelity and performance of the game with the reduced work and effort that's required by the art team, making Ashes of Creation much more beautiful than in UE4.[20]Steven Sharif
Nanite brings us really an entirely new approach to rendering and art workflows. Now we can render more actors with extremely high detail while eliminating the need to bake out normal map textures. For artists essentially what this means is that they can import high quality sculpted meshes directly into Unreal 5 without really having to reduce the poly count, making the workflow more efficient while simultaneously improving the quality of the art.[23]Steven Sharif
  • Features (such as World partitions and One file per actor) make it much easier for multiple developers to work together.[14]
    • World partitions also enable Unreal Engine 5 maps to exceed the map size constraints of UE4 (~20 kilometers squared).[14]
Q: How does this upgrade to UE5 affect the Ashes of Creation release timeline?[14]
A: While UE4 is a great engine, there are certain focuses and technological endeavors that Epic is doing on UE5 that won't necessarily be supported by UE4; and we want to make sure given the lifespan of Ashes and how long we intend this MMO to last, that when we made this decision early on during the development process that we weren't going to exacerbate the amount of effort it would take to move over later in the lifespan or after launch.[14]Steven Sharif
  • As of January 24, 2022 all teams have moved over to Unreal Engine 5.[27]
    • The developers were able to transition to Unreal Engine 5.1.1 in February 2023 as part of milestone 4.[28][29][30]
    • The upgrade to Unreal Engine 5.2 was completed. The developers expect to start upgrading to 5.3 around the end of 2023.[31][32]
    • At some point the developers intend to stop updating Unreal Engine until post-launch. This decision will be based on careful consideration of potential delays and other risks.[33]
Q: What is your stance in regards to focusing on delivering an MVP versus continuously upgrading your tools and engine to deliver a better product with new tech, even if that results in delays or additional years of development like UE 5.2, maybe 5.3 etc?
A: Our technical teams, especially our network team, our ICS teams, our gameplay engineering teams, they convene and weigh when our next update should be on the engine side: What new technologies might bring benefit overall. My perspective on how we balance the need for integration of new technology versus the responsibility we have in a timely manner to provide testing sessions that get us closer to the launch date; that's a delicate balance. I would say generally our disposition is not to incorporate new technologies that yield some significant amount of delay on the development side. We very much take the perspective that we're capable of adjusting and/or integrating those new technologies post-milestone, post-launch if necessary. At some point we'll stop updating the Unreal Engine in development until launch. That point hasn't come yet, but of course the larger the project grows and on the more custom we make the engine for our back-end needs; and for whatever else merge conflicts can occur- those mergers can become big and painful; and the update process gets more painful. So to answer your question shortly, we have a team that evaluates what direction we need to take there; and at the top of my mind is always, let's not incorporate delays as a result of leveraging new technologies.[33]Steven Sharif

Siehe auch

Template:References