All tags

Sign up for our newsletter to always be informed about the latest news in the world of technology

You have successfully signed up!

We have sent you to the specified e-mail with a link confirmation.

8 July 2019

Imagination delivers new and enhanced developer tools for AndroidLatest PowerVR tools include specific support for Unity™ and Unreal Engine 4™

July 8th, 2018 – Imagination Technologies, a leading technology provider for graphics, neural network acceleration and connectivity, announced new and enhanced tools to help developers optimise Android™ graphics performance for devices with PowerVR GPUs. These are: PVRMonitor for real-time GPU and CPU performance statistics; PVRTune for profiling and analysing applications; and PVRStudio for seamless CPU/GPU debugging on PowerVR devices.

David McBrien, EVP Sales and Business Development, Imagination Technologies, says, “PowerVR GPUs have a significant presence in Android handsets, particularly with new chips coming to market from Unisoc and MediaTek in the coming months. It is strategically important for us to provide graphics developers with the best tools to take advantage of our GPU technology in the full range of Android devices, from low-end to high-end. We provide professional tools at no cost to developers because we understand that without outstanding applications, no one will buy the hardware.”

As well as helping developers to get the best performance out of the many devices with PowerVR GPUs, these tools can also help improve the development of applications for any Android phone, tablet, or OTT device.

Carlos Sarria, Senior Developer Technology Manager, Imagination Technologies, says, “Imagination has been providing powerful tools for 3D graphics development for over twenty years, backed up by our extensive technical support and documentation. Our tools are consistently ranked highly by developers thanks to our complete, fully-featured set of performance analysis, debugging, and asset optimisation utilities which are continually improved and updated.”

New versions of PVRMonitor for Unreal Engine and Unity

To make developers’ lives easier, PVRMonitor, PowerVR’s real-time GPU performance monitor for Android, is available as a plug-in for Unreal Engine™, with Unity™ support coming this quarter. Developers simply drag and drop the PVRMonitor widget onto their app. Once their app is launched, developers will find PVRMonitor gives a quick and easy way to view statistics such as frame rate and hardware counter values as an overlay on the development device.

With this latest version, developers now have instant access to the full range of hardware counters previously only available through PVRTune. These include cycles per pixel/vertex, texture processing load, shader units load, and dozens more.

Developers have full control over the statistics they want to see, laying out as few or as many counter graphs as they like, setting threshold values, and even setting which colours indicate high and low values for quicker interpretation.

PVRTune enhancements

PowerVR’s hardware profiler PVRTune now has Vulkan™ and OpenCL™ support, including support for visualising Vulkan debug markers.

PowerVR will be demoing the latest enhancements at GDC which also include:

– Full shader source-code profiling

– Improvements to memory usage reporting, including new software counters for tracking application and driver memory usage

– New statistics report window

– Syntax highlighter for GLSL

– Easier deployment and direct connection to devices via the GUI

PVRStudio new features

Offering developers seamless debugging between GPU and CPU, the latest version of PowerVR’s IDE PVRStudio now offers Android deployment and debugging, with full support for OpenCL, OpenGL ES™, Vulkan and more.

Other recent developments that PVRStudio now offers include:

– GPU conditional breakpoint support / conditional shader breakpoints

– Page fault capture

– Shader source and unified shading cluster (assembler) intermixed debugging

– Improved readability of unified shading cluster code and values passed to the shader

The original of this article