I decided to use a club to kick a ball and let it roll on the turf in RealityKit, but now I can only let it slide but can not roll. I add collision on the turf(static), club (kinematic) and the ball(dynamic), and set some parameters: radius, mass. Using these parameters calculate linear damping, inertia, besides, use time between frames and the club position to calculate speed. Code like these: let radius: Float = 0.025 let mass: Float = 0.04593 // 质量，单位：kg var inertia = 2/5 * mass * pow(radius, 2) let currentPosition = entity.position(relativeTo: nil) let distance = distance(currentPosition, rgfc.lastPosition) let deltaTime = Float(context.deltaTime) let speed = distance / deltaTime let C_d: Float = 0.47 //阻力系数 let linearDamping = 0.5 * 1.2 * pow(speed, 2) * .pi * pow(radius, 2) * C_d //线性阻尼（1.2表示空气密度） entity.components[PhysicsBodyComponent.self]?.massProperties.inertia = SIMD3<Float>(inertia, inertia, inertia) entity.components[PhysicsBodyComponent.self]?.linearDamping = linearDamping // force let acceleration = speed / deltaTime let forceDirection = normalize(currentPosition - rgfc.lastPosition) let forceMultiplier: Float = 1.0 let appliedForce = forceDirection * mass * acceleration * forceMultiplier entityCollidedWith.addForce(appliedForce, at: rgfc.hitPosition, relativeTo: nil) Also I try to applyImpulse but not addForce, like: let linearImpulse = forceDirection * speed * forceMultiplier * mass No matter how I adjust the friction(static, dynamic) and restitution, using addForce or applyImpulse, the ball can only slide. How can I solve this problem?

I am working on adding synchronized physical properties to EntityEquipment in TableTopKit, allowing seamless coordination during GroupActivities sessions between players. Treating EntityEquipment's state to DieState is not a way, because it doesn't support custom collision shapes. I have also tried adding PhysicsBodyComponent and CollisionComponent to EntityEquipment's Entity. However, the main issue is that the position of EntityEquipment itself does not synchronize with the Entity's physics body, resulting in two separate instances of one object. struct PlayerPawn: EntityEquipment { let id: ID let entity: Entity var initialState: BaseEquipmentState init(id: ID, entity: Entity) { self.id = id let massProperties = PhysicsMassProperties(mass: 1.0) let material = PhysicsMaterialResource.generate(friction: 0.5, restitution: 0.5) let shape = ShapeResource.generateBox(size: [0.4, 0.2, 0.2]) let physicsBody = PhysicsBodyComponent(massProperties: massProperties, material: material, mode: .dynamic) let collisionComponent = CollisionComponent(shapes: [shape]) entity.components.set(physicsBody) entity.components.set(collisionComponent) self.entity = entity initialState = .init(parentID: .tableID, pose: .init(position: .init(), rotation: .zero), entity: self.entity) } } I’d appreciate any guidance on the recommended approach to adding synchronized physical properties to EntityEquipment.

Hello, Ive been playing this game called "WarThunder" for quite some time now, however up until now the game wont start up, it just jumps up a few times before giving me a report, this has been a issue for me for the past week ive tried many methods suggested by others, but none of them work I was wondering if it was a issue with the games code -------------------------------------Process: aces [16722] Path: /Applications/WarThunderLauncher.app/Contents/WarThunder.app/Contents/MacOS/aces Identifier: com.gaijinent.WarThunder Version: 1.0 (1) Code Type: X86-64 (Translated) Parent Process: launchd [1] User ID: 505 Date/Time: 2024-11-10 13:00:25.3935 -0700 OS Version: macOS 15.1 (24B83) Report Version: 12 Anonymous UUID: 71AEF0EF-DD30-A031-539D-24A2819B70D2 Sleep/Wake UUID: 4B33BEDC-EC2B-4983-BFDF-1EE49AD45A33 Time Awake Since Boot: 56000 seconds Time Since Wake: 188 seconds System Integrity Protection: enabled Notes: PC register does not match crashing frame (0x0 vs 0x7FF89BDF2A84) Crashed Thread: 21 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: aces [16722] Error Formulating Crash Report: PC register does not match crashing frame (0x0 vs 0x7FF89BDF2A84)

Hello, our app gets rejected as it crashes on launch. According to the logs, it happens because the app attempts to access private-sensitive data. We don't collect any of personal data, so it is probably done by Google Firebase embedded in the app (Core, Firestore, Auth). Maybe you have met similar cases and know any of Firebase settings that disable attempts of accessing privacy-sensitive data? We already set FirebaseDataCollectionDefaultEnabled to NO in info.plist, but it still not enough. Maybe error in facebook sdk? Before that it was written that there was an error when starting the ipad air 5 Log1 Log2 Log3

