By Ursanon
on Mon, 12/03/2018 - 08:17
Hello! I found Vuforia's performance decrease on low spec Android devices.
After few moments with 60 fps app starts to freezing, profilling in Unity shows that "unaccounted time between: InputProcess and InputProcess"
grow over time from 0 to 98% of CPU usage. It can be reproduced even with Vuforia's examples.
On Unity 5.5 with Vuforia 6.2.10 everything is OK, fps are stable.
Tested on:
- Asus Zenphone 2 Laser ZE500KL.
- Unity 2017.3, Unity 2018.2, Unity 2018.3
- Vuforia 7.2, Vuforia 7.5.26
I can provide adb logs or some profiler datas if needed.
Hello,
Hello,
We'll take a look to see if we can determine the source of the issue. Any additional information, particularly profiler data, would be helpful.
Thanks,
Vuforia Engine Support
Well thats been quite some
Well thats been quite some time...
Could you please at least tell us wether we can ever expect a fix for that?
Hello,
Hello,
Thanks for the information. I'll respond with any relevant updates to this thread.
-Vuforia Engine Support
Hey !
Hey !
Great to finally get a reply from you :) !
Can you give me any estimation on when we might get some more information on this ?
Just so that i know wheter it's worth switching to AR Foundation or not?
Hello,
Hello,
As we don't understand the issue or why it is occurring, I have no estimates to provide. This issue's investigation stalled because there was no response from the original forum user.
Thanks,
Vuforia Engine Support
Hey medabit !
Hey medabit !
If you dont understand the issue just ask me for more specifics ! I can't give you my project but i can tell you in great detail my settings.
Hello,
Hello,
Thanks for the offer. I've submitted the issue to core engineering as a bug to be investigated.
I will post back here if there is any additional feedback required, or if I have any updates.
Thanks,
Vuforia Engine Support
Hey medabit !
Hey medabit !
Can you tell me if this problem is actually being worked on?
I have to make decisions on how to proceed with our projects and i need to know if this will be fixed anytime soon...
Hello @timayno,
Hello @timayno,
No update on the issue you've reported, and no ETA on a workaround/fix at this time. Apologies for not having any additional information.
I do target 30fps actually
I do target 30fps actually and it would be totally fine if it were stable, continuous 30 fps but it feels a lot more like its constantly dipping into 5-10 fps territory and up again.
Hello,
Hello,
Thanks for the response. I see that the ticket has been assigned for investigation, so I remain hopeful.
-Vuforia Engine Support
Hello @timayno,
Hello @timayno,
Can you specify which features you're running when observing this? Image Targets? Device Tracker? Model Targets? Combinations?
Thanks,
Vuforia Engine Support
My app uses image targets and
My app uses image targets and ground plane in the same scene but the user starts with selecting one of those two at the beginning and the unused components get deactivated.
Any update on this ? Were you
Any update on this ? Were you guys able to reproduce the issue ?
I would think that this a problem with how vuforia accesses the camera image on huawei phones.
At least all hints points towards this likely being the culprit.
Hello,
Hello,
Thanks for the additional feedback. I've added your observations to the ticket comments.
I just checked the state of the ticket and there are still no updates on the issue. It is still under investigation.
-Vuforia Engine Support
Hello,
Hello,
We've done some extensive testing with Huawei devices in our inventory but unfortunately have not been able to reproduce the issue.
Hi !
Hi !
I have those Problems on a Huawei P Smart - Build Number : FIG-LX1 8.0.0.170(C432)
and on a Huawei Media Pad huawei-m3-btv-w09 - i can't report the exact build number right now but will do so as soon as i will have it in my hands again
Hello @timayno,
Hello @timayno,
Thanks for the feedback. We'll work to procure the Huawei P Smart in order to replicate.
-Vuforia Engine Support
Hi !
Hi !
Here's the Build number for the other Huawei M edia Pad huawei-m3-btv-w09 device that is having the same issues.
BUILD NUMBER: BTV-W09C100B305