Try using HasModel instead of ModelEntity. Your best bet at solving this is putting a breakpoint after setting map and having a look at the contents with Xcode's inspector.

Sounds like you might want to change the properties in PhysicsMassProperties for your object when it's in dynamic mode, maybe your impulse isn't big enough.

Since iOS 15 / macOS 12 we can now add shaders in RealityKit 🎉 The entry point for these is GeometryModifier and SurfaceShader. The usage of these is used in the Underwater code sample: Building an Immersive Experience with RealityKit

In RealityKit the animation will always take the shortest path to get to the correct transform. This means that rotations will take the shortest distance. If you want to force the animation to go the other way around you'll have to add two animations in sequence: the first one goes half way round the anticlockwise direction, and the second is the final transform of your entity. This also means that you can't spin around an axis object continually without doing something similar - which is very annoying!!

Not with the builtin MultipeerConnectivityService, but you can always encode your own data to then send over a TCP connection to another device. The collaboration data can be grabbed with session(_:didOutputCollaborationData:) - https://developer.apple.com/documentation/arkit/arsessionobserver/3152999-session then sent over your network instead. I think if you go to any further detail then you'll need to create your own data structure for sending instructions between devices, which is certainly achievable.

+1 for attention to finer but much needed detail like this please! Or just being able to set blend modes if that's the issue.

Make sure you import ARKit at the top of your swift file, the different AR configurations aren't included in just RealityKit: swift import ARKit

I would guess that the labelNode has a parent with a scale of [0.01, 0.01, 0.01]. Scale (as well as position and rotation) is inherited from the node's parent, so if a parent node has a very small scale, then even if the parent scale is increased again, the position will be multiplied by the parent's scale. There are some methods in SceneKit to help with the maths involved in these operations such as this one: https://developer.apple.com/documentation/scenekit/scnnode/1408018-convertposition And you can set the worldPosition of a node too https://developer.apple.com/documentation/scenekit/scnnode/2867405-worldposition