Platform and Integration Notes

AMP is normally initialized during the GFx::System object construction, or during the GFx::System::Init function call. Alternatively, if a Scaleform::System is instead used to initialize Scaleform, the programmer needs to explicitly initialize and shut down AMP by calling GFx::AMP::Server::Init()and GFx::AMP::Server::Uninit(), respectively.
AMP needs to receive information every game frame in order to display memory and performance statistics. The following call should be inserted in the rendering thread to explicitly update AMP: AmpServer::GetInstance().AdvanceFrame()
The AMP client application is currently available only for Windows.
AMP server is currently supported for Windows, PS4, Linux, Mac, Android, iPhone/iPad, and XboxOne. Using the automatic discovery feature of the AMP client, connecting is straightforward. However, connecting without automatic discovery requires knowledge of the IP address for the AMP server, which can cause confusion because some platforms have multiple IP addresses.

For the PS4, if the development kit is configured to use two IP addresses, please make sure to specify the application IP address, not the IP address used for debugging.
For Android, internet permission needs to be enabled at the application level. To do this, the following needs to be added to AndroidManifest.xml for the application:

For the XboxOne, AMP works only on development consoles. Applications that want to use AMP need to specify a SecureDeviceSocketUsage of SendDebug and ReceiveDebug in the XboxNetworkingManifest. For example:

  <mx:Extension Category="windows.xbox.networking">
    <mx:XboxNetworkingManifest>
    <mx:SocketDescriptions>
    <mx:SocketDescription Name="AMP" SecureIpProtocol="Tcp" BoundPort="7534">
    <mx:AllowedUsages>
        <mx:SecureDeviceSocketUsage Type="SendDebug" />
        <mx:SecureDeviceSocketUsage Type="ReceiveDebug" />
    </mx:AllowedUsages>
    </mx:SocketDescription>
    </mx:SocketDescriptions>  
    </mx:XboxNetworkingManifest>
</mx:Extension>

Some game engines, such as Unreal Engine 3, package their assets in such a way that makes it impossible for the AMP server to locate the AS2 SWD or AS3 AS files corresponding to the flash content being profiled. If that is the case, please make sure to place the SWD or AS files in the AMP client working directory, rather than relying on the AMP server to find them in the same directory as the SWF and send them over the network.

Platform and Integration Notes

Parent topic