Template:Performance

Ashes of Creation community empowered Wiki
Revision as of 17:04, 20 January 2022 by Lex (talk | contribs)

Jump to navigation Jump to search
Performance optimization when rendering 1300 simulated actors utilizing merged materials and meshes in Unreal Engine 5 Nanite.[1] This test was confirmed post-stream to be running on a RTX 3070.[2]

What you're seeing here showcases the new modular appearance component which can combine any set of meshes and materials into a single mesh and single material at run-time. What you're looking at is over 1300 different entities, different actors. These are simulated players essentially. Previously you saw the example they were just standing still. There was no animation, there was no effects, there was no environment and it was a thousand. This is thirteen hundred playing animations, playing effects, plus the environment which is Nanite in this example. So what you're seeing is all of these players moving around and doing something and you're seeing the frame rate at about 30 on Clayton's rig.[3]Steven Sharif

Here you see that the FPS in the top right corner is like seven or eight on average, so not too good from a rendering perspective... So by merging now you can see that the same thousand players who are wearing the same armors as previously are actually having a 300 percent increase- 300 to 400 increase- in the performance of the of the FPS. So it went from 7 to about 21 on average and that is a significant optimization point that obviously this is just the beginning of the optimization efforts.[4]Steven Sharif

Ashes of Creation was performing at 50-60 FPS on a 1080 Ti during early Alpha-1 testing.[6]

The game will be highly customizable from a settings standpoint. If you don't quite have the rig necessary to run it, you can dial the game settings down.[7]

  • Highly scalable options to adjust rendering and particle effects will be offered.[8]
  • Motion blur will be togglable on and off.[9]

A "default player appearance" may be automatically applied during sieges or other large scale battles to improve client-side performance.[10][11][7]