Sorry your browser is not supported!

I've been away for awhile and was last using v1065. I've returned and installed v1076 and started a new project. So I've heard that v1075+ have switched to supporting native orientation ( awesome! ), however I've run into a problem. I looked around and haven't found anything on the forum that's precisely what I'm having trouble with, or I just didn't understand it properly.

I'll keep it simple: I have an app right now that simply detects what orientation the phone is in and prints it out. It reports correctly ( says landscape in landscape and portrait in portrait), however, it doesn't change the way it draws. It still prints out as if it were in portrait mode no matter what.

I've deleted the configuration file since I thought it was deprecated and now the app exits immediately when I run it. I looked through the core.cpp and it looks like it still relies on the config file, but it won't generate a new one...

I assumed that the allowed orientations were all defaulted to 1, but just in case I made a call in the begin method to agk::SetOrienationAllowed(1,1,1,1) to make sure all of them are allowed. This crashes the app.

Is this an AppGameKit issue right now or just something I'm screwing up?

Okay, so I delved a little deeper.

The Core.cpp ( and its header ) are not up to date in the 1076 distribution in the templates folder.

I compared it to the interpreter_android project to find out. I attempted to update it manually, but I think I got some stuff wrong.

Anyway. I'm curious. Does anyone have an updated ( read: fixed ) version of Core.cpp & header?

All the above stuff is solved, however there still seems to be an odd orientation issue.

The device detects an orientation change sooner than AppGameKit does ( which I find odd, because I thought AppGameKit uses the API to detect orientation changes ). So if I rotate only 45 degrees, the screen changes but I have to rotate at least 60 degrees before AppGameKit will detect it and change my aspect ( as my code dictates ).