Closed MaheshXr29 closed 11 months ago
Hello,
Can you please provide the following clarifications:
Thanks, Vuforia Support
hello, something similar happened t me too i was working on image targets before a while with v10.15.4 it was working properly but, after i updated to v10.17.4 the cam is not even responding and the same thing happened to my friends projects too the ar camera turned black all of a sudden
@zoro-the-lost, please create a new bug report as this sounds like a separate issue. Thank you.
Hello,
Can you please provide the following clarifications:
- Which version of the Area Target Generator was used for generating the device databases included in the app? Note that for optimum performance and compatibility, we recommend using the same version of the Area Target Generator as the Unity Extension (i.e. 10.17.X).
- Has the scanned environment changed? Has the placement of furniture or objects within the space been moved or removed? Area Targets are robust to changes, but there is a threshold for which too many changes will cause the space to no longer being detected without rescanning.
Thanks, Vuforia Support
Hello,
@MaheshXr29 thanks for the response. Seems unlikely that the issue would be related to device database compatibility or changes in the scanned space.
Which version of the Unity Editor are you using? My recollection is that we had recently bumped our minimum supported version to 2022.3.5f1+ for Engine 10.17.
Lastly, have you tried testing the device database in the latest version of the Vuforia Creator app?
Thanks, Vuforia Support
2021.3.24f1 is the Unity version I am using. I tried the device database in the latest version of vuforia creator app , It is working and I have one more doubt, since you mentioned minimum unity version for vuforia 10.17 is 2022.3.5f1 , I am using vuforia model targets in my another project which is on unity 2020.3.47f1 and vuforia 10.17 and It is working good but my area targets project on 2021.3.24f1 is not working ,I used same vuforia version in both projects . what could be the reason for the issue with area tragets. Should I need to change some settings in the editor ?
Hello,
I tried the device database in the latest version of vuforia creator app , It is working
Great to hear! This means that the issue is not related to the Area Target device database.
Should I need to change some settings in the editor ?
I don't believe that this is the case. Since you're using the same Engine version (10.17), that setting would be set in both projects.
Since you've proven this issue is not with the Area Target device database, I would suggest you try the same in our Area Targets Test App for HoloLens.
Closing due to lack of activity. Feel free to re-open if there are any updates or new developments.
Summarize the bug: I have been working to create a sample project using Vuforia Area Targets ,It was working flawlessly for a while but all of sudden area targets is not all getting detected.
Observed problem I have tried various solutions that has been mentioned in different forums and I think version of vuforia is reason for this issue. First we used vuforia 10.15 version with this version it is working good , but all of sudden it stopped working , even I tried updating vuforia package versions but no use . Similarly my friend is also facing same issue, when updated vuforia version to latest(10.17) Area targets stopped working.
Expected result Area Targets should be detected as before and the content in the area targets to be positioned accurately as it was in android platform.
Other observations Taking too much time to detect Area Target
Affected Vuforia Engine version: E.g. v10.15.4. & v10.17.3.
Affected platform:
Affected device:
Screenshots / Video Recordings Share any screenshots or video recordings from the platform or device. You can also use the Session Recorder.
Affected database If applicable, share your database / dataset which is affected in the issue you're experiecing.
Device or platform logs
Share any logs from the platform or device.
Workaround Is there currently a workaround that you're using?
Additional comments Add any other details about the problem here.