Yes, that wasn't the issue. It doesn't like the order and there is overlap. It's easier to see when you reduce the nProfiles and print the arrays to visually inspect them. I don't even remember why I started using .makeVerticesUniqueAndReturnError() but it's not even needed here. let controlPoints: [(x: Float, y: Float)] = [ (0.728,-0.237), (0.176,-0.06), (0.202,0.475), (0.989,0.842), (-0.066,1.093), (-0.726,0.787) ] let pairs = bsplinePath(controlPoints) var knobProfile = [SCNVector3]() for (x,y) in pairs { knobProfile += [ SCNVector3(x: Float(x), y: Float(y), z: 0)] } let nProfiles = 20 let aIncrement: CGFloat = 2 * CGFloat.pi / CGFloat(nProfiles) var knobVertices: [SCNVector3] = [] for i in 0..<nProfiles { let angle = aIncrement * CGFloat(i) let rotatedProfile = knobProfile.map { $0.rotate(about: .y, by: Float(angle)) } knobVertices.append(contentsOf: rotatedProfile) } let source = SCNGeometrySource(vertices: knobVertices) var indices = [UInt16]() let profileCount = knobProfile.count for i in 0..<nProfiles { let nextProfileIndex = (i + 1) % nProfiles for j in 0..<profileCount - 1 { let currentIndex = UInt16(i * profileCount + j) let nextIndex = UInt16(nextProfileIndex * profileCount + j) let nextIndexNext = UInt16(nextProfileIndex * profileCount + j + 1) let currentIndexNext = UInt16(i * profileCount + j + 1) indices.append(contentsOf: [currentIndex, nextIndex, currentIndexNext]) indices.append(contentsOf: [currentIndexNext, nextIndex, nextIndexNext]) } } let element = SCNGeometryElement(indices: indices, primitiveType: .triangles) let surfaceGeometry = SCNGeometry(sources: [source], elements: [element]) let modelMesh = MDLMesh(scnGeometry: surfaceGeometry) let aluminum = SCNMaterial() aluminum.lightingModel = .physicallyBased aluminum.diffuse.contents = UIColor.green aluminum.roughness.contents = 0.2 aluminum.metalness.contents = 0.9 aluminum.isDoubleSided = true surfaceGeometry.materials = [aluminum] //let knobNode = SCNNode(geometry: surfaceGeometry) //return knobNode do{ try modelMesh.makeVerticesUniqueAndReturnError() modelMesh.addNormals(withAttributeNamed: "normal", creaseThreshold: 0.1) let flattenedGeom = SCNGeometry(mdlMesh: modelMesh) let flattenedNode = SCNNode(geometry: flattenedGeom) flattenedNode.geometry?.materials = [aluminum] return flattenedNode }catch{ fatalError("mesh vert error") } }

It's been awhile since I worked with this. I ultimately switched to calculating the normals for more control. Not that I'm a wiz with that stuff. A lot of hacking away. But the vertices need to be referred to uniquely for each face and there is a method for that. do{ try modelMesh.makeVerticesUniqueAndReturnError() modelMesh.addNormals(withAttributeNamed: "normal", creaseThreshold: 0.9) let flattenedGeom = SCNGeometry(mdlMesh: modelMesh) let flattenedNode = SCNNode(geometry: flattenedGeom) flattenedNode.geometry?.materials = [greenMaterial] return flattenedNode }catch{ print("mesh vert error") return node } I didn't try your code as it doesn't include bsplinePath.

I copied the exact same previews and screenshots from the base language to the Brazil localization and the error went away. So yes, there certainly seems to be a bug there. Although it seems that had nothing to do with why Basic doesn't reliably spend.

On the plane, try using .firstMaterial?.lightingModel = .constant I didn't have this exact scenario but I remember solving a display issue with SKTextures in a 3D scene by doing this.

Yes, it does crash on the iPad simulator. It didn't crash for me on the iPhone simulator. Try this: let node = SKShapeNode(rect: CGRect(x: 100, y: 100, width: 100, height: 100)) node.fillColor = .yellow let removeAction = SKAction.run { DispatchQueue.main.async { node.removeFromParent() } } node.run(.sequence([ .fadeOut(withDuration: 5), removeAction])) renderer.overlaySKScene!.addChild(node)

It doesn't crash for me on simulator or device.

Well the issue at least helped me spot and resolve a problem with my ‘resolveConflictingSavedGames’ implementation. It also works correctly on a iPad simulation. Just not the iPhone simulators I’ve tried.

I tried to reply to the comment but character limit. I think "add normals" just literally adds the data for the normal vectors and puts them all at uniform value. It's just iterating through the vertices. You can sharpen or soften a custom mesh with it if you didn't want to create a SCNGeometrySource for normals. I wouldn't say programmatic normal maps are all that easy of a solution. It's just easier than writing your own boolean geometry routines. Have you tried to apply the image to the model? I imagine the image will be shrunken at the top and bottom and ballooned out at the equator. The best way to visualize this may still be to use Blender and create a mockup. See what the resulting maps look like for the look you want. Then that is what you would need to shoot for programmatically. I'm sure there are algorithms for this that can be adapted to Swift without reinventing the wheel.

Boolean mesh functions are a little involved and not part of the frameworks last I checked. Not unless you get into voxels. You might look into applying this as a map instead. Normal maps can give the appearance of depth. It's easier to do this in 3D modeling software such as Blender and import the results. You'll need to understand the relationship of the UV map to the 3D vertices to do this programmatically.

I just canceled the attempt to use Basic. The anonymous TechSupportGPT style replies were less than impressive and took 10 days to make any progress. The max spending was exceeding FB ads and still not spending. They also say one country isn't localized yet it's the exact same process used in all other localizations and they seem hung up on the fact that it uses the screen shots from the default localization. Which they admit is supposed to work that way. And all the other localizations use this without error. No indication in Connect that I need to do anything special for one localization. Just Basic ad's TechSupportGPT copypasta repeating it while seemingly failing to comprehend the questions. And I don't know if I'm talking to an LLM in those emails although they don't deny it. It's either an early version or a bad impression of one. But Apple needs to upgrade whichever they are using.

This is insane. They just keep repeating themselves like a bot? There is no indication that anything I say registers.

You should set the position as well. So you have your bounding box: var min = SCNVector3Zero var max = SCNVector3Zero node.__getBoundingBoxMin(&min, max: &max) The pivot at center: let pivot = SCNMatrix4MakeTranslation( min.x + (max.x - min.x)/2, min.y + (max.y - min.y)/2, min.z + (max.z - min.z)/2 ) This pivot is at x: m41, y: m42, z: m43 let posShift = SCNVector3( pivot.m41, pivot.m42, pivot.m43 ) so node.pivot = pivot node.position = posShift

Yes, I'm not too impressed with their data trickle even when it is working. I don't think their ad services are working either.

Could they be running older iOS versions and your new version requires a later iOS version?

I tried the code awhile back but couldn't get .showStatistics to work in RealtyKit without crashing. Do you know possibe reason for that? I've only tackled draw calls in SceneKit and just now converting one of those projects to RealityKit. I wanted to compare your code with using Clone. Even though it looks like there shouldn't be a difference.