<a-camera> and <a-entity camera>

[snavas]

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

I am not that sure if this is a bug or I am requesting a feature

What is the current behavior?

As far as I understand from the documentation, <a-camera> and <a-entity camera> should have se same behaviour, in the same way as <a-box> and <a-entity geometry="primitive: box"> do. However, if I use <a-camera>, AR.js show the AR entities way off the marker. I am using the following versions of a-frame and ar.js:

<script src="https://aframe.io/releases/1.0.4/aframe.min.js"></script>
<script src="https://raw.githack.com/AR-js-org/AR.js/master/aframe/build/aframe-ar.js"></script>

From the examples in the Ar.js documentation I can asume <a-camera> should be used for location-based AR and <a-entity camera> for image and marker-based AR. However, if this is the case, I think it should be indicated more clearly in the documentation. However, which camera entity should I use if I ever want to combine location based and marker based AR?

If the current behavior is a bug, please provide the steps to reproduce.

This is my code using the <a-camera> and exhibiting the wrong behavior:
https://codepen.io/snavas/pen/yLYBPbL

Please mention other relevant information such as the browser version, Operating System and Device Name

What is the expected behavior?

I would expect <a-camera> and <a-entity camera> to behave in the same way.

[nicolocarpignoli]

They behave differently. Actually is not possible to combine marker based and location based. You can find more here: #29

We can continue the discussion in there, as I think this is a duplicate of the issue linked.