Unity apk crashes on start with Vulkan interceptor

Hello!

I have a trouble with profiling my Unity project. (latest Unity 2019.2.12)

I'm failed to use Graphics Analyzer from latest Arm Mobile Studio to profile Vulkan-based Unity application. I have just create empty test scene, add Vulkan interceptor (as specified at https://developer.arm.com/docs/101545/0504/target-installation/android/unrooted-android/installation/installing-for-an-opengl-es-unity-application), build apk, install it on Samsung Galaxy S9 phone, run it and faced a crash. Its not shown in the traceable list in GA Daemon Application also.

At the same time GLES interception method worked as expected. Empty scene with GLES rendering API and libMGD.so interceptor lib have worked without crashes, listed in GA Daemon Application and sends data to host application (I have set Android API level to 25).

Maybe Vulkan interception lib embedding instruction lacks some important steps? Are there succesfull attempts to profile Unity Vulkan-based projects? What the steps I should take to provide more info to solve this problem?

Thanks in advance, Alex.

Parents
  • Hi both, 

    At the moment we know we have some issues with Vulkan interception on Android devices, due to how we load the interceptor library. This is planned for a fix for Mobile Studio 2020.0 next year, but we have some ideas for workarounds which we'll test out next week and let you know how it goes. 

    The workaround tends to be specific to the Android version being targeted (targetSdkVersion in the Android manifest file) and the Android version on the device running the application. If you can let me know this info for your application / test device we can see if we can resolve your specific issue.

    Thanks, 
    Pete

Reply
  • Hi both, 

    At the moment we know we have some issues with Vulkan interception on Android devices, due to how we load the interceptor library. This is planned for a fix for Mobile Studio 2020.0 next year, but we have some ideas for workarounds which we'll test out next week and let you know how it goes. 

    The workaround tends to be specific to the Android version being targeted (targetSdkVersion in the Android manifest file) and the Android version on the device running the application. If you can let me know this info for your application / test device we can see if we can resolve your specific issue.

    Thanks, 
    Pete

Children
More questions in this forum