Epic Games granted us a huge wish and released Epic Citadel for Android devices publicly this week, and included a benchmark inside. Getting Epic Citadel for Android and thus a benchmark of a real game engine (Unreal Engine 3) running atop Android has been a longtime wish, and we immediately started testing some devices. Epic claims to have updated visuals for the Android Epic Citadel release, and correspondingly released an update for the iOS version, although the iOS version still lacks a benchmarking mode. 

The visuals inside Epic Citadel are impressive, which almost goes without saying. Performance walking around the map is also smooth, almost too smooth. I suspect Epic spent a lot of time optimizing the Android version for optimal performance on a wide set of hardware. Keep in mind that Epic Citadel is designed more as a proof of concept for developers, and to prove that Unreal Engine 3 can be performant across a wide range of hardware.

The Android version of Epic Citadel includes support for both ARM devices and x86, which lets us test it out on Intel's Medfield platform with a RAZR i in a native way alongside a suite of other Android devices. I grabbed a handful of current devices and N-1 generation devices to see how effective of a benchmark Epic Citadel's new mode proves to be. There's a menu option exposed by the drop down, which allows users to select between High Quality and High Performance modes, and below it, rendering resolution percentages if you want to set a render target smaller than the display (for example how the iPad with Retina Display initially rendered). To make the test as taxing as possible I set High Quality even on devices which defaulted to High Performance, and made sure resolution was set to 100% of native.

Epic Citadel for Android - High Quality, 100 Percent Resolution

Unfortunately Epic Citadel for Android is already running at vsync on most modern devices most of the time. Watching a run through on devices like the HTC Droid DNA or Butterfly, which are 1080p, it's amazing how much of the benchmark is right against vsync. There really is only one outdoor scene that is taxing enough to bring the device's FPS down into the low 50s and high 40s, which brings that average down below 60. If we're already at vsync on Fusion 3 hardware which is shipping today, that means future devices are going to be even more constrained running the same benchmark. Even Nexus 10 spends much of its time against vsync despite rendering to a positively huge WQXGA display natively. 

My conclusion is really that either Epic waited too long to release Epic Citadel with a benchmark, and now the assets are nowhere near taxing enough, or this is primarily designed as a benchmarking mode to showcase how well UE3 runs on current hardware. Given the purpose of Epic Citadel, I'd say the latter is more of a credible story. While I'm glad we finally have a proper UE3 benchmark to use on Android, I doubt we'll be able to glean much from running it on next-generation devices and SoCs. 

Source: Play Store, Epic Blog



View All Comments

  • SquattingDog - Friday, February 8, 2013 - link

    On my Samsung Google Nexus S (2nd generation Nexus):

    24.8 @ 800x480 (Native), High Performance
    21.6 @ 800x480 (Native), High Quality

    Specs: 1GHz Cortex A8 Single Core, 512MB RAM, PowerVR SGX540, Jellybean 4.1.2
  • Taemoor - Wednesday, January 30, 2013 - link

    I just got 58.8. I want to confirm this score. Is there anyone else out there with a Kobo Arc? Please reply to this and post your score.
  • Taemoor - Thursday, January 31, 2013 - link

    it was on full res (1280X736) and ran it again with even astonishing 58.9. Reply
  • nagi603 - Thursday, January 31, 2013 - link

    B&N NookColour with CM10: 13.whatever fps, regardless of resolution. Reply
  • neothe0ne - Thursday, January 31, 2013 - link

    On my APQ8064 / Adreno 320 phone at 720p and "power saving" mode (only 1 core turned on?), I got a 42.9 FPS average (was generally always at ~58 except for some outdoor scenes in the 30s).

    With all cores on, the average FPS is 57.3. (I saw a low of 45 for a split second I believe)

    Apparently that makes this APQ8064 / Adreno 320 phone is marginally better than the Nexus 4 :)
  • dragonsqrrl - Thursday, January 31, 2013 - link

    Strange, I don't seem to have a benchmarking mode on my Droid 3. When it starts up I'm taken straight into the environment, and I don't see any options or settings available. Am I just noob'n out, or is anyone else having this problem? Reply
  • WeaselITB - Thursday, January 31, 2013 - link

    Swipe down from the top little banner thing, tap the gear on the right to go into Settings to adjust quality / resolution. Then when you're back in the engine, swipe down again to hit the Benchmark button. Reply
  • dragonsqrrl - Thursday, January 31, 2013 - link

    There is no top little banner thing when I'm running around in the environment. This is the difference I was talking about between what I'm seeing on my Droid 3 and the screen shots posted above. I'm wondering if it's a problem specific to the Droid 3 (wouldn't surprise me), or if it has to do with Android 2.3. Is anyone else still running 2.3? Reply
  • jmke - Thursday, January 31, 2013 - link

    it's good that it is running close to vsync.
    means that once you start adding AI , gameplay elements, bots, objects etc the performance will remain good.

    imagine if it were running <30fps without any elements or objects inside the gameworld, that would be a bad sign.
  • xaueious - Thursday, January 31, 2013 - link

    Average was mid 30s for my T30 TF300. Anandtech should have one of these devices lying around. Would be curious to see your results. Reply

Log in

Don't have an account? Sign up now