Hey, I submitted my game for review several times over the last two weeks, and I keep getting rejeted under the 4.1 Design Copycat guidelines. Guideline 4.1 - Design - Copycats This app or its metadata appears to be misrepresenting itself as another popular app or game already available on the App Store, from a developer's website or distribution source, or from a third-party platform. Apps should be unique and should not attempt to deceive users into thinking they are downloading something they are not. I have tried contacting and writing to the support team several times but I get absolutely no response. The game is completely built from scratch and I own all rights to it which is clearly mentioned as well. There hasn't been a single thing that I have used in the game that is not owned by me and the game in general is completely original and novel with its design, and not trying to compete or derive its design from any other game in the app store. All I just is more clarity and information or someone to respond and help me out with this, since I am a sole developer and I intend to release this game very soon. Thanks, and please help!

The welcome banner is off the top left side of the screen instead of coming down the center. This behavior is encountered when running my iOS application on macOS.

I am a developer, please send me the authentication code, I need the code for the test flight application!

I am a developer, please send me the authentication code !

Dear Apple Supervisors, im Enrik Sulaj an apps and games developer .I have many Why-s ! Why app review team have a stone heart? Why they dont value our work? Why they are not helpful? Why they cant tell us where the problem is ? Why they dont do their work right? Why "They dont share information "even that information can solve the problem. Why they create the problem just to reject our games? I sent an appeal for that, still waiting for it but they always had respond with not a solution to me and not in an helpful form! Why they hate new creators? And the last why, why they make the impossible to undervalue creators hardwork and made us never work with Apple Again. I never saw an car game that collect gold and rubin, gives all free assets or crushes into a wall, but they have always their answer and dont listen to the facts, the most common answer "Duplicated but with anonymous and not shareable proof "Apple supervisors, fix my problem, im an Apple unhappy user of Developer services ! Not about Apple policies, but even my new idea can get rejected. That will hurt so many new creators. Its just not right, to take money and to refuse to give service. If i buy your product you need to give me the service. At least the support, helpful support, not like (We cant share information, becouse if you analise it well that translates in " we cant help " or "we dont have any proof just want to make your road longer ".Fix this asap, apple review team need to support us, not just to say things we already know. My app is duplicated ? How is that possible didnt copy anybody, if they continue like this even if i have the problem i will never solve this becouse i dont know what to do, this situation is making me angry becouse think of it as in the same position, if you get refused for not a real reason. I will never give up, i will get my right, and i hope the other creators facing the same problem fix this also ! Do not use bots to do the work auto and faster, instead use your eyes, they never lie . Do not save time, instead do the work longer and ri to say a little thing, anything will be in the right place at the right time .

Hi i have uploaded a match 3 game and i have changed the game from levels selection to gameplay. but still i am getting copycat rejection. i dont know what i am missing, all the match 3 games have the same generc same gameplay than why i am getting the rejection kindly explain Thanks

I am working on adding synchronized physical properties to EntityEquipment in TableTopKit, allowing seamless coordination during GroupActivities sessions between players. Current Approach and Limitations I have tried setting EntityEquipment's state to DieState and treating it as a TossableRepresentation object. This approach achieves basic physical properties synchronized across players. However, it has several limitations: No Collision Detection Between Dice: Multiple dice do not collide with each other. Shape Limitations: Custom shapes, like parallelepipeds, cannot be configured. Below is my existing code for Base Entity Equipment without physical properties: struct CubeWithPhysics: EntityEquipment { let id: ID let entity: Entity var initialState: BaseEquipmentState init(id: ID, entity: Entity) { self.id = id self.entity = entity initialState = .init(parentID: .tableID, pose: .init(position: .zero, rotation: .zero), entity: self.entity) } } I’d appreciate any guidance on the recommended approach to adding synchronized physical properties to EntityEquipment.

Hi, When using a High Definition Display, is there a way to render at exactly the target resolution on the physical screen? My understanding is that the default behavior is to render to a backing store with a resolution (in pixels) which can be twice the size of the logical resolution (in points). Then we let the OS handle the down-scaling to the actual target resolution on the screen. This is all nice for non-graphics intensive apps, but it means that my game will render at a higher resolution than needed, which seems like an obvious loss of performance. My expectation is that, for graphics intensive application such as games, we should be able to query and render to the final resolution on the display. Can it / should it be done? Thank you for your help :) FYI I did find a document which explains how to setup your CAMetalLayer to render at a custom resolution. I suspect that this may be what I have to do?

