Just don't put it in the struct. Output directly from the VS. I think that will fix it.

Not for indirect, but for directly setting textures. https://developer.apple.com/documentation/metal/mtlrendercommandencoder/1515842-setvertextexture?language=objc

So can we get a resizable window with iOS on macOS? I'm confused by this statement. Currently we require fullscreen, and only support landscape. But if I turn off UIRequiresFullscreen and state we support all orients, I can get a resizable window. Some elements scale, and other do not. Does that mean that I need to respond to the UIWindowScene scaling, or is the main render always fullscreen size? "When the window is resized, e.g. by using the Window->Zoom menu item, or by taking the window full screen, your fixed-size UIWindowScene is scaled up or down by macOS automatically, and your app does not find out about this."

This is still completely bust in MacOS 12, 13, and 14. Maybe even back as far as 11.0. It's more than just an error message. It breaks using ProMotion in Rosetta apps, and having any chance of reaching 120Hz. CurrentVBLDelta returned 200,000 for display 1 -- ignoring unreasonable value [0x7f85fd07ba20] Bad CurrentVBLDelta for display 1 is zero. defaulting to 60Hz. <- 0 fps is supposed to mean run at maximum refresh, not divide by 0 and compute an invalid vertical blank (f.e. 20000).

This is confusing, since the Metal Feature Set table conveniently leaves A13 off the list of Metal 3 devices. So which is it? A13 has Tier2 argument buffers (indexing), but not barycentrics, RT or mesh shaders, etc.

iPad apps even if you change the size of the Window are just rescaling to the window (still full res). Have to require iOS 13, and jump through some hoops to allow resizing the application window (and not always be full res). But that's iPadOS on macOS, and not iPhone.

This is still bust even in macOS 14.5. The initial return of batteryLevel seems to be fine, but when responding from a notification handler it fails and returns 0. So then our app displays the low battery indicator. I'm running iOS on macOS with an M2 Max. Error retrieving battery status: result=-536870207 percent=-2093318143 hasExternalConnected=1 isCharging=5 isFullyCharged=184 p [[UIDevice currentDevice] batteryLevel] (float) 0

CVDisplayLink, which is already part of CoreVideo, is used by every macOS app. CADisplayLink is iOS. CAMetalDisplayLink is the compositor for Metal apps to avoid needing MTKView, but has a high iOS/macOS requirement. So I would assume CVDisplayLink isn't going away anytime soon unless Apple plans to break every app out there. 0 is a valid setting for the fps, and doesn't mean Apple computes 1/0 and gets some randomly large integer number, and then clamp the 120Hz display to 60Hz. 0 is meant to indicate "run at highest framerate of the monitor". This only happens for apps compiled for x64 and run under Rosetta, and not if recompiled for arm64. macOS x64 runs the x64 app at 120Hz too. This has to also clamp any games using GPTK too.

Also macOS27 drops Intel and not Rosetta. Rosetta may be dropped in macOS28. So still have 2 years to run x64 code. And even after that Valve will have FEX and games still being emulated.