Delve into the world of graphics and game development. Discuss creating stunning visuals, optimizing game mechanics, and share resources for game developers.

All subtopics
Posts under Graphics & Games topic

Post

Replies

Boosts

Views

Activity

Adding achievements to an existing product
We have an existing product on the appstoreconnect. It uses Game center to handle achievements. The game has been out for a few years but we're planning on adding some new achievements for an up coming expansion. We have a privacy concern, we do not want players to see our new achievements until the game has released, but we still need to test them Reading through the docs, we inferred that the right way to handle this is to create new achievements through appstoreconnect -> game center, but do not push them for review yet. We have created 10+ new achievements. Using a tester account, we built a debug tool to simply unlock the achievements with a click, and we got the following error No AchievementDescription could be found for Achievement with ID: <ACHIEVEMENT_ID>This message only comes up once and only for achievements we actually have created in the backend, not just any ol' string we feed it. We're a little stumped about what else to do. Have we missed something? Is this an outage issue? Any help would be appricated. Thank you!
0
0
119
20h
WebGL linkProgram fails for every program in a Mac Catalyst WKWebView on macOS 27.3 beta
On macOS 27.3 beta (26C5035r), WebGL draws nothing in a WKWebView in a Mac Catalyst app. A WebGL2 context is created and shaders pass COMPILE_STATUS, but linkProgram fails for every program, with LINK_STATUS false and an empty program log. The same source file draws when built for My Mac. The same page also draws in Safari 27.3 and in the iOS 27.0 Simulator. Only the Mac Catalyst build fails. To reproduce, run a trivial vertex and fragment shader pair in a WKWebView, built for My Mac (Mac Catalyst): LINK_STATUS: false program log: "" pixel: 0, 0, 0, 0 getError: 1282 The unified log for the Catalyst app's com.apple.WebKit.GPU process shows this for each shader: (Metal) Metal Compiling Shader (Metal) Compiler failed to build request MTLCompilerService logs "Compilation BEGIN" for each request, then no "Compilation SUCCESS". The Metal source from WEBGL_debug_shaders is byte-identical in the Mac and Catalyst views, and with ANGLE's link placeholders filled in by hand it compiles in a Catalyst process, so the failure seems specific to the Catalyst GPU process. Signing, app sandbox, hardened runtime and a new bundle identifier make no difference. A macOS bundle loaded into the Catalyst process does not help, because its WKWebView is the Catalyst one. Sketchy Workaround: run the page in an AppKit WKWebView in a separate macOS helper process. FB25444425
1
1
231
1d
Public API for user-authorized interaction with a button in another iOS app?
Goal I am building an iPhone app for a user who has explicitly authorized it. A third-party app on the same device shows a list item with a "Details" button. The content I need is only displayed after that button is pressed. I want my app, in the user's own session and with their consent, to press that button so the detail screen appears. Constraints Stock iOS 26 or later, no jailbreak, no Mac or other computer attached during daily use, App Store distribution. What I have looked at XCUITest and WebDriverAgent need a host computer. Switch Control, Voice Control, and AssistiveTouch appear to be user-enabled system features. I could not find a public API that lets a third-party app trigger them. Shortcuts has no action that taps inside another app. App Intents works only when the other app exposes its own intents. Questions Is there any public, App Store-compatible API on iOS that lets an app, with user authorization, press a button inside another app? If not, is that an intentional platform boundary? Is there any other supported technical architecture for this use case, other than relying on the other app's own App Intents? Thank you.
1
0
234
1d
Game Center overlay places its back and Play buttons under the rounded corners (and camera) on iPhone Duo's outer display
Environment Device: iPhone Duo, closed (outer display), iOS 27.2 Xcode 27.1 (27A9275), iOS 27.1 SDK, deployment target iOS 18 SwiftUI app lifecycle (WindowGroup, generated scene manifest, generated UILaunchScreen), not letterboxed What happens On the iPhone Duo's outer display, the Game Center screens that GKAccessPoint.trigger(...) opens put their top controls (the round back button at the top left, the "Play" button at the top right) right up in the display's rounded top corners, where the corner partly clips them. The same screens look correct on other iPhones. The outer display's status sits in a column at the right, so a full-screen window there gets a top safe area inset of 0. On other iPhones the top inset (status bar or Dynamic Island) keeps these buttons clear of the corners. The overlay appears to rely on that inset and has no margin of its own for the display's corner radius. Our own app content on the same display handles this: when the top safe area is 0 we add a fixed top margin. The Game Center overlay has no API for us to do the same, at least none that we can find. Steps to reproduce Sign in to Game Center on an iPhone Duo and keep it closed (outer display). In any app, call GKAccessPoint.shared.trigger(leaderboardID: "<id>", playerScope: .global, timeScope: .allTime, handler: {}) Look at the top corners of the Game Center screen, on the leaderboards list and on a single leaderboard. Expected: the back and Play buttons sit clear of the rounded corners, as on other iPhones. Actual: they sit under the corners (screenshot, though it doesn't show the camera cutout) What we tried (none changed the layout at all) Binding the access point to our window before every trigger: let scene = UIApplication.shared.connectedScenes.compactMap { $0 as? UIWindowScene } .first { $0.activationState == .foregroundActive } if let window = scene?.keyWindow { GKAccessPoint.shared.parentWindow = window } GKAccessPoint.shared.trigger(leaderboardID: id, playerScope: .global, timeScope: .allTime, handler: {}) Hosting GKGameCenterViewController (deprecated in iOS 26, used only for this test) as a child of our own full-screen view controller, with a top safe area margin: final class GameCenterHolder: UIViewController, GKGameCenterControllerDelegate { let screen: GKGameCenterViewController // GKGameCenterViewController(leaderboardID:playerScope:timeScope:) // init sets modalPresentationStyle = .fullScreen override func viewDidLoad() { super.viewDidLoad() screen.gameCenterDelegate = self addChild(screen); view.addSubview(screen.view); screen.didMove(toParent: self) } override func viewSafeAreaInsetsDidChange() { super.viewSafeAreaInsetsDidChange() screen.additionalSafeAreaInsets.top = view.safeAreaInsets.top < 1 ? 20 : 0 } nonisolated func gameCenterViewControllerDidFinish(_ vc: GKGameCenterViewController) { MainActor.assumeIsolated { dismiss(animated: true) } } }The screen opened and worked, but its layout was identical. The same holder, giving the child a smaller frame instead (starting 20 pt lower): override func viewDidLayoutSubviews() { super.viewDidLayoutSubviews() let top: CGFloat = view.safeAreaInsets.top < 1 ? 20 : 0 screen.view.frame = view.bounds.inset(by: UIEdgeInsets(top: top, left: 0, bottom: 0, right: 0)) }Still identical, so the screen seems to be drawn by the system outside the app's view hierarchy, out of the app's reach. We also checked the usual causes: the app is built with the iOS 27.1 SDK, uses the scene lifecycle and a generated launch screen, doesn't use UIScreen.main for layout, and fills the outer display edge to edge (not letterboxed).
0
0
101
2d
Metal 4: MTL4Compiler crashes when many threads capture binaries into one MTL4PipelineDataSetSerializer
Hey all, hoping someone on the Metal team can take a look at this one. It's a crash inside Metal 4's binary capture, and as far as I can tell there's no way to fix it from the app side. Filed as FB25478288 (partial repro is link is there too). Why I think it matters The setup that crashes is basically the recommended Metal 4 workflow: one MTL4Compiler with a MTL4PipelineDataSetSerializer (CaptureBinaries) attached, called from maximumConcurrentCompilationTaskCount threads, to harvest pipelines for an offline archive. Lots of pipelines share a vertex function, which I'd guess is true for most real renderers. The crash is 100% inside Metal.framework, with no app code on the crashing thread. It's easy to hit: 3 out of 3 harvest runs crashed for us, one of them 2 s in. The serializer is attached to the compiler implicitly, so the app can't put a lock around whatever it does internally. MTL4Compiler is Sendable, and the docs say it handles multithreading by default, so I'd expect capture to be thread-safe too. Environment MacBook Pro M2 Max, macOS 27.2, Xcode 27.2, Metal toolchain 32023.922.4 Also reported on an M3 Pro ~33k render pipelines over ~16k vertex functions, up to ~1,000 pipelines in a row sharing one vertex function MTL4RenderPipelineDescriptor with MTL4LibraryFunctionDescriptor stages (sometimes wrapped in MTL4SpecializedFunctionDescriptor), all colour attachments Unspecialized The serializer gets written out with serializeAsArchiveAndFlushToURL: every so often, then we start a fresh compiler + serializer Crash EXC_BAD_ACCESS (SIGSEGV), "possible pointer authentication failure": objc_msgSend MultiLevelAirntBinaryCache::getElementAtDestination(MTLBinaryKey*, ...) -[MTLCompiler compileFunctionRequestInternal:frameworkLinking:linkDataSize:reflectionOnly:compilerTask:completionHandler:] ... AGX::Compiler::compileProgram<AGX::VertexProgramKey, ...>It looks like a use-after-free: two compiles capturing the same vertex program at the same time, and an entry in the destination archive gets freed while the other one is still using it. It only happens with capture on, and it goes away if we never let two capture compiles that share a stage function run at once. Workaround we ship (not great) A lock per stage function around each capture compile, plus sending runs of pipelines that share a vertex shader to the same thread. That stopped the crashes, but we had to put a timeout on the lock, because the compiler occasionally never returns, so in theory it can still race. Second, related crash If serializeAsArchiveAndFlushToURL: runs while other threads are still compiling into that serializer, we get a different crash (null deref at 0x30) in dispatch_data_create_map ← -[_MTLBinaryArchive newArchiverIdWithBinaryKey:entry:srcArchiverId:functionType:]. Our standalone repro hits this one reliably. The getElementAtDestination crash only shows up with our real workload so far. Repro + details https://github.com/Aeonitis/metal4-capture-race It's a small Objective-C repro (Metal + Foundation only) with a bunch of modes, the results so far, and a comparison with how Vulkan (VkPipelineCache) and D3D12 spell out the thread-safety rules for this same pattern. Questions Is capturing from multiple threads into one MTL4PipelineDataSetSerializer meant to be supported? If not, could the docs say so? Is one compiler + one serializer per thread a safe workaround, or is there shared state between compilers in the same process that would still race? Is calling serializeAsArchiveAndFlushToURL: while compiles are still in flight on that serializer allowed? Is this already fixed in a seed
1
0
509
2d
M5 Pro external 5K 165Hz display: Window animations and scrolling UI appear to render at ~60Hz/jitter while cursor remains perfectly smooth
Hello Apple engineers, I’m trying to determine whether what I’m seeing is expected behavior or a software issue with the new M5 Pro platform. System MacBook Pro (M5 Pro) Latest macOS Beta External 5K 165Hz monitor connected via DisplayPort Refresh rate correctly detected as 165Hz What I observe The display itself is clearly running at 165Hz. For example: Mouse cursor movement is extremely smooth. Dragging the desktop by holding an empty area is also perfectly smooth. However: Moving application windows feels much closer to 60Hz. Scrolling in Safari, Chrome and other applications also appears to run at a much lower frame rate than the display refresh rate. Mission Control animations sometimes show similar micro-stutters. This makes the cursor and desktop movement noticeably smoother than normal window animations. ⸻ Troubleshooting already performed Different DisplayPort cables Different timing configurations Different resolutions / HiDPI modes DSC enabled and disabled Refresh rate confirmed at 165Hz Same behavior across multiple applications The issue appears unrelated to the monitor itself because the cursor is clearly rendered at the full refresh rate. ⸻ Additional observation Interestingly, I previously used another external 4K 144Hz HDR monitor and did not notice this behavior. I also found another M5 Pro user reporting nearly the same issue: external 165Hz display smooth cursor window dragging jitter / micro-stuttering At the same time, I haven’t found similar reports from M4 Pro or the base M5 running the same monitor. ⸻ My question Could this be related to the new M5 Pro display pipeline (WindowServer, Display Engine, or DCP)? Is there any known issue regarding high-refresh-rate external displays on the M5 Pro platform? Or is there additional diagnostic logging (WindowServer, DCP, Metal, etc.) that would help identify whether frames are actually being presented at the display refresh rate? I’d be happy to provide: sysdiagnose WindowServer logs Screen recordings Display timing information IORegistry dumps if they would be helpful. Thank you!
8
1
2.6k
4d
M5 Pro WindowServer/Display Engine: Window animations and UI scrolling capped at ~60Hz on external 5K 165Hz display while hardware cursor remains smooth
On the new M5 Pro platform running macOS, UI animations (window dragging, Safari/Chrome scrolling, Mission Control) on an external 5K 165Hz display appear to render at a much lower frame rate (~60Hz) or exhibit severe micro-stuttering. However, the mouse cursor and desktop wallpaper dragging remain perfectly fluid at 165Hz, indicating a potential issue in the WindowServer compositor or display pipeline rather than the physical link. Environment • Hardware: MacBook Pro (M5 Pro) • OS: macOS 27.0 beta 3 (26A5378j) • External Display: 5K 165Hz monitor connected via DisplayPort (DSC confirmed via IORegistry). System Settings correctly detects and selects 165Hz. Expected Behavior All UI elements, including window movement, application scrolling, and system animations, should render smoothly at the native 165Hz refresh rate matching the hardware capabilities. Actual Behavior The display output appears split between two different refresh rates: 1. Full 165Hz: The hardware mouse cursor and desktop dragging (empty area selection) are perfectly smooth. 2. ~60Hz / Jitter: Application windows (Finder, Safari, Chrome) stutter heavily when dragged or scrolled. Mission Control animations suffer from micro-stutters. Note: This specific combination suggests the Hardware Cursor layer is running at full rate, but the WindowServer compositor layer is throttled or dropping frames. Troubleshooting Performed (No Change) • Verified with multiple certified DisplayPort cables. • Tested across various resolutions (Scaled/HiDPI modes) and toggling DSC. • Regression Check: This issue did not occur on a 4K 144Hz HDR monitor previously, and initial community feedback shows other M5 Pro users experiencing this specific 165Hz window-dragging jitter, while M4 Pro / base M5 users on the same macOS beta do not seem impacted. Questions & Diagnostics 1. Is this a known regression related to the new M5 Pro display engine / Display Coprocessor (DCP) pipeline handling 5K high-refresh-rate timings? 2. Are there specific defaults write commands, Quartz Debug profiles, or custom logging arguments (WindowServer, DCP, or Metal) we can enable to capture frame presentation metrics? I have captured a sysdiagnose, IORegistry dump, and high-frame-rate screen recordings, and am ready to attach them as soon as this feedback is processed. Case / Feedback Reference Feedback ID: FB23616959 (Captured after the system format)
1
1
851
5d
Doc bug? Any reason to use Metal's wantsExtendedDynamicRangeContent instead of CALayer preferredDynamicRange?
Should CAMetalLayer wantsExtendedDynamicRangeContent be considered deprecated? Some links for context: CAMetalLayer wantsExtendedDynamicRangeContent for iOS 16+ CALayer wantsExtendedDynamicRangeContent for iOS 17+ CALayer preferredDynamicRange for iOS 26+ So Metal got it, then CALayer got it, then CALayer got a more extensible one in iOS26 and wantsExtendedDynamicRangeContent got marked Deprecated. But it's not marked as deprecated on the CAMetalLayer. I tested it and setting preferredDynamicRange on the CALayer worked to allow my CAMetalLayer to show HDR content on both iOS 27 and tvOS 27. I don't know if there's some reason though (performance for example?) to prefer setting the property on the CAMetalLayer rather than the CALayer. I'm asking because I want react-native-webgpu to support HDR on tvOS, but right now they're using CAMetalLayer wantsExtendedDynamicRangeContent which has no tvOS support. https://github.com/wcandillon/react-native-webgpu/pull/607
1
0
463
5d
Total triangle budget for a one skinned character app, iOS 26 and later
Hello, I’m working on an iOS app built around a single skinned character with fur, rendered in Metal and shown in close-up, so it takes up most of the screen. It needs to run at a steady 60fps, and the oldest hardware I want to support is the A15 (iPhone 13). The fur will be alpha cards layered over the base mesh. All of the character’s motion is computed on the GPU each frame, and ARKit and Vision hand tracking are running at the same time. This is what I have so far. A 180k-triangle test character with no hair cards runs smoothly in the Simulator on my Mac (yes, I know it's not entirely representative of the GPU numbers on a phone). On an actual iPhone 16, a synthetic bench (60k vertices, 4 influences each) put GPU skinning at 1.1 to 1.3 ms whether I used 250 joints or 1000, so I’m not worried about skinning. The final model is still being built, so I can’t test the real thing yet, but I have to give the modeler a budget now. I’m thinking of 100k to 120k triangles in total, base mesh plus alpha cards. Would that look fairly reasonable for an A15, or not? Thanks!
2
0
310
6d
CIRAWFilter.supportedCameraModels(with: .version9) does not include camera models that appear to be supported
CIRAWFilter.supportedCameraModels(with: .version9) does not include some camera models that appear to be supported. For example a Sony A1 or Nikon Z8 RAW file opened using CIRAWFilter and then calling filter.supportedDecoderVersions.contains(.version9) return true but these models are not included in the supportedCameraModels list. Why is the supportedCameraModels(with:) not all the supported camera models ?
1
0
226
6d
Is Metal 4.1 `interleave` available on M4 Pro? Pipeline creation fails with "unlowered function call"
The Metal Shading Language Specification 4.1, section 6.4, lists interleave and deinterleave as "All OS: Metal 4.1 and later", with no GPU family restriction. The Metal Feature Set Tables list the M4 series as Apple9 and have no row for interleave. On an M4 Pro, a kernel that calls interleave compiles, but creating its compute pipeline fails. Which GPUs and macOS versions support interleave and deinterleave, and is the M4 family expected to? import Metal let src = """ #include <metal_stdlib> kernel void k(device const metal::uchar2 *a [[buffer(0)]], device metal::ushort *b [[buffer(1)]], uint i [[thread_position_in_grid]]) { b[i] = metal::interleave(a[i]); } """ let device = MTLCreateSystemDefaultDevice()! let options = MTLCompileOptions() options.languageVersion = .version4_1 let function = try! device.makeLibrary(source: src, options: options).makeFunction(name: "k")! do { _ = try device.makeComputePipelineState(function: function) print(device.name, "| pipeline created") } catch { print(device.name, "| pipeline failed:", error.localizedDescription) }The library compiles, but creating the pipeline fails. ushort2/uint, uint2/ulong and deinterleave fail the same way. Apple M4 Pro | pipeline failed: Encountered unlowered function call to air.interleave.i16. Verify device or GPU architecture supports this featureIf I replace the kernel line b[i] = metal::interleave(a[i]); with b[i] = metal::ushort(a[i].x) | (metal::ushort(a[i].y) << 8);, it prints Apple M4 Pro | pipeline created. Configuration Apple M4 Pro, macOS 27.2.1 (26B131), Xcode 27.1 (27A9275), Swift 6.4, metal 32023.921. Software Update shows nothing newer.
1
0
163
1w
CGSetDisplayTransferByTable is broken on macOS Tahoe 26.4 RC (and 26.3.1) with MacBook M5 Pro, Max and Neo
The CGSetDisplayTransferByTable() is not working on the latest round of Mac hardware, namely the MacBook Neo (external display), MacBook M5 Pro (both built-in and external display) and possibly the M5 Max. All tested apps (BetterDisplay, MonitorControl, f.lux, Lunar) exhibit the very issue both in macOS Tahoe 26.3 and macOS Tahoe 26.4 RC. Tested on multiple Macs and installations on the MacBook Neo and MacBook M5 Pro. This issue breaks several display related macOS apps. Way to reproduce the issue using an affected app: Install the app BetterDisplay (https://betterdisplay.pro) Launch the app, open the app menu, choose Image Adjustments and try to adjust colors. Adjustments take no effect Way to reproduce the issue programmatically: Attempt to use the affected macOS API feature: https://developer.apple.com/documentation/coregraphics/cgsetdisplaytransferbytable(::::_:) Here are the FB numbers: FB22273730 (Filed this one as a developer on an unaffected MBP M3 Max) FB22273782 (Filed from an affected MBP M5 Pro running 26.4 RC, with debug info attached)
19
7
8.7k
1w
A small scrolling ticker pins GPU at ~50% on a rich screen but ~0% on a blank one — is whole-tree compositing at the animation's rate the expected cost?
I have a SwiftUI clock-radio app on iPhone (ProMotion display). The face is a rich, layered screen (glass panels, gradients, shadows). One element is a 340×46 pt text ticker strip that scrolls continuously. Its GPU behaviour is reproducible and, to me, surprising: Measurements (Xcode GPU gauge used only for within-session relative contrasts; cadence from an in-app frame-pacing log): With the ticker scrolling, GPU sits at a ~50% plateau. The step is binary: one scroller or three scrollers cost the same. Frames are never dropped: 16.7 ms median frame time, ~3% of frames over 20 ms. The GPU bills heavily for frames it renders on time. The same strip scrolling on an otherwise blank screen costs ~0%. The ticker visible but static costs 0%. Motion is the trigger; the cost scales with what surrounds the strip, not with the strip itself. What I have tried: SwiftUI offset animation of the text — baseline behaviour above. A fully severed Canvas leaf: own layer subtree, own CADisplayLink, snapshot-fed, no view-tree publishing or subscriptions — identical cost on the full face (and literally 0% redrawing alone on a blank screen at full frame rate). Pre-rendered bitmap content scrolled instead of text — identical. The strip hosted in a separate UIWindow above the face — identical, measured with the strip visibly scrolling in its seat. Pinning the strip's CADisplayLink.preferredFrameRateRange to exactly 30 Hz (minimum = maximum = preferred = 30) — no change. .compositingGroup() on the panel subtree — a modest reduction only. What works: removing the motion duty (scroll once, then park — cost collapses), and, elsewhere in the app, a pull-model spectrum visualiser replaced a publish-driven one and its cost vanished. Severing worked for the visualiser but not for the ticker. Questions: Is this step the expected consequence of the WWDC22 session 10083 rule (the display refresh rate is set by the highest-frame-rate animation in the app) composed with whole-layer-tree compositing per presented frame? Is there any dirty-region scoping that a layer structure like ours defeats? The 30 Hz pin above was hard (min = max = preferred). Would a CAFrameRateRange in the 15–24 Hz band that Apple's ProMotion guidance suggests for small, slow animations behave materially differently, or is that distinction already settled by the 30 Hz result? Is there a known construction for a continuously scrolling ticker that lets the GPU idle between updates? Happy to share a minimal repro or the pacing logs if useful.
2
0
543
1w
Distributing D3DMetal with a Mac App Store app
Hello, We develop a Mac App Store app that runs Windows on Apple silicon. We use D3DMetal from the Game Porting Toolkit so that DirectX 12 games and apps can run in it. Today, each user has to download the Game Porting Toolkit, open the "Evaluation environment" disk image and point our app to D3DMetal.framework. Many users find this confusing, and we would like to make DirectX 12 work out of the box. When we tried to bundle D3DMetal.framework in our app, App Store Connect rejected the upload: ▎ Invalid Bundle. The application bundle may not contain tools or frameworks provided by Apple, or using bundle identifiers in the 'com.apple.' namespace. Invalid bundle: D3DMetal … with bundle identifier 'com.apple.D3DMetal'. We also note that the Game Porting Toolkit licence limits distribution to non-commercial purposes. Our questions: Is there an approved way for a Mac App Store app to include or distribute D3DMetal, for example a commercial redistribution agreement or a separate licence? If not, is there a supported way for an App Store app to obtain D3DMetal on the user's Mac, such as an Apple-provided download or a system component it can use? Are there plans to make D3DMetal available to third-party apps, as a public framework or as part of macOS? We want to follow Apple's licence and App Store guidelines, so any guidance on the correct approach would be much appreciated. Thank you.
0
0
229
1w
Request for PROLED display to support Adaptive Sync (VRR)
I was hoping with an OLED display that the new MBP might support true Adaptive Sync aka VRR. Alas, it only gets ProMotion, with the same huge gap between supported refresh rates at the top end (60hz and 120hz). Hooking up an HDMI VRR display such as any LG TV results in a display that works much better with variable framerates than the built-in display, since you can deliver frames at any interval between the min and max. VRR greatly improves games and already works great in macOS with an external display, so I humbly request that Apple consider another option next to ProMotion, for Adaptive Sync/VRR.
0
0
234
1w
Game Center Player Identity Continuity After App Transfer Between Developer Accounts
Dear Apple Developer Support Team, We plan to transfer multiple non-Apple Arcade games from Developer Account A to Developer Account B. The transfers have not yet been initiated. Approximately one million existing players use Game Center to sign in and link their identities to our in-game accounts. Before initiating the transfers, we need to clarify how player identities will be preserved. If internal implementation details cannot be disclosed, please describe the observable behavior from our apps and backend servers. We would appreciate direct confirmation or correction of the following statements. Background We use Game Center authentication signatures to verify player identities and associate Game Center IDs with our own account system, following Apple’s requirement: “Trust only the fields in the signed payload.” Our existing records contain legacy playerID (deprecated API) and teamPlayerID, but not gamePlayerID. Apple documentation states that the current authentication signature payload for non-Arcade games contains teamPlayerID, bundleID, timestamp, and salt, but not gamePlayerID. Therefore, even if gamePlayerID remains unchanged after the transfer, we cannot independently verify its authenticity. After the transfer, there will be three player categories: Existing installations that are not updated, continuing to use versions signed by Account A. New installations downloaded from the App Store after the transfer, still using versions signed by Account A. Players who update to new versions released under Account B. Questions 1. legacy playerID: Status and Availability (A) Is playerID globally scoped rather than tied to a developer account (Team ID)? Does transferring an app leave existing players’ playerID values unchanged? (B) Does Apple provide any way to map historically stored legacy playerID values to the corresponding gamePlayerID or teamPlayerID? (C) Although the playerID API is deprecated, will Apple stop returning this value in a future iOS version, or under any specific conditions? 2. What Determines teamPlayerID? Please confirm which model applies, or explain the actual mechanism: (A) teamPlayerID is determined by the app’s current developer account (Team ID), meaning all players’ values change immediately when the transfer takes effect, regardless of app version. (B) teamPlayerID is determined by the account that signed the installed app, meaning values change individually when players update to a version signed by Account B. For the three player categories above, which account’s teamPlayerID will Game Center return? Specifically: Will categories (1) and (2) receive the same value? Are there differences between app updates, fresh installations, and uninstalling and reinstalling? 3. Can Older Versions Signed by Account A Still Be Verified? (A) Can older versions in categories (1) and (2) still authenticate with Game Center and generate valid signatures that our backend can verify? (B) Will Apple stop issuing authentication signatures for versions signed by Account A? If so, under what conditions or after what period? 4. How Can Players Be Reliably Reassociated with Their Original Game Accounts? If teamPlayerID changes after the transfer, while gamePlayerID remains unchanged but is absent from the signed payload: (A) Does Apple provide an official mechanism to prove that a post-transfer player identifier belongs to the same Game Center account as a previously stored identifier? (B) If not, how does Apple recommend that non-Arcade games securely verify that returning players are the legitimate owners of their original game accounts after an account transfer? (C) If Apple recommends using gamePlayerID, please clarify: Is accepting a client-reported gamePlayerID, which is not included in the signed payload, an Apple-approved practice for non-Arcade games? Since an attacker could submit another player’s gamePlayerID to hijack their account, what protection does Apple recommend against such impersonation? 5. Required Actions and Timing for Developers and Players (A) What actions should Accounts A and B take at each stage of the transfer? Does Apple provide migration credentials, identifier mapping exports, or other migration mechanisms? (B) Must players sign in or update the app before the transfer takes effect? What happens to those who do not? (C) If players must act within a specific time window, how should we handle those who do not launch the game during that period and only return months or years later? How can their original accounts and game data be preserved? 6. Can We Verify These Behaviors Before the Transfer? (A) Can Game Center Sandbox or TestFlight environments reproduce identifier changes before and after an app transfer between developer accounts? (B) If not, can we transfer a test app between our two developer accounts to verify the actual behavior? Are there any restrictions? (C) If neither approach is possible, what does Apple recommend for verifying these behaviors before the actual transfer? ⸻ This transfer affects the continuity of approximately one million existing player accounts. We would therefore like to obtain clarification before submitting the transfer requests. If these questions are outside the current support team’s scope, please escalate this inquiry to the Game Center engineering team. Thank you for your assistance. Best regards !
0
0
63
1w
PDFKit Page Rerender
I'm experiencing an issue with PDFKit where page.removeAnnotation(annotation) successfully removes the annotation from the page's data structure, but the PDFView no longer updates automatically to reflect the change visually. Issue Details: The annotation is removed (verified by checking page.annotations.count) The PDFView display doesn't refresh to show the removal This code was working correctly before and suddenly stopped working No code changes were made on my end
5
3
1.9k
1w
Request for higher hardware encoding resolution/performance on the future Mac desktop/laptop platforms for VR support.
Request: Mac media-engine headroom for 3840-per-eye stereo encoding to Apple Vision Pro We develop a Mac app that streams OpenXR VR applications, rendered on the Mac's GPU, to Apple Vision Pro as stereo video. The Mac encodes with VideoToolbox, as MV-HEVC (one layer per eye) or side-by-side HEVC. Vision Pro decodes the stream and presents it in an immersive space. We'd like to ask for future Mac hardware to support stereo encoding at Vision Pro-class resolution: 3840 pixels per eye at 90 fps. Why resolution matters without eye tracking Vision Pro does not give applications eye-tracking data. We understand and respect the privacy reasons. It does mean a streaming app can not use gaze-driven foveated encoding, which sends full detail where the wearer is looking and less elsewhere. Streaming solutions on other headsets use that to stay within their encoder budget. Without gaze data, every part of each eye's image has to be sent at full detail, so the only route to a sharper image is encoding more pixels. Today the encoder is where that stops. What we measured (tested on an M4 Max) M4 Max, macOS 27.0.1, hardware HEVC through VideoToolbox, synthetic frames at 200 Mbps, no frame reordering, RealTime off, speed prioritised, frames submitted at 90 Hz with at most 4 in flight, eye heights at 20:19. Results are frames per second, with median encode latency in brackets. MV-HEVC: 2048×1952 per eye: 90 fps (16 ms) 2240×2128 per eye: 90 fps (19 ms), the largest size that holds 90 2304×2192 per eye: 87 fps (46 ms) 3072×2928 per eye: 50 fps (79 ms) 3840×3648 per eye: 33 fps (121 ms) Side-by-side HEVC: 2048×1952 per eye: 90 fps (12 ms) 3072×2928 per eye: 90 fps (25 ms) 3200×3040 per eye: 90 fps (27 ms), the largest size that holds 90 3328×3168 per eye: 86 fps (46 ms) 3840×3648 per eye: 65 fps (61 ms) What the numbers show: One MV-HEVC session uses one media engine (about 0.92 Gpx/s at every size). The second engine sits idle: two MV-HEVC sessions at 3840 per eye run at the same time at 33 fps each. One single-layer HEVC session spreads across both engines (about 1.82 Gpx/s), but only while nothing else is encoding. With a second session open (we used a 1080p30 desktop share), it drops to one engine: 3072 per eye falls from 90 to 52 fps, and 3840 per eye from 65 to 33 fps. GPU load does not slow the media engine. We repeated the tests beside a synthetic GPU load using 7 to 9.6 ms of every 11.1 ms frame, as a VR title would, and every result was unchanged. The encoding window we actually have At 90 Hz a frame lasts 11.1 ms, and the VR application uses most of that rendering on the GPU. Rendering and encoding run in sequence for each frame, so every millisecond of encoding adds directly to the wearer's motion-to-photon latency, on top of the app's own frame. In practice we need two things from the encoder: Latency: finish each frame within about one frame period (around 11 ms), so the stream adds no more than one frame beyond the app. Today 2048 per eye MV-HEVC takes 16 ms, or about 1.5 frames. Headroom: run at no more than about 75 % of capacity. Real scenes vary in complexity, and near the limit latency climbs steeply (side-by-side HEVC goes from 27 ms at 3200 per eye to 46 ms at 3328 per eye). At 75 % load an M4 Max supports about 2000 per eye for MV-HEVC, which is the 2048 we ship today, and about 2800 per eye for side-by-side HEVC when no other session is running. 3840×3648 per eye at 90 fps is 2.52 Gpx/s. With the 25 % headroom, that is about 3.4 Gpx/s of sustained encode capacity: roughly 1.9× both M4 Max engines together, or 3.7× the single engine an MV-HEVC session gets today. For comparison, our Windows host encodes MV-HEVC at 3840×3648 per eye at 90 fps on a current desktop NVIDIA GPU, in about 11 ms per frame, by splitting the work across its encoder engines. Vision Pro decodes and presents that stream at 90 fps, so the headset handles this resolution. The gap is on the Mac's encoding side. What we don't know yet We do not yet know whether the Mac GPU can render VR titles at 3840 per eye at 90 fps; that will depend on the title. We can not usefully find out while the encoder limits us first, so in practice we ship MV-HEVC/HEVC at 2048 per eye by default. What we're asking for About 3.4 Gpx/s of HEVC / MV-HEVC encode capacity in future Mac media engines, enough for 3840×3648 per eye at 90 fps with headroom, plus room for a smaller second session such as a desktop share. MV-HEVC/HEVC sessions that can use more than one media engine on chips that have them. On current chips this alone would roughly double the stereo ceiling. A single-layer HEVC session that keeps its multi-engine split while another session is running, or a property to request that. If the platform can offer it, a privacy-preserving foveation path for streaming apps, where the system supplies a foveation region to the encoder without the app ever seeing raw gaze. If a VideoToolbox configuration already lets one MV-HEVC/HEVC session use both engines, we'd be glad to hear about it. We're happy to file a Feedback report with our test tool attached.
0
0
227
1w
Damage numbers on 100s of enemies - performance question
Hello guys, i hope someone can help with that *i already have particle system working for hit feedback on enemies, and i manage to maintain the FPS quite good while using a pre-wamred pool of emitters and a cleanup system that cycle thru that pool. So i do have some basic experience with the particle system and the ECS system. For the spawning of damage numbers of enemies, I try to find a way to show damage numbers on enemies while keeping performence . 100s of enemies might get hit at a single frame, In unreal i used niagara Particles with UV pooling, with mass. object pooling the numbers with the GPU itself fed by the cpu mass ECS. What is the best way to do that in reality kit ? System is very high level, im not sure what is the best approach to begin with to keep good FPS. even if i need to use AI to write some custom shader, i still need help to design the overall system (should i put the logic inside an ECS system with a dedicated emitter with a custom metal shader for the particles?) Thank you guys
1
0
866
1w
Adding achievements to an existing product
We have an existing product on the appstoreconnect. It uses Game center to handle achievements. The game has been out for a few years but we're planning on adding some new achievements for an up coming expansion. We have a privacy concern, we do not want players to see our new achievements until the game has released, but we still need to test them Reading through the docs, we inferred that the right way to handle this is to create new achievements through appstoreconnect -> game center, but do not push them for review yet. We have created 10+ new achievements. Using a tester account, we built a debug tool to simply unlock the achievements with a click, and we got the following error No AchievementDescription could be found for Achievement with ID: <ACHIEVEMENT_ID>This message only comes up once and only for achievements we actually have created in the backend, not just any ol' string we feed it. We're a little stumped about what else to do. Have we missed something? Is this an outage issue? Any help would be appricated. Thank you!
Replies
0
Boosts
0
Views
119
Activity
20h
WebGL linkProgram fails for every program in a Mac Catalyst WKWebView on macOS 27.3 beta
On macOS 27.3 beta (26C5035r), WebGL draws nothing in a WKWebView in a Mac Catalyst app. A WebGL2 context is created and shaders pass COMPILE_STATUS, but linkProgram fails for every program, with LINK_STATUS false and an empty program log. The same source file draws when built for My Mac. The same page also draws in Safari 27.3 and in the iOS 27.0 Simulator. Only the Mac Catalyst build fails. To reproduce, run a trivial vertex and fragment shader pair in a WKWebView, built for My Mac (Mac Catalyst): LINK_STATUS: false program log: "" pixel: 0, 0, 0, 0 getError: 1282 The unified log for the Catalyst app's com.apple.WebKit.GPU process shows this for each shader: (Metal) Metal Compiling Shader (Metal) Compiler failed to build request MTLCompilerService logs "Compilation BEGIN" for each request, then no "Compilation SUCCESS". The Metal source from WEBGL_debug_shaders is byte-identical in the Mac and Catalyst views, and with ANGLE's link placeholders filled in by hand it compiles in a Catalyst process, so the failure seems specific to the Catalyst GPU process. Signing, app sandbox, hardened runtime and a new bundle identifier make no difference. A macOS bundle loaded into the Catalyst process does not help, because its WKWebView is the Catalyst one. Sketchy Workaround: run the page in an AppKit WKWebView in a separate macOS helper process. FB25444425
Replies
1
Boosts
1
Views
231
Activity
1d
Public API for user-authorized interaction with a button in another iOS app?
Goal I am building an iPhone app for a user who has explicitly authorized it. A third-party app on the same device shows a list item with a "Details" button. The content I need is only displayed after that button is pressed. I want my app, in the user's own session and with their consent, to press that button so the detail screen appears. Constraints Stock iOS 26 or later, no jailbreak, no Mac or other computer attached during daily use, App Store distribution. What I have looked at XCUITest and WebDriverAgent need a host computer. Switch Control, Voice Control, and AssistiveTouch appear to be user-enabled system features. I could not find a public API that lets a third-party app trigger them. Shortcuts has no action that taps inside another app. App Intents works only when the other app exposes its own intents. Questions Is there any public, App Store-compatible API on iOS that lets an app, with user authorization, press a button inside another app? If not, is that an intentional platform boundary? Is there any other supported technical architecture for this use case, other than relying on the other app's own App Intents? Thank you.
Replies
1
Boosts
0
Views
234
Activity
1d
Game Center overlay places its back and Play buttons under the rounded corners (and camera) on iPhone Duo's outer display
Environment Device: iPhone Duo, closed (outer display), iOS 27.2 Xcode 27.1 (27A9275), iOS 27.1 SDK, deployment target iOS 18 SwiftUI app lifecycle (WindowGroup, generated scene manifest, generated UILaunchScreen), not letterboxed What happens On the iPhone Duo's outer display, the Game Center screens that GKAccessPoint.trigger(...) opens put their top controls (the round back button at the top left, the "Play" button at the top right) right up in the display's rounded top corners, where the corner partly clips them. The same screens look correct on other iPhones. The outer display's status sits in a column at the right, so a full-screen window there gets a top safe area inset of 0. On other iPhones the top inset (status bar or Dynamic Island) keeps these buttons clear of the corners. The overlay appears to rely on that inset and has no margin of its own for the display's corner radius. Our own app content on the same display handles this: when the top safe area is 0 we add a fixed top margin. The Game Center overlay has no API for us to do the same, at least none that we can find. Steps to reproduce Sign in to Game Center on an iPhone Duo and keep it closed (outer display). In any app, call GKAccessPoint.shared.trigger(leaderboardID: "<id>", playerScope: .global, timeScope: .allTime, handler: {}) Look at the top corners of the Game Center screen, on the leaderboards list and on a single leaderboard. Expected: the back and Play buttons sit clear of the rounded corners, as on other iPhones. Actual: they sit under the corners (screenshot, though it doesn't show the camera cutout) What we tried (none changed the layout at all) Binding the access point to our window before every trigger: let scene = UIApplication.shared.connectedScenes.compactMap { $0 as? UIWindowScene } .first { $0.activationState == .foregroundActive } if let window = scene?.keyWindow { GKAccessPoint.shared.parentWindow = window } GKAccessPoint.shared.trigger(leaderboardID: id, playerScope: .global, timeScope: .allTime, handler: {}) Hosting GKGameCenterViewController (deprecated in iOS 26, used only for this test) as a child of our own full-screen view controller, with a top safe area margin: final class GameCenterHolder: UIViewController, GKGameCenterControllerDelegate { let screen: GKGameCenterViewController // GKGameCenterViewController(leaderboardID:playerScope:timeScope:) // init sets modalPresentationStyle = .fullScreen override func viewDidLoad() { super.viewDidLoad() screen.gameCenterDelegate = self addChild(screen); view.addSubview(screen.view); screen.didMove(toParent: self) } override func viewSafeAreaInsetsDidChange() { super.viewSafeAreaInsetsDidChange() screen.additionalSafeAreaInsets.top = view.safeAreaInsets.top < 1 ? 20 : 0 } nonisolated func gameCenterViewControllerDidFinish(_ vc: GKGameCenterViewController) { MainActor.assumeIsolated { dismiss(animated: true) } } }The screen opened and worked, but its layout was identical. The same holder, giving the child a smaller frame instead (starting 20 pt lower): override func viewDidLayoutSubviews() { super.viewDidLayoutSubviews() let top: CGFloat = view.safeAreaInsets.top < 1 ? 20 : 0 screen.view.frame = view.bounds.inset(by: UIEdgeInsets(top: top, left: 0, bottom: 0, right: 0)) }Still identical, so the screen seems to be drawn by the system outside the app's view hierarchy, out of the app's reach. We also checked the usual causes: the app is built with the iOS 27.1 SDK, uses the scene lifecycle and a generated launch screen, doesn't use UIScreen.main for layout, and fills the outer display edge to edge (not letterboxed).
Replies
0
Boosts
0
Views
101
Activity
2d
Metal 4: MTL4Compiler crashes when many threads capture binaries into one MTL4PipelineDataSetSerializer
Hey all, hoping someone on the Metal team can take a look at this one. It's a crash inside Metal 4's binary capture, and as far as I can tell there's no way to fix it from the app side. Filed as FB25478288 (partial repro is link is there too). Why I think it matters The setup that crashes is basically the recommended Metal 4 workflow: one MTL4Compiler with a MTL4PipelineDataSetSerializer (CaptureBinaries) attached, called from maximumConcurrentCompilationTaskCount threads, to harvest pipelines for an offline archive. Lots of pipelines share a vertex function, which I'd guess is true for most real renderers. The crash is 100% inside Metal.framework, with no app code on the crashing thread. It's easy to hit: 3 out of 3 harvest runs crashed for us, one of them 2 s in. The serializer is attached to the compiler implicitly, so the app can't put a lock around whatever it does internally. MTL4Compiler is Sendable, and the docs say it handles multithreading by default, so I'd expect capture to be thread-safe too. Environment MacBook Pro M2 Max, macOS 27.2, Xcode 27.2, Metal toolchain 32023.922.4 Also reported on an M3 Pro ~33k render pipelines over ~16k vertex functions, up to ~1,000 pipelines in a row sharing one vertex function MTL4RenderPipelineDescriptor with MTL4LibraryFunctionDescriptor stages (sometimes wrapped in MTL4SpecializedFunctionDescriptor), all colour attachments Unspecialized The serializer gets written out with serializeAsArchiveAndFlushToURL: every so often, then we start a fresh compiler + serializer Crash EXC_BAD_ACCESS (SIGSEGV), "possible pointer authentication failure": objc_msgSend MultiLevelAirntBinaryCache::getElementAtDestination(MTLBinaryKey*, ...) -[MTLCompiler compileFunctionRequestInternal:frameworkLinking:linkDataSize:reflectionOnly:compilerTask:completionHandler:] ... AGX::Compiler::compileProgram<AGX::VertexProgramKey, ...>It looks like a use-after-free: two compiles capturing the same vertex program at the same time, and an entry in the destination archive gets freed while the other one is still using it. It only happens with capture on, and it goes away if we never let two capture compiles that share a stage function run at once. Workaround we ship (not great) A lock per stage function around each capture compile, plus sending runs of pipelines that share a vertex shader to the same thread. That stopped the crashes, but we had to put a timeout on the lock, because the compiler occasionally never returns, so in theory it can still race. Second, related crash If serializeAsArchiveAndFlushToURL: runs while other threads are still compiling into that serializer, we get a different crash (null deref at 0x30) in dispatch_data_create_map ← -[_MTLBinaryArchive newArchiverIdWithBinaryKey:entry:srcArchiverId:functionType:]. Our standalone repro hits this one reliably. The getElementAtDestination crash only shows up with our real workload so far. Repro + details https://github.com/Aeonitis/metal4-capture-race It's a small Objective-C repro (Metal + Foundation only) with a bunch of modes, the results so far, and a comparison with how Vulkan (VkPipelineCache) and D3D12 spell out the thread-safety rules for this same pattern. Questions Is capturing from multiple threads into one MTL4PipelineDataSetSerializer meant to be supported? If not, could the docs say so? Is one compiler + one serializer per thread a safe workaround, or is there shared state between compilers in the same process that would still race? Is calling serializeAsArchiveAndFlushToURL: while compiles are still in flight on that serializer allowed? Is this already fixed in a seed
Replies
1
Boosts
0
Views
509
Activity
2d
M5 Pro external 5K 165Hz display: Window animations and scrolling UI appear to render at ~60Hz/jitter while cursor remains perfectly smooth
Hello Apple engineers, I’m trying to determine whether what I’m seeing is expected behavior or a software issue with the new M5 Pro platform. System MacBook Pro (M5 Pro) Latest macOS Beta External 5K 165Hz monitor connected via DisplayPort Refresh rate correctly detected as 165Hz What I observe The display itself is clearly running at 165Hz. For example: Mouse cursor movement is extremely smooth. Dragging the desktop by holding an empty area is also perfectly smooth. However: Moving application windows feels much closer to 60Hz. Scrolling in Safari, Chrome and other applications also appears to run at a much lower frame rate than the display refresh rate. Mission Control animations sometimes show similar micro-stutters. This makes the cursor and desktop movement noticeably smoother than normal window animations. ⸻ Troubleshooting already performed Different DisplayPort cables Different timing configurations Different resolutions / HiDPI modes DSC enabled and disabled Refresh rate confirmed at 165Hz Same behavior across multiple applications The issue appears unrelated to the monitor itself because the cursor is clearly rendered at the full refresh rate. ⸻ Additional observation Interestingly, I previously used another external 4K 144Hz HDR monitor and did not notice this behavior. I also found another M5 Pro user reporting nearly the same issue: external 165Hz display smooth cursor window dragging jitter / micro-stuttering At the same time, I haven’t found similar reports from M4 Pro or the base M5 running the same monitor. ⸻ My question Could this be related to the new M5 Pro display pipeline (WindowServer, Display Engine, or DCP)? Is there any known issue regarding high-refresh-rate external displays on the M5 Pro platform? Or is there additional diagnostic logging (WindowServer, DCP, Metal, etc.) that would help identify whether frames are actually being presented at the display refresh rate? I’d be happy to provide: sysdiagnose WindowServer logs Screen recordings Display timing information IORegistry dumps if they would be helpful. Thank you!
Replies
8
Boosts
1
Views
2.6k
Activity
4d
M5 Pro WindowServer/Display Engine: Window animations and UI scrolling capped at ~60Hz on external 5K 165Hz display while hardware cursor remains smooth
On the new M5 Pro platform running macOS, UI animations (window dragging, Safari/Chrome scrolling, Mission Control) on an external 5K 165Hz display appear to render at a much lower frame rate (~60Hz) or exhibit severe micro-stuttering. However, the mouse cursor and desktop wallpaper dragging remain perfectly fluid at 165Hz, indicating a potential issue in the WindowServer compositor or display pipeline rather than the physical link. Environment • Hardware: MacBook Pro (M5 Pro) • OS: macOS 27.0 beta 3 (26A5378j) • External Display: 5K 165Hz monitor connected via DisplayPort (DSC confirmed via IORegistry). System Settings correctly detects and selects 165Hz. Expected Behavior All UI elements, including window movement, application scrolling, and system animations, should render smoothly at the native 165Hz refresh rate matching the hardware capabilities. Actual Behavior The display output appears split between two different refresh rates: 1. Full 165Hz: The hardware mouse cursor and desktop dragging (empty area selection) are perfectly smooth. 2. ~60Hz / Jitter: Application windows (Finder, Safari, Chrome) stutter heavily when dragged or scrolled. Mission Control animations suffer from micro-stutters. Note: This specific combination suggests the Hardware Cursor layer is running at full rate, but the WindowServer compositor layer is throttled or dropping frames. Troubleshooting Performed (No Change) • Verified with multiple certified DisplayPort cables. • Tested across various resolutions (Scaled/HiDPI modes) and toggling DSC. • Regression Check: This issue did not occur on a 4K 144Hz HDR monitor previously, and initial community feedback shows other M5 Pro users experiencing this specific 165Hz window-dragging jitter, while M4 Pro / base M5 users on the same macOS beta do not seem impacted. Questions & Diagnostics 1. Is this a known regression related to the new M5 Pro display engine / Display Coprocessor (DCP) pipeline handling 5K high-refresh-rate timings? 2. Are there specific defaults write commands, Quartz Debug profiles, or custom logging arguments (WindowServer, DCP, or Metal) we can enable to capture frame presentation metrics? I have captured a sysdiagnose, IORegistry dump, and high-frame-rate screen recordings, and am ready to attach them as soon as this feedback is processed. Case / Feedback Reference Feedback ID: FB23616959 (Captured after the system format)
Replies
1
Boosts
1
Views
851
Activity
5d
Doc bug? Any reason to use Metal's wantsExtendedDynamicRangeContent instead of CALayer preferredDynamicRange?
Should CAMetalLayer wantsExtendedDynamicRangeContent be considered deprecated? Some links for context: CAMetalLayer wantsExtendedDynamicRangeContent for iOS 16+ CALayer wantsExtendedDynamicRangeContent for iOS 17+ CALayer preferredDynamicRange for iOS 26+ So Metal got it, then CALayer got it, then CALayer got a more extensible one in iOS26 and wantsExtendedDynamicRangeContent got marked Deprecated. But it's not marked as deprecated on the CAMetalLayer. I tested it and setting preferredDynamicRange on the CALayer worked to allow my CAMetalLayer to show HDR content on both iOS 27 and tvOS 27. I don't know if there's some reason though (performance for example?) to prefer setting the property on the CAMetalLayer rather than the CALayer. I'm asking because I want react-native-webgpu to support HDR on tvOS, but right now they're using CAMetalLayer wantsExtendedDynamicRangeContent which has no tvOS support. https://github.com/wcandillon/react-native-webgpu/pull/607
Replies
1
Boosts
0
Views
463
Activity
5d
Total triangle budget for a one skinned character app, iOS 26 and later
Hello, I’m working on an iOS app built around a single skinned character with fur, rendered in Metal and shown in close-up, so it takes up most of the screen. It needs to run at a steady 60fps, and the oldest hardware I want to support is the A15 (iPhone 13). The fur will be alpha cards layered over the base mesh. All of the character’s motion is computed on the GPU each frame, and ARKit and Vision hand tracking are running at the same time. This is what I have so far. A 180k-triangle test character with no hair cards runs smoothly in the Simulator on my Mac (yes, I know it's not entirely representative of the GPU numbers on a phone). On an actual iPhone 16, a synthetic bench (60k vertices, 4 influences each) put GPU skinning at 1.1 to 1.3 ms whether I used 250 joints or 1000, so I’m not worried about skinning. The final model is still being built, so I can’t test the real thing yet, but I have to give the modeler a budget now. I’m thinking of 100k to 120k triangles in total, base mesh plus alpha cards. Would that look fairly reasonable for an A15, or not? Thanks!
Replies
2
Boosts
0
Views
310
Activity
6d
CIRAWFilter.supportedCameraModels(with: .version9) does not include camera models that appear to be supported
CIRAWFilter.supportedCameraModels(with: .version9) does not include some camera models that appear to be supported. For example a Sony A1 or Nikon Z8 RAW file opened using CIRAWFilter and then calling filter.supportedDecoderVersions.contains(.version9) return true but these models are not included in the supportedCameraModels list. Why is the supportedCameraModels(with:) not all the supported camera models ?
Replies
1
Boosts
0
Views
226
Activity
6d
Is Metal 4.1 `interleave` available on M4 Pro? Pipeline creation fails with "unlowered function call"
The Metal Shading Language Specification 4.1, section 6.4, lists interleave and deinterleave as "All OS: Metal 4.1 and later", with no GPU family restriction. The Metal Feature Set Tables list the M4 series as Apple9 and have no row for interleave. On an M4 Pro, a kernel that calls interleave compiles, but creating its compute pipeline fails. Which GPUs and macOS versions support interleave and deinterleave, and is the M4 family expected to? import Metal let src = """ #include <metal_stdlib> kernel void k(device const metal::uchar2 *a [[buffer(0)]], device metal::ushort *b [[buffer(1)]], uint i [[thread_position_in_grid]]) { b[i] = metal::interleave(a[i]); } """ let device = MTLCreateSystemDefaultDevice()! let options = MTLCompileOptions() options.languageVersion = .version4_1 let function = try! device.makeLibrary(source: src, options: options).makeFunction(name: "k")! do { _ = try device.makeComputePipelineState(function: function) print(device.name, "| pipeline created") } catch { print(device.name, "| pipeline failed:", error.localizedDescription) }The library compiles, but creating the pipeline fails. ushort2/uint, uint2/ulong and deinterleave fail the same way. Apple M4 Pro | pipeline failed: Encountered unlowered function call to air.interleave.i16. Verify device or GPU architecture supports this featureIf I replace the kernel line b[i] = metal::interleave(a[i]); with b[i] = metal::ushort(a[i].x) | (metal::ushort(a[i].y) << 8);, it prints Apple M4 Pro | pipeline created. Configuration Apple M4 Pro, macOS 27.2.1 (26B131), Xcode 27.1 (27A9275), Swift 6.4, metal 32023.921. Software Update shows nothing newer.
Replies
1
Boosts
0
Views
163
Activity
1w
CGSetDisplayTransferByTable is broken on macOS Tahoe 26.4 RC (and 26.3.1) with MacBook M5 Pro, Max and Neo
The CGSetDisplayTransferByTable() is not working on the latest round of Mac hardware, namely the MacBook Neo (external display), MacBook M5 Pro (both built-in and external display) and possibly the M5 Max. All tested apps (BetterDisplay, MonitorControl, f.lux, Lunar) exhibit the very issue both in macOS Tahoe 26.3 and macOS Tahoe 26.4 RC. Tested on multiple Macs and installations on the MacBook Neo and MacBook M5 Pro. This issue breaks several display related macOS apps. Way to reproduce the issue using an affected app: Install the app BetterDisplay (https://betterdisplay.pro) Launch the app, open the app menu, choose Image Adjustments and try to adjust colors. Adjustments take no effect Way to reproduce the issue programmatically: Attempt to use the affected macOS API feature: https://developer.apple.com/documentation/coregraphics/cgsetdisplaytransferbytable(::::_:) Here are the FB numbers: FB22273730 (Filed this one as a developer on an unaffected MBP M3 Max) FB22273782 (Filed from an affected MBP M5 Pro running 26.4 RC, with debug info attached)
Replies
19
Boosts
7
Views
8.7k
Activity
1w
A small scrolling ticker pins GPU at ~50% on a rich screen but ~0% on a blank one — is whole-tree compositing at the animation's rate the expected cost?
I have a SwiftUI clock-radio app on iPhone (ProMotion display). The face is a rich, layered screen (glass panels, gradients, shadows). One element is a 340×46 pt text ticker strip that scrolls continuously. Its GPU behaviour is reproducible and, to me, surprising: Measurements (Xcode GPU gauge used only for within-session relative contrasts; cadence from an in-app frame-pacing log): With the ticker scrolling, GPU sits at a ~50% plateau. The step is binary: one scroller or three scrollers cost the same. Frames are never dropped: 16.7 ms median frame time, ~3% of frames over 20 ms. The GPU bills heavily for frames it renders on time. The same strip scrolling on an otherwise blank screen costs ~0%. The ticker visible but static costs 0%. Motion is the trigger; the cost scales with what surrounds the strip, not with the strip itself. What I have tried: SwiftUI offset animation of the text — baseline behaviour above. A fully severed Canvas leaf: own layer subtree, own CADisplayLink, snapshot-fed, no view-tree publishing or subscriptions — identical cost on the full face (and literally 0% redrawing alone on a blank screen at full frame rate). Pre-rendered bitmap content scrolled instead of text — identical. The strip hosted in a separate UIWindow above the face — identical, measured with the strip visibly scrolling in its seat. Pinning the strip's CADisplayLink.preferredFrameRateRange to exactly 30 Hz (minimum = maximum = preferred = 30) — no change. .compositingGroup() on the panel subtree — a modest reduction only. What works: removing the motion duty (scroll once, then park — cost collapses), and, elsewhere in the app, a pull-model spectrum visualiser replaced a publish-driven one and its cost vanished. Severing worked for the visualiser but not for the ticker. Questions: Is this step the expected consequence of the WWDC22 session 10083 rule (the display refresh rate is set by the highest-frame-rate animation in the app) composed with whole-layer-tree compositing per presented frame? Is there any dirty-region scoping that a layer structure like ours defeats? The 30 Hz pin above was hard (min = max = preferred). Would a CAFrameRateRange in the 15–24 Hz band that Apple's ProMotion guidance suggests for small, slow animations behave materially differently, or is that distinction already settled by the 30 Hz result? Is there a known construction for a continuously scrolling ticker that lets the GPU idle between updates? Happy to share a minimal repro or the pacing logs if useful.
Replies
2
Boosts
0
Views
543
Activity
1w
Distributing D3DMetal with a Mac App Store app
Hello, We develop a Mac App Store app that runs Windows on Apple silicon. We use D3DMetal from the Game Porting Toolkit so that DirectX 12 games and apps can run in it. Today, each user has to download the Game Porting Toolkit, open the "Evaluation environment" disk image and point our app to D3DMetal.framework. Many users find this confusing, and we would like to make DirectX 12 work out of the box. When we tried to bundle D3DMetal.framework in our app, App Store Connect rejected the upload: ▎ Invalid Bundle. The application bundle may not contain tools or frameworks provided by Apple, or using bundle identifiers in the 'com.apple.' namespace. Invalid bundle: D3DMetal … with bundle identifier 'com.apple.D3DMetal'. We also note that the Game Porting Toolkit licence limits distribution to non-commercial purposes. Our questions: Is there an approved way for a Mac App Store app to include or distribute D3DMetal, for example a commercial redistribution agreement or a separate licence? If not, is there a supported way for an App Store app to obtain D3DMetal on the user's Mac, such as an Apple-provided download or a system component it can use? Are there plans to make D3DMetal available to third-party apps, as a public framework or as part of macOS? We want to follow Apple's licence and App Store guidelines, so any guidance on the correct approach would be much appreciated. Thank you.
Replies
0
Boosts
0
Views
229
Activity
1w
Request for PROLED display to support Adaptive Sync (VRR)
I was hoping with an OLED display that the new MBP might support true Adaptive Sync aka VRR. Alas, it only gets ProMotion, with the same huge gap between supported refresh rates at the top end (60hz and 120hz). Hooking up an HDMI VRR display such as any LG TV results in a display that works much better with variable framerates than the built-in display, since you can deliver frames at any interval between the min and max. VRR greatly improves games and already works great in macOS with an external display, so I humbly request that Apple consider another option next to ProMotion, for Adaptive Sync/VRR.
Replies
0
Boosts
0
Views
234
Activity
1w
Game Center Player Identity Continuity After App Transfer Between Developer Accounts
Dear Apple Developer Support Team, We plan to transfer multiple non-Apple Arcade games from Developer Account A to Developer Account B. The transfers have not yet been initiated. Approximately one million existing players use Game Center to sign in and link their identities to our in-game accounts. Before initiating the transfers, we need to clarify how player identities will be preserved. If internal implementation details cannot be disclosed, please describe the observable behavior from our apps and backend servers. We would appreciate direct confirmation or correction of the following statements. Background We use Game Center authentication signatures to verify player identities and associate Game Center IDs with our own account system, following Apple’s requirement: “Trust only the fields in the signed payload.” Our existing records contain legacy playerID (deprecated API) and teamPlayerID, but not gamePlayerID. Apple documentation states that the current authentication signature payload for non-Arcade games contains teamPlayerID, bundleID, timestamp, and salt, but not gamePlayerID. Therefore, even if gamePlayerID remains unchanged after the transfer, we cannot independently verify its authenticity. After the transfer, there will be three player categories: Existing installations that are not updated, continuing to use versions signed by Account A. New installations downloaded from the App Store after the transfer, still using versions signed by Account A. Players who update to new versions released under Account B. Questions 1. legacy playerID: Status and Availability (A) Is playerID globally scoped rather than tied to a developer account (Team ID)? Does transferring an app leave existing players’ playerID values unchanged? (B) Does Apple provide any way to map historically stored legacy playerID values to the corresponding gamePlayerID or teamPlayerID? (C) Although the playerID API is deprecated, will Apple stop returning this value in a future iOS version, or under any specific conditions? 2. What Determines teamPlayerID? Please confirm which model applies, or explain the actual mechanism: (A) teamPlayerID is determined by the app’s current developer account (Team ID), meaning all players’ values change immediately when the transfer takes effect, regardless of app version. (B) teamPlayerID is determined by the account that signed the installed app, meaning values change individually when players update to a version signed by Account B. For the three player categories above, which account’s teamPlayerID will Game Center return? Specifically: Will categories (1) and (2) receive the same value? Are there differences between app updates, fresh installations, and uninstalling and reinstalling? 3. Can Older Versions Signed by Account A Still Be Verified? (A) Can older versions in categories (1) and (2) still authenticate with Game Center and generate valid signatures that our backend can verify? (B) Will Apple stop issuing authentication signatures for versions signed by Account A? If so, under what conditions or after what period? 4. How Can Players Be Reliably Reassociated with Their Original Game Accounts? If teamPlayerID changes after the transfer, while gamePlayerID remains unchanged but is absent from the signed payload: (A) Does Apple provide an official mechanism to prove that a post-transfer player identifier belongs to the same Game Center account as a previously stored identifier? (B) If not, how does Apple recommend that non-Arcade games securely verify that returning players are the legitimate owners of their original game accounts after an account transfer? (C) If Apple recommends using gamePlayerID, please clarify: Is accepting a client-reported gamePlayerID, which is not included in the signed payload, an Apple-approved practice for non-Arcade games? Since an attacker could submit another player’s gamePlayerID to hijack their account, what protection does Apple recommend against such impersonation? 5. Required Actions and Timing for Developers and Players (A) What actions should Accounts A and B take at each stage of the transfer? Does Apple provide migration credentials, identifier mapping exports, or other migration mechanisms? (B) Must players sign in or update the app before the transfer takes effect? What happens to those who do not? (C) If players must act within a specific time window, how should we handle those who do not launch the game during that period and only return months or years later? How can their original accounts and game data be preserved? 6. Can We Verify These Behaviors Before the Transfer? (A) Can Game Center Sandbox or TestFlight environments reproduce identifier changes before and after an app transfer between developer accounts? (B) If not, can we transfer a test app between our two developer accounts to verify the actual behavior? Are there any restrictions? (C) If neither approach is possible, what does Apple recommend for verifying these behaviors before the actual transfer? ⸻ This transfer affects the continuity of approximately one million existing player accounts. We would therefore like to obtain clarification before submitting the transfer requests. If these questions are outside the current support team’s scope, please escalate this inquiry to the Game Center engineering team. Thank you for your assistance. Best regards !
Replies
0
Boosts
0
Views
63
Activity
1w
PDFKit Page Rerender
I'm experiencing an issue with PDFKit where page.removeAnnotation(annotation) successfully removes the annotation from the page's data structure, but the PDFView no longer updates automatically to reflect the change visually. Issue Details: The annotation is removed (verified by checking page.annotations.count) The PDFView display doesn't refresh to show the removal This code was working correctly before and suddenly stopped working No code changes were made on my end
Replies
5
Boosts
3
Views
1.9k
Activity
1w
Request for higher hardware encoding resolution/performance on the future Mac desktop/laptop platforms for VR support.
Request: Mac media-engine headroom for 3840-per-eye stereo encoding to Apple Vision Pro We develop a Mac app that streams OpenXR VR applications, rendered on the Mac's GPU, to Apple Vision Pro as stereo video. The Mac encodes with VideoToolbox, as MV-HEVC (one layer per eye) or side-by-side HEVC. Vision Pro decodes the stream and presents it in an immersive space. We'd like to ask for future Mac hardware to support stereo encoding at Vision Pro-class resolution: 3840 pixels per eye at 90 fps. Why resolution matters without eye tracking Vision Pro does not give applications eye-tracking data. We understand and respect the privacy reasons. It does mean a streaming app can not use gaze-driven foveated encoding, which sends full detail where the wearer is looking and less elsewhere. Streaming solutions on other headsets use that to stay within their encoder budget. Without gaze data, every part of each eye's image has to be sent at full detail, so the only route to a sharper image is encoding more pixels. Today the encoder is where that stops. What we measured (tested on an M4 Max) M4 Max, macOS 27.0.1, hardware HEVC through VideoToolbox, synthetic frames at 200 Mbps, no frame reordering, RealTime off, speed prioritised, frames submitted at 90 Hz with at most 4 in flight, eye heights at 20:19. Results are frames per second, with median encode latency in brackets. MV-HEVC: 2048×1952 per eye: 90 fps (16 ms) 2240×2128 per eye: 90 fps (19 ms), the largest size that holds 90 2304×2192 per eye: 87 fps (46 ms) 3072×2928 per eye: 50 fps (79 ms) 3840×3648 per eye: 33 fps (121 ms) Side-by-side HEVC: 2048×1952 per eye: 90 fps (12 ms) 3072×2928 per eye: 90 fps (25 ms) 3200×3040 per eye: 90 fps (27 ms), the largest size that holds 90 3328×3168 per eye: 86 fps (46 ms) 3840×3648 per eye: 65 fps (61 ms) What the numbers show: One MV-HEVC session uses one media engine (about 0.92 Gpx/s at every size). The second engine sits idle: two MV-HEVC sessions at 3840 per eye run at the same time at 33 fps each. One single-layer HEVC session spreads across both engines (about 1.82 Gpx/s), but only while nothing else is encoding. With a second session open (we used a 1080p30 desktop share), it drops to one engine: 3072 per eye falls from 90 to 52 fps, and 3840 per eye from 65 to 33 fps. GPU load does not slow the media engine. We repeated the tests beside a synthetic GPU load using 7 to 9.6 ms of every 11.1 ms frame, as a VR title would, and every result was unchanged. The encoding window we actually have At 90 Hz a frame lasts 11.1 ms, and the VR application uses most of that rendering on the GPU. Rendering and encoding run in sequence for each frame, so every millisecond of encoding adds directly to the wearer's motion-to-photon latency, on top of the app's own frame. In practice we need two things from the encoder: Latency: finish each frame within about one frame period (around 11 ms), so the stream adds no more than one frame beyond the app. Today 2048 per eye MV-HEVC takes 16 ms, or about 1.5 frames. Headroom: run at no more than about 75 % of capacity. Real scenes vary in complexity, and near the limit latency climbs steeply (side-by-side HEVC goes from 27 ms at 3200 per eye to 46 ms at 3328 per eye). At 75 % load an M4 Max supports about 2000 per eye for MV-HEVC, which is the 2048 we ship today, and about 2800 per eye for side-by-side HEVC when no other session is running. 3840×3648 per eye at 90 fps is 2.52 Gpx/s. With the 25 % headroom, that is about 3.4 Gpx/s of sustained encode capacity: roughly 1.9× both M4 Max engines together, or 3.7× the single engine an MV-HEVC session gets today. For comparison, our Windows host encodes MV-HEVC at 3840×3648 per eye at 90 fps on a current desktop NVIDIA GPU, in about 11 ms per frame, by splitting the work across its encoder engines. Vision Pro decodes and presents that stream at 90 fps, so the headset handles this resolution. The gap is on the Mac's encoding side. What we don't know yet We do not yet know whether the Mac GPU can render VR titles at 3840 per eye at 90 fps; that will depend on the title. We can not usefully find out while the encoder limits us first, so in practice we ship MV-HEVC/HEVC at 2048 per eye by default. What we're asking for About 3.4 Gpx/s of HEVC / MV-HEVC encode capacity in future Mac media engines, enough for 3840×3648 per eye at 90 fps with headroom, plus room for a smaller second session such as a desktop share. MV-HEVC/HEVC sessions that can use more than one media engine on chips that have them. On current chips this alone would roughly double the stereo ceiling. A single-layer HEVC session that keeps its multi-engine split while another session is running, or a property to request that. If the platform can offer it, a privacy-preserving foveation path for streaming apps, where the system supplies a foveation region to the encoder without the app ever seeing raw gaze. If a VideoToolbox configuration already lets one MV-HEVC/HEVC session use both engines, we'd be glad to hear about it. We're happy to file a Feedback report with our test tool attached.
Replies
0
Boosts
0
Views
227
Activity
1w
Damage numbers on 100s of enemies - performance question
Hello guys, i hope someone can help with that *i already have particle system working for hit feedback on enemies, and i manage to maintain the FPS quite good while using a pre-wamred pool of emitters and a cleanup system that cycle thru that pool. So i do have some basic experience with the particle system and the ECS system. For the spawning of damage numbers of enemies, I try to find a way to show damage numbers on enemies while keeping performence . 100s of enemies might get hit at a single frame, In unreal i used niagara Particles with UV pooling, with mass. object pooling the numbers with the GPU itself fed by the cpu mass ECS. What is the best way to do that in reality kit ? System is very high level, im not sure what is the best approach to begin with to keep good FPS. even if i need to use AI to write some custom shader, i still need help to design the overall system (should i put the logic inside an ECS system with a dedicated emitter with a custom metal shader for the particles?) Thank you guys
Replies
1
Boosts
0
Views
866
Activity
1w