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

POST A COMMENT

52 Comments

View All Comments

  • CeriseCogburn - Friday, February 01, 2013 - link

    Hardware variants - something to do with the cell chip type and other wifi junk - but yeah the point is, it's irritating.

    Got 45.3 on the Note 2 here, not 45.8 as the chart shows - US version, original android no hacks, has the quad and the mali 400, jellybean 4.1.1, cleared the ram first as well that helped a bit, also it came with split screen apps working.

    960x540 (75% rez) high quality = 45.6

    100% rez(1280x720), high performance = 47.4

    lol - Kind of surprised I guess the mali400 is a bit weak / it does better in the bench suites Quadrant and Antutu vs the others in the charts.
    Reply
  • sheh - Friday, February 01, 2013 - link

    But then, why should the RF radio affect the CPU and GPU choice? :)

    And I also don't get why they don't have unified RF hardware as well, maybe with the exception of antennas which take up physical space.
    Reply
  • CeriseCogburn - Wednesday, February 06, 2013 - link

    Brain Klug mentioned it somewhere might be in this article about the chip doing LTE - so the dual core snapdragon version had to mesh with the no LTE radio chip as I understood it.
    Others elsewhere have stated there were shortages of quadcores due to demand so Samsung used alternate cores for regions and also for similar phones (changing nearly just the ARMs core and making a new phone model).
    So I guess there are several reasons.
    Reply
  • sheh - Friday, February 01, 2013 - link

    Strangely lower. I guess it's difficult to say like that if there are other factors than CPU and GPU. Reply
  • WeaselITB - Thursday, January 31, 2013 - link

    Droid 4 (TI OMAP4430 1.2GHz / PowerVR SGX540 304MHz / 1GB RAM)
    Average FPS of three runs: 49.9
    Resolution 960x540 qHD
    High Quality
    Reply
  • Kepe - Thursday, January 31, 2013 - link

    HTC Sensation (qHD) @ 1728 MHz CPU & 332 MHz GPU and set to High Quality
    1st run 42,1 fps
    2nd run 41,1 fps
    3rd run 41,5 fps
    Reply
  • hammer256 - Thursday, January 31, 2013 - link

    Resolution: 1024x720
    Average FPS: 29.3

    Ok so Adreno 220 might be showing its age at this point....
    Reply
  • randomhkkid - Thursday, January 31, 2013 - link

    Strange that the s2 scores lower than the Galaxy nexus even though the GNex is a higher res and has a slower gpu. Reply
  • powerarmour - Thursday, January 31, 2013 - link

    I think it's quite well optimized for PowerVR hardware, especially if it's an iOS port.

    Then again Tegra 3 seems to do quite well, I wonder what excuse the Nvidia haters will have for this one... ;)
    Reply
  • CeriseCogburn - Friday, February 01, 2013 - link

    None.

    I'm thrilled, it's utter silence...

    Wait, the tegra3 won, top o the chart ... why one would think they'd retract all the months of whining about tegra3.

    Not thrilled, I take it back.
    Reply

Log in

Don't have an account? Sign up now