Reply to thread

Message: <blockquote data-quote="Stuart Webster" data-source="post: 137619" data-attributes="member: 2529">iPad 1 - suffers from limited RAM and VM space, making our app likely to get terminated due to memory pressure. Also limited by CPU and GPU. We use the lower level of detail model set for performance reasons.iPad 2 / iPad Mini - the problem of the iPad 1's memory pressure gets resolved, but the CPU and GPU remain a limitation on performance. We use the lower level of detail model set for performance reasons.iPad 3 - CPU and GPU had a spike in performance. This and all newer iPads use a retina display. However, our app doesn't utilize the retina display and instead we scale our view to the new resolution (this is why we sometimes have issues with device scaling and the user interface; when the iPad Air first launched, we UI wasn't set to scale up). We use the higher level of detail model set on this and all newer iPads.iPad 4 - CPU and GPU had another spike in performance. We added post processing options, but they were later removed due to unexpected issues surfacing.iPad Air / iPad Mini Retina - Not as dramatic of a change in CPU and GPU (at least not that benefits our app), but the dual-band WiFi increases networking performance (table downloads, posting to leaderboards, etc.) and battery efficiency is greatly improved. These also support OpenGL ES 3.0 but we haven't updated our engine to utilize it yet.</blockquote>

No members online now.

Total: 119 (members: 0, guests: 119)