Is it possible to create and modify procedural meshes yet?

I appreciate the concerns about doing or not doing those practices, but really I just wanted to know if they’re possible. With all due respect, I am careful. Also, the programs I’m referring to are UNIXy and don’t really use system services, so that’s less of a concern. By securely, I meant, I hand a usb drive physically to the person and watch them try my application, or I send via some secure service that isn’t e-mail. The idea is that right now the computer blocks unless I disable “download from anywhere” even if I self-sign. Can you elaborate on what disabling SIP actually does? Am I mistaken that it disables signing restrictions? In any case, regardless of the safety of these practices, can I always go ahead with them in the worst case, or so we simply not know yet when it comes to Apple sillicon? I think you quoted a 2019 wwdc talk here - https://developer.apple.com/forums/thread/117896?answerId=365071022#365071022 suggesting that Apple has committed to letting you re-enable things, but I’m not sure—is this no longer a guarantee? If it makes people more at-ease, I would typically only do something like this with the internet off or with some LAN where I’m not exposing the system to malicious software.

Yes, actually, but I feel that's really complex to do right now, and it looks like there's no code example for sparse textures at all. For example, how would I chunk textures the way the example figure shows it, and how do sparse textures actually work? Are textures partly deleted when not in use? Also, I am using an iPad Pro 2020, which sadly still has an A12 chip instead of an A13 or A14 (I wonder if they'll do yet another refresh soon...) Atlases are more doable, but packing them efficiently is non-trivial. When you say replace regions, do you mean I'd load separate textures and blit those textures to a main atlas? Don't I need a render pass per region bit in case I need to use that memory again for something else? In short, when am I allowed to replace regions of a texture so as not to clobber texture data required in a previous draw call? I actually tried the argument buffer idea and it *seems* to work, but I think that you're correct that texture streaming is closer to what I'd actually want to do.

I third that. I'm building an application right now that would benefit greatly from this example. Please release it!

I realized that iOS is still an umbrella term for iOS + iPadOS support for many APIs in the documentation. That's a little bit confusing.

Has anyone tried with the new M1 iPad Pro 2021s?

By the way, I attended a GroupActivities lab and the engineer seemed surprised the code wasn't up. He indicated that it'd probably go up eventually, but it's unclear whether this was guaranteed.

I've heard from another developer that some other SpeechRecognition apps are no longer working as expected, so this seems to be a bug.

Side-note: how were you able to get it to work in the first place? I am running a localhost python3 server to test and I can't get the page to request access to the microphone in Safari--only in Chrome.

I've confirmed that iOS 14.8 is still just fine on a spare non-upgraded iPad.

Any updates? I haven't received word via the bug report or code-level support request (the latter of which is kind of a waste).

This is still a problem and unexpected behavior. Dictation or Siri need to be on for recognition to work again, seemingly (as @adadas said) , but iOS 14 had no such requirement. There is also no way to really prompt the user to activate this setting programmatically, and it puts undue burden on them when an app should just have its own permissions that the user approves/authorizes.

Xcode 13.1 has been released, but does it actually address this issue at all?

Has anyone filed a bug report?

Is there a way to build to ios 15 and macOS 12 using Xcode 12? I am delaying upgrading due to this. I think the answer is “no,” so I am stranded because my large project is impossible to edit realistically. How can can an issue like this get past v .0?