thanks, will do. I know it may look like a minor thing, but after spending time developing with RCP2 it feels big when a workflow no longer works and the newer ones feel like they have fewer features. or not as convenient. for my current work around i've made a mesh resource with multiple material slots. I still prefer the decoupled way it worked from USD files.

is there a working sample for non AR scene? I got it half working but my result is pretty flat, not relative to camera. This is really hard.

"Build & Run in RCP3 into a device or simulator" thanks for your explanation. i just started using RCP 3 yesterday and i got stuck on this. build and run on device pushes the changes to my app.reality file but build and run on simulator does not. what could i be doing wrong? running on device is getting tedious as it takes a while to run my app and then i have to quit it and go back to xcode to do my work.

lol. yeah, that was a while ago. thank you anyway, i will still look into that. i ended up including ffmpeg into my game, a bit overkill but it worked. also had issues with race conditions while syncing multiple tracks. not sure how i feel about saving to disk and then read. seems like there would be a lot of writing also how fast will the file be ready to play? does the full file need to covert before access? some songs are multi tracks with up to 8 tracks.

i submitted a report to apple about this and their reply was to post in these forums with the tag wwdc25

omg, this has been driving me nuts for years. i only work on my laptop and the real estate this take is too expensive.

i'll test it out in the weekend.

i think it has something to do with authentication. it doesn't happen in iOS safari or desktop chrome. and it doesn't happen on my older iMac. just my MacBook with touch ID.

good to know. i didn't look other methods of importing, just the one you used which the documentation didn't explain much other than "it blocks your application while importing" i haven't gotten into reality kit, but this will be useful when/if i do. the documentation seems to have a lot of holes (like usual)

well, what does your code look like?

my game uses all regular apis and just realized "scale to fit below built-in camera" was applied which made my SpriteKit overlay to fit quire right. of course now I know that, but I can't figure out how to make the scale to fit to selected by default.