I took all the care to stop this jitter fully.Even after considering distance and Camera angle and hand movement factors little jitter is still there - Can't I make a 100% jitter free AR app?I have did the same experiment placing simple 3D cube as child to Marker Image Target earlier.It is working fine for a simple 3D cube,But the jitter comes when I import a 3D object like a car, van or truck which had shaders,filters,gradients and other features.

Another problem is heating - for three minutes play Device becomes so hot.Earlier I did some games using android studio.There ae can reduce this by modifying the settings like wait lock and others.Is there any way to make such power saving tricks through unity Developer Appliction?I didn't check Player Settings menu fully.if we can do such things It encourages the client market!

I don't think this is an issue with Vuforia and it's something you could be doing better.  My quick test seemed pretty solid: https://www.dropbox.com/s/mbi4l25sqz76zlw/EOCB7965.MP4?dl=0

Some things to try:

Make sure you enter a width of 1 when exporting from the target manager.  Don't scale the target after that, scale your models to it.

The pixel resolution on your image target is about 1/3 the resolution it should be.  Remeber that I said it should be 800-1000 pixels.

Make sure image target is clean and perfectly flat, tape it to something if you have to.

Read over the Image Target guidelines in the Vuforia library again.

To see where the problem lies:

Run the Vuforia samples to see if it's shaky.  If it is then it might be your particular device.

If not then I would parent your object to the sample target and see if it's some issue with parenting/scaling.

OK,I am following your suggestions one by one:

1).share your marker image if you'd like me to test:-I am attaching the marker image.It is decorated wit a gradient b blue clouds and metallic body ,but I am using B/W print.

2),You are using an old version of Vuforia, it may not come with the device camera profile for your phone.  It usually downloads an updated device profile when you launch your app.

OK, My Device is OPPO F3 and using Unity version of 5.4.3f1 and  Vuforia version of 6-1-17.But, I have installed Unity 2017 and so so ,that is recent version and tested this app and there is no difference.I tested that in a different device which is compatible with that version.can you elaborate on this device profile and its influence on this app?

3).How many other devices have you tried? 

OK,Most of the times I tested in this device only.Asper your suggestion I will test now in ther devices also.

4).make sure your 3d object origin is parented to the image target origin

Yes,It is perfectly transformed at position 0,0,0a and rotation 0,0,0 and scaling 1,1,1 from the begening.One small adjustment.Actual 3D object whch I took froma completed VR project is so laarge and was split into two parts - external body and internal cabi,So,here I made both of them childs to a common Unity .This Parent gameObject was made a child to ImageTarget with 0.04 scaling.All these levels were transformed position and rotation just like the above.

5).There are smoothing scripts you can find in the forums to smooth out the jitter:

Yes,I am also agreeing with you about the idea that little touch ups willl solve the problem.

Like I said, share your marker image if you'd like me to test.  From the video it appears you could probably get stable tracking from it and there's something wrong with what you are doing.

The three main factors are distance from target, quality of target and device camera.  You are using an old version of Vuforia, it may not come with the device camera profile for your phone.  It usually downloads an updated device profile when you launch your app.

How many other devices have you tried?  

Also make sure your 3d object origin is parented to the image target origin, is this is offsetted, any slight jitter will be greatly magnified.  

There are smoothing scripts you can find in the forums to smooth out the jitter at the cost of lag, but again I'm not sure you need it, just need to solve the inherent problem.

I am very happy for the response.Yes,the marker print is now dirty as I am using it for so long.But,the shaking which you have observed is the real problem and it is like that from the first hour from which moment I started to use that marker as fresh print

As I have seen other threads in the forum also which are similar in the description, I want to know one thing from you:This little shaking is unique for my app only or a general thing in AR apps.Why I am asking this is after so many trial and error updates and experiments I could manage that the model is not going out of view as it was before the corrections.Performance was improved,but my main prblem is client feedback.I took this project as converting VR into AR.If we compare the VR which never shows this shakingwith AR with this shaking will definitely be a drawback.

AS a programer myself I am suspecting the reason that taking vertices of3D model from app data and inserting into camera Input per each frame and blending these two vertices data with triangle back face culling might Giving this aberration.

Can we expect stability in this scenario in future versions?

Your target is not laying perfectly flat and the paper looks folded and crumpled.   I don't know the exact reason for the jitter, but start with the basics, and get a perfectly printed target sorted out first, then you can move on to find out the real issue.  Looking at the target and the distance you are holding the phone from it, you should be able to get it almost jitter free.  Feel free to share the target is you can.



 

Thanks for responding.This marker is having 4 stars in the admin marker upload screen.But whata bout the second marker which I am showing in the video along this question.This is the key project .This marker also got 4 stars in trackability estimation screen.One thing I sudenly want to tell you now.This actual image is color image.And the Print I am using is B/W. Is there any difference in this scenario for trackability?If you want to see the shaking effect You have to view the video patiently upto the end.In the last frames It just starts the dwindling.

Looks like your image target is too simple, it probably needs more feature points.  Look at the yellow feature dots in the target uploader and you'll see it only tracks corners, your target has a lot of curves which will be ignored.  Try replacing it with another image that has alot of contrasting detail and you'll probably see an improvement.  Another thing to try is different sizing on the target you uploaded, 800-1000 pixels wide is about right.  Much more than that and you'll see poorer tracking.  If you have to use this marker, think of how you can add detail to the design of it.  Other than that you can try to do a ground plane+image target combo, but it gets more complex.