Crowds Control

Artificially intelligent, virtually real

A sample iOS application using Ogre 3D

13 August 2013 // development // masa // reaching for Disqus...

I’m currently working on an iOS demo of MASA LIFE, the AI middleware I’m developping; in fact I’m porting the demo we did for this year’s GDC to iOS. It is called PaperArena, and it is a small capture the flag tank game showcasing the kind of AI you can develop with LIFE. This demo was originally developped for Windows using Ogre 3D.

Paperarena

Long story short, while porting LIFE runtime and the core of the PaperArena code to iOS was quite easy and straightforward, I ran into some problem trying to make Ogre use a UIView that I gave him.

No documentation is available but I found two interesting forum threads, here and there. While providing good base information, none gave a final solution.

After a few hours of work I finally got something running and decided to share it, expecting it might help others and hoping to get some feedback, being neither an Ogre3D nor an iOS expert.

The full repository can be browsed, pulled and forked on github.

The sample

Interesting stuffs

The Objective-C side

The app delegate handles the lifetime of the application, it creates the window, the view controller (from an interface builder file) and start the “simulation”. The windows is passed to the view controller because it is needed to properly initialize the Ogre renderer.

 1 - (void)applicationDidFinishLaunching:(UIApplication *)application
 2 {
 3     self.mWindow = [[UIWindow alloc] initWithFrame:[[UIScreen mainScreen] bounds]];
 4     
 5     self.mViewController = [[ViewController alloc] initWithNibName:@"ViewController" bundle:nil];
 6     
 7     [self.mViewController startWithWindow:self.mWindow];
 8     
 9     [self.mWindow makeKeyAndVisible];
10 }

The view controller start method initializes the OgreApplication, the C++ instance that encapsulate the Ogre context and all the actual “simulation”, in this case.

 1 - (void)startWithWindow:(UIWindow*) window
 2 {
 3     unsigned int width  = self.view.frame.size.width;
 4     unsigned int height = self.view.frame.size.height;
 5     
 6     mOgreView = [[OgreView alloc] initWithFrame:CGRectMake(0,0,width,height)];
 7     [self.view addSubview:mOgreView];
 8 
 9     mApplication.start(window, mOgreView, self, width, height);
10     
11     // Linking the ogre view to the render window
12     mOgreView.mRenderWindow = mApplication.mRenderWindow;
13 
14     // Ogre has created an EAGL2ViewController for the provided mOgreView
15     // and assigned it as the root view controller of the window
16     //
17     // Let's first retrieve it
18     UIViewController* ogreViewController = window.rootViewController;
19     
20     // I want to be the actual root view controller
21     window.rootViewController = self;
22     
23     // But i want to add a child link with the ogre one
24     [self addChildViewController:ogreViewController];
25     
26     // add the ogre view as a sub view
27     [self.view addSubview:mOgreView];
28     [self.view sendSubviewToBack:mOgreView];
29 }

On line 6, a sub-view is created, that is the one actually used by Ogre. I would have preferred to be able to directly create such view in the interface builder and even get rid of the parent view but it Ogre creates its own view controller for it (which I failed to replace) and I wanted to keep my own.

This view uses the custom class OgreView (.h, .mm) that “mimicks” what Ogre is expected as a view, ie. the not exported EAGL2View (.h, .mm).

On line 18, Ogre’s created view controller is retrieved, self then takes back its place as window’s root view controller and a parenting link is created between the two view controllers (should help propagating OS events).

Finally, the Ogre view is attached to the main view and sent to the back for other sub-views to be visible.

The C++ side

On the C++ side, the given pointers are provided when creating Ogre’s render window.

 1 void OgreApplication::start(void* uiWindow, void* uiView, void* uiViewController, unsigned int width, unsigned int height)
 2 {
 3     mRoot = new Ogre::Root("", mResourcesRoot + "ogre.cfg");
 4     m_StaticPluginLoader.load();
 5     
 6     Ogre::NameValuePairList params;
 7     params["colourDepth"] = "32";
 8     params["contentScalingFactor"] = "2.0";
 9     params["FSAA"] = "16";
10     params["Video Mode"] = Ogre::StringConverter::toString(width) + "x" + Ogre::StringConverter::toString(height);
11     params["externalWindowHandle"] = Ogre::StringConverter::toString((unsigned long)uiWindow);
12     params["externalViewHandle"] = Ogre::StringConverter::toString((unsigned long)uiView);
13     params["externalViewController"] = Ogre::StringConverter::toString((unsigned long)uiViewController);
14     
15     // Initialize w/o creating a renderwindow.
16     mRoot->initialise(false, "");
17     
18     // Create the window and attach it to the given UI stuffs.
19     mRenderWindow = mRoot->createRenderWindow("",width,height,true,&params);
20 }

And voilà, everything works as expected!

On top of that, this sample application uses CoreMotion for accelerometer/gyroscope control of the camera as well as touch gestures recognizers and more. Once again it’s available on github.

I’m sure I’ve done some bad stuff and that there is a much simpler way of doing all that. Experts of iOS, experts of Ogre, please let me know, I’ll update the application accordingly!

If you are going to GDC Europe next week (19/08/13 and 20/08/13), drop by and say hi (booth #170 on the GDC expor floor). If all goes well for me, you should be able to play PaperArena on an iPad!

Update - 26/8/13

I’ve updated both the code on github and the post. I was previously setting params["externalViewController"] instead of params["externalViewControllerHandle"] which is the actual good name for the parameters. That was in fact the reason why this piece of code was working.

Furthermore I have discovered that the system doesn’t handle well screen orientation when starting in non portrait mode (e.g. when you set the valid orientations from the settings of the app). This needs further investigation.