SKTexture.cgImage() smaller than SKTexture

It would seem that updating my devices to iOS 12.2 broke this. SKTexture.cgImage() used to return an image the same size as the texture, but now it only returns the visible size of the image. So infuriating!!!

Can anybody please tell me how I now get the full size image?

I've come across this issue too and after investigation identified the following:

1. The issue only occurs for images stored in a Sprite Atlas/TextureAtlas.

2. The issue only occurs when running on Metal hardware. It doesn't occur when running on the Simulator or older hardware that doesn't support Metal (actually not sure about the older hardware, as my older hardware is on iOS < 12.2).

3. The issue only occurs when creating an SKTexture using the filename initialiser SKTexture(imageNamed: String) or SKTextureAtlas.textureNamed(_ name: String). So depending on the context you may be able to work around the problem by using the SKTexture(image: UIImage) initialiser instead, something like:

if let textureImage = UIImage(named: "textureName") {
     let texture = SKTexture(image: textureImage)
     // Do something with the texture
}

Except that this uses a lot of memory and isn't a solution for me.

This is a pretty big problem if you're creating an SKPhysicsBody using a texture (which is what led me here). The physics body is being created using the texture that's been cropped in size to visible pixels, but texture.size() gives you the uncropped dimensions, so if you pass that size to the physics body initialiser then the body gets scaled up to fit. This creates a physics body that doesn't match the texture used to generate it.

Thanks for the reply, I was beginning to think I was alone lol

I've used something similar to your suggestion as a workaround. The annoying part of my particular usage problem is that I am using the TileSet sks editor in Xcode to create a long list of SKTileGroup SKTileGroupRule / SKTileDefinition / SKTextures, which are then being used to design my game levels upon a SKTileMapNode, again all in Xcode. So the SKTexture objects are all created for me. I have no choice as to how the SKTexture objects get created, unless I actually construct my game levels using code and none of WYSIWYG features that are available. If I had to do that, tbh, I'd abandon the whole project.

Even getting the image name from the SKTexture was problematic, but I ended up using this hacky way for now...

public extension SKTexture
{
  func GetImageName() -> String
  {
       return description.components(separatedBy: "'")[1];
  }
}

Then for each SKTileDefinition in my TileSet I had to do this...

  var TextureList : [SKTexture] = [SKTexture]();
  TextureList.append(contentsOf: TileDef.textures);

  TileDef.textures.removeAll();

  for Texture : SKTexture in TextureList
  {
    let Image : CGImage = UIImage(named: Texture.GetImageName())!.cgImage!;

    let NewTexture : SKTexture = SKTexture(cgImage: Image);

    TileDef.textures.append(NewTexture);
  }

...which basically removes all the textures from the SKTileDefinition called TileDef, and recreates them by loading a UIImage using the image name retrieved by my GetImageName() extension above. Feels really hacky and wrong because I know the images have already been loaded for me, but can't figure out any alternatives.

I've also tried updating my device (an iPad mini) to iOS 12.3 beta in case it's just an iOS 12.2 thing, but unfortunately the normal way of doing this is still broken in that.

I do hope they fix it soon, because I've little confidence in my hacky solution always working as it depends on parsing thet description.

Yeah, no satisfactory workaround. Watch your peak memory usage when using UIImage to initialise a lot of textures too, it seems to circumvent the benefits of using a texture atlas. Same issue is described in this Open Radar from 2015 https://openradar.appspot.com/22496050

Maybe a change in the Metal conversion of Spritekit has reverted a problem?

Better submit a bug report.