Hi, The Swift Student Challenge Terms and Conditions doesn't explicitly state that source code will be judged. However, I'd still advise you to have a clean code, and to let some comments for hard parts of your code. Submissions will be judged on: Technical accomplishment in the submitted app playground; Creativity of ideas in the submitted app playground; and. Content of written responses to the questions in the submission form. Good luck for the challenge!

Hi @eskimo, as SwiftData is only available with iOS 17, and Playgrounds on iOS 16, is it an issue if features using SwiftData are only available for a specific version ? To bypass this issue, we could use a third-part library as requested by yuccc. Because if the playground is tested on iOS 16, some features could be missing.

Hi, Nothing in the Terms and Conditions says that it's not allowed. Also, previous winners did it, so I guess your answer is "Yes". Good luck ;)

Hi @Vision Pro Engineer, thank you for your response. I followed the link you provided, and it worked! Thank you very much. ModelSortGroup is the solution. I won't be using ManipulationComponent because I need visionOS 2.0, but it's a very interesting component. That said, I encountered a problem with ModelSortGroup in my actual application, not the demo one (where my image comes from). I couldn't find any explanation, but using generateCollisionShapes(recursive: false) didn't work, whereas my spheres (which are real entities loaded from files) worked when I manually created the collision shape. I tried displaying the collision shapes using visionOS debugging, and both methods seemed to produce exactly the same collision shape, position, etc. Is there a logical explanation? Thanks for your help, it really solved my issue.

Just to be clear, are CollisionFilter & CollisionGroup only working for physical collisions and not hit tests?