Our team has recently encountered a tricky issue: our game app was rejected during the App Store review process due to Guideline 4.3(a) - Design - Spam. We firmly believe this to be a miscarriage of judgment, as our game app is entirely self-developed and does not copy or imitate any other app. We've noted that the App Store review team may have considered our app to share similar binaries, metadata, and/or concepts with other apps on the App Store. However, we would like to emphasize that our team has invested a significant amount of time, effort, and creativity in developing this app. Despite our best efforts, our app was still rejected. We are sincerely seeking help and advice from the Apple Developer Forums community. Have any other developers encountered a similar situation, and if so, how did you resolve it?

Hi everyone, I'm experiencing issues with Apple ID binding and payment on an IPv6 network. I've tried multiple devices and networks, but the problem persists. I'm not sure if it's due to a lack of official support for IPv6. I have a few questions: 1.Has anyone successfully completed Apple ID binding and payment on an IPv6 network? 2.If there is no official support, are there any solutions or alternatives? For example, switching to IPv4 or other workarounds?

Hello everyone, I updated a new version to fix bugs and add more levels, but Apple rejected it citing spam design 4.3(a). Everything in the game is created by my team, and we did not copy or imitate any other product. We discovered that a studio has unpacked our game and stolen all our images, sounds, and many other files, even the file names match ours. Our game was released over a month before theirs, while they just released their first version a week ago. Despite being the original version, our game was rejected for spam. Currently, our game is generating $10k daily in IAP and we are spending a lot on ads. We are in urgent need of updating the game. I’m really frustrated that this issue has not been resolved yet. I have submitted all the information and evidence to the Apple Review Board, but I haven’t received any response so far.

When I was using Instruments to test the Display on my phone, I discovered a long-duration frame. Below that frame, there were some gaps in the vsync queue. As I understand it, vsync signals should appear consistently and steadily. How can this behavior be explained? My phone is iPhone 15 Plus and iOS 18.

I would like to warn other developers about shocking Apple practices of not allowing to update already published games. I have two published games on App Store and Apple does not allow me to update my games to fix simple bugs or just to replace the game icons. The updates are classified as SPAM despite the successful publication of the original games. I cannot comprehend what benefit would Apple have from dealing with upset users and developers who download suboptimal apps and who are not allowed to update already published apps to fix issues and improve users' experience. Do you think that such practices are fair? Your thoughts are welcome.

Hello All, My team and I are developing a mobile application (offgrid) to help combat screen addiction. Our application will allow users through gamification, to challenge each other to stay off certain predetermined apps on their phone for a set amount of time and risk their own money. The money will act as a reinforcement to stay focused and off the application. Example: Jon challenges Jen to stay off Instagram for 1 hour for $5. If Jen accepts the challenge, she and Jon cannot go on Instagram. If Jen or Jon decides to click the Instagram app within the hour, the $5 automatically goes to the winner via Apple Pay or another service. If they complete the challenge and stay off Instagram then there is no exchange of money. I will also give the option for users to challenge each other and risk their money for a charity cause if someone loses. My question is, will the exchange of money count as an in-app purchase, or will the winner receive the full amount? Also, if the money goes to charity, will that count as an in-app purchase? Thanks!

