Right now I have a bunch of .usda files in different folders, in order to use findEntity(named:) I would need to reorganize the assets and put all the models into a single .usda right ?. That's the only way ?

Thanks, I have summited the bug.

These models I’m preparing and then exporting are actually in its own composer pro project, not in the one included in xcode. The app will load models (usdz) from a cloud service at run time, and I need these models to have certain properties so it can work with other stuff in the app and with other usdz’s. That’s why they have this custom component so they can interact correctly when the user inserts these models into their session. Does this make sense ? 🙂

Hi, Here is more information. Xcode: Version 16.0 (16A242d) Composer Pro: Version 2.0 (448.0.16.0.3) VisionOS: 2.0 I tried the component 2 ways. Model A: In composer add the component, set some values as not to use the default ones, to a 3d model and export that model as a usdz Model B: In composer add the component to a simple cub that will be part of the scene. Also setting some values as to not use the default ones. The component is registered in the app main, init with RealityKitContent.MyObjectComponent.registerComponent() Or. not sure what the difference is but its the same result. MyObjectComponent.registerComponent() Then in the immersiveView var body: some View { RealityView { content, attachments in \\...... after everything is setting up I print the entities in the scene with that component including the one inserted from the usdz For model A: all the values are different. Some are false, some are true. Not idea where that comes from, it's not what I setup in composer For model B: all the values are at their default false, not what I set in composer I can add the component manually in code, set values and it works correctly, but I want to be able to set the values in composer as I will be exporting these usdz’s

That worked Perfect ! Thanks Geoff