Hi,
I saw something curious today. I have a game that is happily running 60fps in landscape with the Director attached to the window. However, to simplify using UIKit in some scenes I introduced a view controller (ala the suggestion in the documentation) and attached the Director to that view instead.
Everything seems to be working fine and I can even autorotate the game, but now the frame rate is around 40. This is consistent throughout - even on an unanimated main menu scene. I've done CPU sampling and there seems to be no difference in the profiles - almost all the time is spent in CFRunLoopRunInMode (which seems right as it is effectively idling there). There is also no particular difference if I use the fast Director or the normal one.
I've dug around in the Director itself but that just raised another question: how come using the fast director doesn't run faster than 60fps anyway? It looks to be coded to run flat-out so what stops it calling mainloop continuously?
Apologies if either or both these topics have been covered elsewhere. For now I will probably switch back to using the window directly and add transforms to the UIKitLayer but it would be nice to understand why things are happening the way they are.
