3D Cameratracker unable - now able, and other fixes

Finally after one whole year, it seems that die "unable to acquire rendered frame" error is fixed in the 16.1.2 release.

I testet it for example with 3 problem-clips of 360material which never worked in CC19 before, but always in "early CC18".

The processingspeed seems slightly improved by 10% on my machine under OSX 10.13.6.

So hopefully all the others here around who have complained the same issue in vain for more then a year now, can confirm that as well for Win10 (I would need that information for another project /company I'm working for).

So finally my last words about it.

Why can I not find this issue mentioned in the "fixed in june edition" list ?

Was it fixed only by chance ?

Some here announced that the developers could reproduce it and ...... but why then, is there no notice about it in the fixed-list ?

Another behavior I'm really missing:

Maybe it is a good idea that , before responding to a comment ..

1st read

2nd think about it whether it is a) true - b) important - c) nice

3rd write the comment

before blaming the customer of his fault using

unprofessional material

an unappropriate hardware

beeing not professional enough

sending testfiles of an issue everyone has

everyone is glad to get real help , I will be as well