Hi Friends! I’m facing an issue with SceneKit. I’m developing a 3D mobile game. I have a character 3D model and several skeletal animations CAAnimation. I import both the model and the animations from Maya in *.dae format. The character’s animations play continuously one after the other, with each new animation being triggered randomly. The transition between animations makes smoothly by setting the fadeInDuration and fadeOutDuration properties. Here’s an example of the code: import UIKit import QuartzCore import SceneKit class TestAnimationController: UIViewController { var bodyNode: SCNNode? override func viewDidLoad() { super.viewDidLoad() let scnView = SCNView(frame: self.view.bounds) scnView.backgroundColor = .black // Set your desired background color scnView.autoresizingMask = [.flexibleWidth, .flexibleHeight] let scene = SCNScene(named: "art.scnassets/scene/Base_room/ROOM5.scn")! bodyNode = collada2SCNNode(filepath: "art.scnassets/female/girl_body_races.dae")! bodyNode?.renderingOrder = 10 scene.rootNode.addChildNode(bodyNode!) playIdleAnimation() scnView.scene = scene // Assign the scene to the SCNView self.view.addSubview(scnView) // Add the SCNView to your main view) } func collada2SCNNode(filepath:String) -> SCNNode? { if let scene = SCNScene(named: filepath) { let node = scene.rootNode.childNodes[0] return node } else { return nil } } func playIdleAnimation() { let array = [ "art.scnassets/female/animations/idle/girl_idle_4.dae", "art.scnassets/female/animations/idle/girl_idle1.dae", "art.scnassets/female/animations/idle/girl_idle2.dae", "art.scnassets/female/animations/idle/Girl_idle3.dae", ] let animation = CAAnimation.animationWithSceneNamed(array.randomElement() ?? "")! self.setAnimationAdd( fadeInDuration: 1.0, fadeOutDuration: 1.0, keyTime: 0.99, animation, isLooped: false ) { [weak self] in guard let self = self else { return } try? self.playBoringAnimations() } } func playBoringAnimations() { let array = [ "art.scnassets/female/animations/boring/girl_boring1.dae", "art.scnassets/female/animations/boring/girl_boring2.dae", "art.scnassets/female/animations/boring/girl_boring3.dae", "art.scnassets/female/animations/boring/girl_boring4.dae", "art.scnassets/female/animations/boring/girl_boring5.dae", "art.scnassets/female/animations/boring/girl_boring6.dae", "art.scnassets/female/animations/boring/girl_boring8.dae" ] let animation = CAAnimation.animationWithSceneNamed(array.randomElement() ?? "")! self.setAnimationAdd( fadeInDuration: 1.0, fadeOutDuration: 1.0, keyTime: 0.99, animation, isLooped: false ) { [weak self] in guard let self = self else { return } try? self.playIdleAnimation() } } func setAnimationAdd(fadeInDuration : CGFloat, fadeOutDuration : CGFloat, keyTime : CGFloat, _ animation: CAAnimation, isLooped: Bool, completion: (() -> Void)?) { animation.fadeInDuration = fadeInDuration animation.fadeOutDuration = fadeOutDuration if !isLooped { animation.repeatCount = 1 } else { animation.repeatCount = Float.greatestFiniteMagnitude } animation.animationEvents = [ SCNAnimationEvent(keyTime: keyTime, block: { _, _, _ in completion?() }) ] bodyNode?.addAnimation(animation, forKey: "avatarAnimation") } } Everything worked perfectly until I updated to iOS 18. On a physical device, the animations now transition abruptly without the smooth blending that was present in earlier iOS versions. The switch between them is very noticeable, as if the fadeInDuration and fadeOutDuration parameters are being ignored. However, in the iOS 18 simulator, the animations still transition smoothly as before. Here two example videos - IOS 17.5 and IOS 18 https://youtube.com/shorts/jzoMRF4skAQ - IOS 17,5 smooth https://youtube.com/shorts/VJXrZzO9wl0 - IOS 18 not smooth I try this code in IOS 17.5, everything works fine Does anyone have any ideas on how to fix this issue?

This project had been stable for years, doing hundreds of updates for customers but XCode has suddenly started generating lists of errors with every build. I have sent in reports in Feedback Assistant but never get any response. Is this a recent regression in XCode? This project is Objective-C++ with C++11, clang with lots of assembly for both CPU families. Cleaning up ... Building XCode Project... --- xcodebuild: WARNING: Using the first of multiple matching destinations: { platform:macOS, arch:arm64, id:00006001-000851861A42401E } { platform:macOS, arch:x86_64, id:00006001-000851861A42401E } { platform:macOS, name:Any Mac } --- xcodebuild: WARNING: Using the first of multiple matching destinations: { platform:macOS, arch:arm64, id:00006001-000851861A42401E } { platform:macOS, arch:x86_64, id:00006001-000851861A42401E } { platform:macOS, name:Any Mac } 2024-10-02 22:42:09.000 xcodebuild[3235:7055835] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103 Details: createItemModels creation requirements should not create capability item model for a capability item model that already exists. Function: createItemModels(for:itemModelSource:) Thread: <_NSMainThread: 0x6000033fc2c0>{number = 1, name = main} Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide. 2024-10-02 22:42:09.000 xcodebuild[3235:7055835] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103 Details: createItemModels creation requirements should not create capability item model for a capability item model that already exists. Function: createItemModels(for:itemModelSource:) Thread: <_NSMainThread: 0x6000033fc2c0>{number = 1, name = main} Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide. 2024-10-02 22:42:09.000 xcodebuild[3235:7055835] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103 Details: createItemModels creation requirements should not create capability item model for a capability item model that already exists. Function: createItemModels(for:itemModelSource:) Thread: <_NSMainThread: 0x6000033fc2c0>{number = 1, name = main} Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide. 2024-10-02 22:42:09.000 xcodebuild[3235:7055835] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103 Details: createItemModels creation requirements should not create capability item model for a capability item model that already exists. Function: createItemModels(for:itemModelSource:) Thread: <_NSMainThread: 0x6000033fc2c0>{number = 1, name = main} Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide. 2024-10-02 22:42:09.000 xcodebuild[3235:7055835] [MT] DVTAssertions: Warning in === CUT 10000 LINES of XCode Errors === PS: the maximum length on these forum posts is crazy small!