Incompatibility

February 28, 2015 - 6:15am #1

Hello,

In this moment we are experiencing problems due to the incompatibility with the old flow of creating device targets which results that part of our platform features are unavailable.

 

The issue in details is as follows:

Its necessary for us to still download the DAT/XML files for a single target with the option to name the package with the name of the uploaded one. After the change to 4.0 we can’t do that instead the only option is to download the whole database, which for us its not feasible. As well there is no way to create new database without the licence key.

 

Please let us know what can/must be done, because we were expecting a period of compatibility before the planned mandatory switch.

 

Best regards

 

Borislava Krasteva

Marketing Manager
Seac02  S.r.l.

Incompatibility

May 6, 2015 - 3:03pm #4

With today's release of Vuforia SDK 4.2.3, the ability to download partial quantities of targets to a DataSet from a Device DB has been restored.

Incompatibility

March 1, 2015 - 10:41am #3

They have broken and/or severely limited the workflow..........The new target manager is a complete PITA. 

 

For those of us who had huge databases and only downloaded the targets we selected, we have to go through and re-design our databases and manually re-enter all the targets??? 

 

Incompatibility

March 1, 2015 - 7:12am #2

This is affecting us too.  We want to update our Vuforia 3.0 app (Apple is still allowing non 64 bit updates, just not new apps).

The new database download format won't allow us.  We have a database of 65 targets.  We seperate this into 5 datasets.  When downloading we just checked off the ones we wanted in each dataset.  Looks like Vuforia thought we only seperated datasets into different databases.  We probably could download the whole databse 5 times and edit the xml, but the filesize now becomes too large becasue we have to include the data file 5 times.  Everythnig Vuforia stated made it seem that things would work the same as before for the next month...  

Are there any workarounds for this?

 

 

 

 

Log in or register to post comments