.. but not the actual content of the image, the only criterion I care about ?!

Interesting .. I was struggling with this too and the example helped. One question, though. We don't know what is contained in "MyScene" but I assumed that it contained a node called "camera" for the pointOfView (POV) parameter, else cameraNode would be nil. So I put my scene in place of "MyScene" and ran it. Imagine my surprise when it rendered in the view, even though I have no POV node in my model. Just to be sure I changed the SceneView creation to: SceneView(scene: scene, pointOfView: nil, options: []) and it still rendered nicely. So SceneView has a default POV, which makes sense given pointOfView is an optional, but its location is not documented (it looks to be somewhere outside the model on the +Z axis). In fact, scene is optional too, which leaves me wondering what:SceneView() means?	Are there ways to provide values for those optionals after the `SceneView` is created?

The documentation is sufficient, it looks like a fairly simple library. What I didn't know was what the word "system" might include .. I see the material, so far, covers the file system and that's a good start! While I'm back here, commenting on this, I'd like to ask if this will become part of Swift's body of open source work? It seems a good candidate, given its subject matter is platform independent.

Years back, when iPhones took time from the phone company, it was not uncommon for AT&T to set time that was up to about two minutes off true time. My satellite tracking app, while not requiring high precision, needed better than that to avoid people hunting on the wrong side of the sky! I wrote a little SNTP library so my app didn't have to rely on clock time.The [S]NTP process relies on, simplifiying, averaging resonses from multiple time-servers. It collects those server names from a pool address (pool.ntp.org, etc) which uses DNS round robin to make a random selection from a pool of time servers that have volunteered to be in the pool, for example:% host pool.ntp.org pool.ntp.org has address 173.255.215.209 pool.ntp.org has address 44.190.6.254 pool.ntp.org has address 74.6.168.73 pool.ntp.org has address 96.8.121.205The client software then fires UDP queries at all the servers, filters out less reliable one and uses the rest averaging their responses in aggregate, and over time. I know, Quinn, that there's nothing new to you in this but I've laid it out for future readers.Some people, and organizations, used my library to get a true time when naughty users were trying to defeat software expiration by setting their device clock back to an earlier date. My library is antiquated (written many years ago) and somewhat redundant (it's my experience that Apple's devices keep sub-second accurate time). Because of the age of my software, and the remaining ability to defeat expiry dates, I started to write an improved version in Swift using the Network framework and tripped over the topic of my original question.I'm amused to re-read my Radar report related to this topic you suggested I submit in 2010 (FB6015112) .. today I'd add to to my CoreTime suggestion the ability to ask the OS for true time, regardless of any fiddling with the system clock setting! Happy Hogmanay ..

Found it!! A sneaky one too .. If you name the project "Watch," it fails .. name it something else, it's OK.Bug reported .. FB7474537