hmm, I have investigated / researched a bit more ... TL:DR ... I guess I will have to go down the "draw my own strokes" ... and create some sort of "Stroke based font file in a PKDrawing file-type format" ... to use for what I want to make. If you are a bit like me, and would like to understand why? ... please open a document in a vector app (I used Affinity Designer...) and type a text ... and Outline it / "Convert it to Curves" ... and analyze what you get (see attached image). Take the letter H in my case ... it's a shape ... that has an outline stroke that goes around in the canvas to make up a shape we understand as the letter H ... it's not "just a stroke" from the middle ... as when we write with our pencil on an iPad or for that matter with a pen on a piece of paper ... After I outlined the text ... I used some help guides to manually draw some strokes with the pen-tool in the middle of the outlined shapes ... and gave these strokes a thickness ... so it looks to the eyes as the font-face letters do. And in the end the blue (bottom) looks like the green (top) ... And in this case, I've chosen a "simple font-face" ... image if I'd gone with a Times New Roman font-face :-)

hmm I even did a total re-install of macOS Monterey Beta 2 (erased the SSD and a fresh install). And yet again, this "Volume Hash Mismatch" is persistent Hmm

So, I did: fsck_apfs /dev/rdisk1s5 From Recovery .... on all Volumes and the disk itself. Back in macOS MR B2 ... Still getting this annoying notification hmm

Is it possible to configure Xcode, so the the lldb always does the "process handle SIGTERM --stop false --pass true"? When launching the app inside Xcode? instead of always having to type in the "process handle SIGTERM --stop false --pass true" everytime (it's getting a bit tedious to re-type this everytime you CMD+R the app, when you are testing that it's handling the signals correctly ....) Would be nice if there was a setting in inside Xcode, that you could configure the lldb with what you want it to do each time.

Also, if you're having issue ... try to re-download the sample code .... I had an issue after updating to Beta 3 and Xcode Beta 3 ... but after I re-downloaded the sample code, it ran. (looks like both the OS and sample code is in development too :-) ...)

yeah, I was wondering about that too ... what other Error codes might we encounter .... and why there isn't an Error list (in the SDK) we can look at when we encounter them? Why haven't you (Apple Developers) added one? ... I have looked though all of the RealityKit SDK ... line by line ... but I haven't seen a "comment section" (that is usually the norm...) with all of the Error codes that one might encounter. (just a bit frustrated that every time one encounters an Error code, one has to "pray to the Apple gods of code" ... and hope they might reply ...)

Thanks! ... Error "-11"? ... I did some more testing, and when I run the sample-code on Monterey Beta 1, I get the error value of "-11". Updated the system to Beta 3 and here I get "-21". Are they the same? ... just that since beta 1 --> beta 3, you have updated the Error codes?

BTW, Would it be possible for you to add all of the potential Error Codes into RealityFoundation API documentation in the next beta release? (green or blue highlight?) ... so we can quickly look-up the issue ourselves? :-)

as @unibodydesignn said, your GPU doesn't meet the minimum requirements... Curious though, are you getting this "-11" error code on Monterey Beta 1, Beta 2 or Beta 3? ... as I too got "-11" on Beta 1 ... though after updating to Beta 3 ... I'm getting a "-21" ... (thinking same issue, just that they updated the Error Codes list between the different Beta's ....) My "-21" issue ... and asking the devs for a complete list of error codes to be added to the API Documentation, so we don't have to ask everytime. https://developer.apple.com/forums/thread/685208?page=1#682368022

ompff ... that's a hard one. From an financial POV ... if you'll earn back your money from buying a MBA M1 now in august (until the next one comes out...) ... go for it. It'll increase your productivity and you'll earn back your investment back by doing so ... ... and if you won't earn your money back in increased productivity (read: the computer doesn't generate any money back to you, and are one of those "I just want the latest thing, even though I don't really need it") ... then don't buy one. Save your money for the next generation apple silicon chip ... time flies ... and you'll do a benefit for the environment too ... (My personal view: I also would like to have a new apple silicon mac ... but I can't really motivate to buy one right now ... since I have a bunch of mac's that I still can be productive with, that I can't really justify to buy another computer. Financially I'm still productive with what I got ... since they aren't that old mac's ... so I can't justify to buy one from an environmental POV either ... I'll wait until it'll make sense to upgrade ...) cheers.

Update: I tried Beta 3 ... and now running Beta 4 .... on my MBA ... and I'm still getting them. I have to say, it's gotten a bit worse ... since Finder and other vital "vital mac apps" crash and they won't re-spawn. And I end up with no apps running (read: showing). Funny when you just have the WindowServer app running and everything else has crashed, and didn't re-spawn. Luckily pressing the PowerButton does pop up the "shutdown window" ... and I can restart my MBA from it (and not force...) BTW: ... something I noticed is I was getting the error when using / having Safari open ... so I'm going to test using Firefox instead .... and try extra not to start any other "Apple apps" (just 3rd party apps) and see ...

@robnotyou The "iCloud Private Relay" is located under: System Preferences --> Apple ID --> iCloud --> iCloud Private Relay And know about it. but this "Limit IP Address Tracking" is located under the Network settings: System Preferences --> Network --> Ethernet --> Limit IP Address Tracking And I haven't seen it previously when I tested some of the macOS 12 Beta's. Don't know when they added this new option under the Network options. And why I'm wondering it's now there :-)

Update 2022-01-12: Filed *this in FBA: FB9842248 Filed a Feature Request with Objective Development (Little Snitch devs...): 1789897 /* I will try to keep this post updated, with any news (if someone is interested) ... */

@HK2LS Go into System Preferences --> Network --> on press "the tiny wheel" (see attached image) --> Set Service Order --> Re-arrange "Ethernet" to be above "Wi-Fi" I had this issue too, where everything was showing that it's connected and working. But I was still getting slow Wi-Fi speeds. Re-arranging the Service Order, helped me. Hope it helps you too.

[Update 2022-01-29] macOS 12.2 seems to have a solution for this problem. I've done a complete clean re-install (with re-formating the entire drive). I've run a 24hr Blackmagic Disk Speed Test, Safari open (the app that most usually made it trigger this issue). Without the issue. Could more people try 12.2 too? and see if it solved their issue?