NFT positions 3D model differently for different images?

[ODINN555]

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
My test repo: https://github.com/ODINN555/ArExample/tree/master

I have 1 NFT image called "goodjob" under ArExample/goodjob/ which when I use it the AR works and the 3d model appears fine,
but then when I use another NFT image named "city_with_code7", the model does not appear.
The city nft does get tracked and I even debug it with "markerFound" and "markerLost" events.

My suspicion is that because the image is different, the 3D model is placed in a different location in the scene. But if it is the case, how can I measure how much to move the 3D model to appear correctly?

If the current behavior is a bug, please provide the steps to reproduce.
Clone my repro: https://github.com/ODINN555/ArExample/tree/master
first use the goodjob image (update the nft url to https://[YOUR GITHUB URL]/ArExample/goodjob/goodjob)
then use the city_with_code7 (update the nft url to https://[YOUR GITHUB URL]/ArExample/nft/city_with_code7)

https://github.com/ODINN555/ArExample/tree/master

Please mention other relevant information such as the browser version, Operating System and Device Name
Tried in both desktop and mobile, the problem persists in both
What is the expected behavior?
both images should be displaying the 3d model
If this is a feature request, what is motivation or use case for changing the behavior?

[ODINN555]

[Update]
After trying to adjust the size and position of the 3d model, i got it to be visible, kind of as seen in this image:

but the model is very glitchy, it is not only black, it is you can also see white in some areas and sometimes you see through the model.
Does anyone know why this is happening? the model shows fine with different settings on a different nft image. why on this one isnt?

You can see the changes ive made in the "newImageTesting" branch in the repo above (https://github.com/ODINN555/ArExample/tree/newImageTesting)

[kalwalt]

Hi @ODINN555 it could depend by the dpi and size of the NFT, if it is too low you must be very close to the image to scan and goes outside of the FOV.

[ODINN555]

Thank you for your response,
It is true that the resoultion of each image is different, but it shouldnt effect this drastically...
for the first image the scale of the model is 100 and for the second it is 800.
and it does not explain why the model is glitching out like in the image I sent above

[ODINN555]

Managed to fix the "glitching" by adding this script:
<script> // Workaround for an AR.js bug (https://github.com/jeromeetienne/AR.js/issues/410) const sceneEl = document.querySelector('a-scene'); sceneEl.addEventListener('loaded', () => { sceneEl.camera = new THREE.PerspectiveCamera(); }); </script>

I do still think that the issue I mentioned above is a bug.
The camera is at the same relative position to the images (I scan them from about the same distance), there shouldnt be such a drastic difference in positioning because of the resoultion or dpi of the image.