Note that there are some explanatory texts on larger screens.

plurals
  1. USDevin
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. COThis sounds like the best idea, since I posted this I realized that transitioning between different SKScenes seemed like the best idea. I didn't even think about adding subviews to the view, I just created my own button class as an SKLabelNode subclass, but it does seem to make more sense to do that rather than reinvent everything. Just a pain that I won't fully be able to use storyboards I guess, but not too hard to live with.
      singulars
    2. COSo, just reversed the view controller order like you suggested. I set up a storyboard with a UIViewController and created a segue to a controller containing an SKView. I then called performSegue:withIdentifier: in my first view controller's viewDidLoad so that the SKView was effectively the rootViewController. This worked perfectly, zero lag, even though it had to create a new instance of the SKView to push on top of the stack every time. I am confused.
      singulars
    3. COIt can't be textures, I get this delay even when I don't create a scene and just present a blank SKView. If I go into my storyboard and switch it to a blank UIView, there's zero delay. Then when I switch it back to an SKView, the delay returns even without adding back in the scene setup code. Like I said, I've tested this on both a 4S and a 5 and get the same results. I should have mentioned that I don't see any issues in the simulator, if that's what you're testing it on. I also checked, it's not being deallocated, so that can't be it either. I'll have to try reversing the segue order later.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload