Hello,

Here is more information on a regression introduced in Vuforia 7.5.26:

https://developer.vuforia.com/forum/unity/known-issue-vuforia-7526-does-work-net-scripting-backend-uwp-unity

Thanks,

Vuforia Engine Support

I cannot reproduce comma/dot issue mentioned here.

Using Unity 2018.2.14 with Vuforia 7.5.20, switching to scripting runtime version .net 4.x and importing and using the default databases works for me both in the editor (Mac) and on iOS.



I'm pretty certain that is because my system's CultureInfo is one that uses '.' as a decimal separator, but yours isn't.

Nevertheless, I'd like to ask you to use the script attached to provide me more information so that I can reproduce the same issue and fix it.

Just drop the script into an Editor folder in any Unity project that is set to use .net 4.x

You should immediately see log messages like this:

Current CultureInfo is 'en-US'

Current NumberDecimalSeparator is '.'

If you could post what is logged for you that would be very helpful.

Thanks,

Vuforia Engine Support

I went to Unity Los Angeles last week where unity encourage us A LOT to use their new job / ECS systems / burst compiler. Augmented reality apps are really hard on the CPU. I tried once again to switch to C# .NET 4.x but even with the latest vuforia version 7.5.26, it doesn't work.

This is a HUGE bummer at the moment and Vuforia reps should give us an ETA. Thank you.

Hello,

All of our samples are still set to use .NET 3.5. Before Unity 2018.3, .NET 3.5 was the default.

We're working on a fix, but no ETA at this time. Apologies for the inconvenience.

Thanks,

Vuforia Engine Support

Update: Well, it's more than an annoyance.

Image tracking works, but no luck with Multi-Targets. Unity Editor crashes instantly when finding it. Interestingly, on NET3.5 there is no crash but it still does not track the Multi-Target.

Also, leasson learned: Changing the commas to dots works while Vuforia imports the databases, but it leads to crashes in runtime. So do NOT change the commas to dots, instead override the target's size. For image targets you can do that in the "Advanced" editor portion of ImageTargetBehaviour.

@Vuforia team: Please get an issue tracker. Forums are no professional choice for this.

I'm currently developing an app with Vuforia 7.5.2 where this has not been a (real) problem so far.

I can build for iOS without problems, hope it stays this way.

Only annoyance is the Comma/Dot-Thing while importing. It should be simple to fix?! Isn't it just setting the right FormatProvider? Vuforia team, go.

Has this issue been officially addressed somewhere? I encountered this problem too, and I can't find whether it will be fixed or not.

I am not able to import any database. I just wanted to use Iamge recognition. I am aware of that, there is the problem with commas and dots in xml files. But fixing this issue (and others) it is still not enough, app won't compile. I can't downgrade my app to .net 3.5 and i don't know what to do now. 

Does it crash only with object target recognition or images too?

Hello? Vuforia devs? Can You give Us some answers? Unity 2018.2.6f1 and Vuforia 7.2.23 there is still this problem. 

I'm having the same issue as well with Unity 2018.2.5f1 android + Vuforia 7.2.24. I did swap the " . " and the " , ". It does remove the warnings but I get a hard editor crash upon object target recognition. I reverted to .NET 3.5 equivalent until they fix it.

Okay, So after a few days trying to make it work, i've found a suitable solution : you can manually modify the xml document located in : YourApp/Assets/StreamingAssets/*yourdatabasename*.xml, and change the "."  of the imageTargetsize to a ",".

The reason is, as explained before by vuforiaBlocInBloc (thank you verymuch!), that the value hasn't been parsed the right way to be understood by .NET 4.6.

For Database issue with Vuforia + .NET 4.6 (in both Unity 2017.3 & Unity 2018.1),

you can notice this warning in console when you add an image Target in the scene : "Found illegal itSize attribute for Image Target ... in config.xml. Image Target will be ignored."

This is because the size value in the .xml come from Vuforia is not in the right format for .NET 4.6.

<ImageTarget name="..." size="10.000000 9.857955" />

Correct way :

<ImageTarget name="..." size="10,000000 9,857955" />

The reason :

.NET 3.5 :

• float.Parse("9.857955") => 9.857955
• float.Parse("9,857955") => 9857955

.NET 4.6 :

• float.Parse("9.857955") => Exception
• float.Parse("9,857955") => 9.857955

But Unity crash when Vuforia detect ImageTarget with .NET 4.6 (Unity 2017.3.1 & Unity 2018.1b9) on both macOs & Windows Editor...

Edit : My global CurrentCulture is "fr-FR", I tried to change for invariant or "en-US" but Unity always crash.

If anyone comes across with the same issue, here is my bug report.

https://developer.vuforia.com/forum/issues-and-bugs/video-background-bug-net-46

It doesn't seem to work perfectly on Android.

As soon as I switch from a scene to another, there's an error produced and the AR video background freaks out. It never comes back after that.

If I revert back to .NET 3.5 everything works fine. I tested on iPad and I don't notice any issue.