Hello,when I work with more than one scene in Reality Composer and want to switch between them during the play mode, an annoying bug appears.After switching between two scenes in an AR play-mode for the first time (by using a "tap"-trigger and "change scene" action sequence), the ground plane "jumps" together with the whole second scene to a different place in the room. So the plane/grid and all objects from the scene are not standing on the ground or on a table anymore (where I placed them before turning the play-mode on) - they are floating ca 0.5-1m above the recognized ground surface in the range of 1-3 meters to the left or to the right to the position from the second scene.This happens always when I switch a scene in play-mode for the first time. After that all other scenes appear on the same wrong position above the ground.I used "horizontal anchor" for my scenes, but the same error happens by using "vertical anchor". It doesn't happen when I use "image anchor", but I need "horizontal anchor" for my project.I attached a video with the problem and a project file here:https://drive.google.com/file/d/1CY1kLqMbNFzcHN-PtDhYs0bRQVRV7Ova/view?usp=sharingAnyone also facing this problem?

When working with "Look at Camera" action I noticed that the action has some problems with groups of objects after exportig the project as a .reality file.I created a group with an image, a text and a primitive shape and wanted to apply the "look at camera" action ( face was set to "front" and rotation to "yaw") to the whole group. In the play-mode in Reality Composer it worked very well - the group was rotating properly, so my image always faced the camera.But after exporting the project as a .reality file and opening it in AR Quick Look the group was not showing correctly - it iwas laying on the ground and doesn't look at the camera properly.https://imgur.com/a/9kHpGeuI found a workaround - you have to place the group in Reality Composer wrong ( rotate it, so it is laying on a side) and than it is working in AR Quick Look almost correct. But is is unhandy to work like that - I have to export the project every time I want to know how it really looks like in AR Quick Look.https://imgur.com/a/Hl3AJGgHere are my .rcproject and .reality files :https://drive.google.com/file/d/1sAZt0GXBtkRvTvqQZzNKbCI4oBDLyG-M/view?usp=sharingIs there any other way to make groups and "look at camera" action work together correctly?

Hello everyone,I had some problems with buttons and tap-trigger in AR Quick View.If I place a button-object and another object over the button ( in my case it was a sphere, or an imported usdz object) and export the project from Reality Composer as a .reality file - the button loses it's interactivity. It is working in a Reality Composer play mode ( in the example video I attached the sphere starts moving if you tap the button) but nothing happens if I export the project and test it in AR Quick View.Here is a small example of this problem (with attached .rpproject, .reality and two videos of testing the scene in Reality Composer play mode and in in AR Quick View) :https://drive.google.com/file/d/1eQa-pCEihRVtgP7jJUlpfhG5PjKZulJB/view?usp=sharingDo you have any ideas how to fix this problem?

I noticed that after exporting interactive USDZ files or reality files from Reality Composer and opening them in AR Quick View some touch events don't work at all/ are being ignored. Especially when: a) the object that should be touched was scaled in Reality Composer and has lower or greater scale than 100% b) the object the user should tap/touch is laying too near to other objects - for example a cube is laying on a chair. In this situations the touch event is not working in AR Quick View, even if it worked in Reality Composer play mode. Is there a workaround for this problem?