drewolbrich.bsky.social
I'm creating a special relativity explainer app for iPhone, iPad, and Vision Pro.
https://www.lunarskydiving.com/relativity/
519 posts
388 followers
628 following
Regular Contributor
Active Commenter
comment in response to
post
That’s ridiculous. Boats don’t fly.
comment in response to
post
??? in the past did you drive to Cupertino or take a train or walk?
comment in response to
post
I don’t see this.
comment in response to
post
That's probably wise.
I think if you've chosen to create a game of any complexity using either SceneKit or RealityKit, you've also taken on the task of creating your own bespoke game engine and tool set.
comment in response to
post
Congratulations, Tim!
comment in response to
post
Given a choice between SceneKit and RealityKit, I recommend not basing a new project on the API that no longer seems to be supported.
comment in response to
post
RealityKit has been updated every year since it was introduced in 2019.
SceneKit and RealityKit both support AR and non-AR rendering.
On visionOS, SceneKit is not supported for stereo 3D rendering, and only works in a flat window.
comment in response to
post
WWDC17 featured a "SceneKit: What's New" session video developer.apple.com/videos/play/...
Then, in the seven years that followed, Apple never updated SceneKit or mentioned it at WWDC again.
I don't have a source because AFAIK, Apple provided no communication except through silence and inaction.
comment in response to
post
Nice, thanks for writing this up.
fwiw, for 3D, SceneKit was superseded by RealityKit in 2019.
comment in response to
post
Thanks! Yes I am planning to go. We should meet up and talk science apps! I'll DM you. 😀
comment in response to
post
😀
comment in response to
post
Shouldn’t it be WWDC26?
comment in response to
post
👀 …
comment in response to
post
Hopefully it’s not also shorter along the time axis.
comment in response to
post
comment in response to
post
That's great to hear.
Maybe MeshResource.Contents was overlooked in the Swift 6 transition and the set of external developer using MeshResource.Contents and adopting Swift 6 last summer and who would actually report the issue as feedback was small.
comment in response to
post
WHERE ARE YOUR EYES GREGORY
comment in response to
post
It really is.
Either your eyes are in the front of your head to help you chase down other animals to eat them, or your eyes are on the sides of your head so you’re always on the lookout for the animals that are trying to eat you.
comment in response to
post
It’s much crazier than that — 330 degree wrap-around vision.
comment in response to
post
Maybe this is a good case for submitting a technical support request (bottom of page) developer.apple.com/support/tech...
Oh neat, it seems there's no longer a limit of 2 of these per year.
comment in response to
post
I have just enough experience with AVFoundation to taste crippling PTSD anxiety while reading that, but unfortunately not enough experience to help you.
comment in response to
post
Does it happen when you have Picture in Picture mode enabled on iPhone?
comment in response to
post
Meanwhile, I've revised gist.github.com/drewolbrich/... to use MeshResource.generate(from:) instead, which is synchronous.
The updated version of the Gist should no longer generate any errors, but unfortunately is not async.
comment in response to
post
One workaround is to change the import statement at the top of the file to
@preconcurrency import RealityKit
although that's a little unsettling
comment in response to
post
I did notice that RealityKit defines MeshResource.Contents as not conforming to Sendable, though. Maybe that's the core issue.
Perhaps Apple will update this next month in Xcode 17.
comment in response to
post
I don't have a lot of experience with Swift 6 yet, and I couldn't figure out how to make the error go away while still keeping the method asynchronous.
comment in response to
post
Thanks for reporting that!
I wrote the GenerateSolidInterior extension in 2023, before Swift 6 was introduced, and I assume you've configured your Xcode project to use Swift 6.
comment in response to
post
It can be confusing because visionOS 1, released the same year as iOS 17, did support RealityKitContent.
comment in response to
post
And you can’t do math without pants.
comment in response to
post
I might be wrong but maybe the issue is RealityKitContent wasn’t supported on iOS 17, so if an existing Xcode project was targeting that iOS version, it wouldn’t work. A freshly created Xcode project would target iOS 18 only and would support RealityKitContent.
comment in response to
post
Steve Austin has entered the chat.
comment in response to
post
I do not know
comment in response to
post
is it too late for me to learn the algol?
comment in response to
post
This does help me a lot, thank you.