Following on from my previous article we don the rubber gloves and grab Zeus’s lightning bolt to launch it on other platforms.

Not cryptic enough for you then read on

We left off just porting Michael Hoffman’s excellent article showing us how to generate lightning effects almost effortlessly using XNA over to MonoGame in minutes, however (as I usually do) I felt it didn’t just go far enough, sure Windows desktop is fine but MonoGame V3 now gives us entry to Windows 8 / RT and Windows Phone for FREE with paid options for other platforms.

Also where we had a working project, I wouldn’t call it a solution as I’d have to repeat that process for each platform and maintain them separately which is not ideal, so let’s kick  it up a notch and make this more shocking!!!!!

Source for the series can be found here on codeplex as well as the code drop for this stage here

# Going Portable

First problem we need to address is to separate our content / game from our project, following a kind of MVC / MVVM / MVP style of architecture but for games, all we should have in our main “game” project is what we need to actually RUN the game and start painting to the screen.  This will make more sense in the SunBurn portion of this series but will aid us as we go multi-platform with MonoGame.

To begin add a new project to our VS 2010 solution (yes, we will get on to VS2012 shortly!! just hang on) for a Class library (We should use a Portable Class library project but cannot for two factors, this project needs a lot of graphical references at present and MonoGame doesn’t have  PCL version, yet).

So add the new Class library project to your solution: and call it “MonoGameLightningDemoLib”:

Next move all the code files from the original game solution over to our new lass Library except for Game and Program, to be more specific move these files:

Art.cs
BranchLightning.cs
ColorUtil.cs
ILightning.cs
LightningBolt.cs
LightningText.cs

If you drag then over in Visual Studio be sure to remove the old files from the original project as VS will just copy them instead of move them.

This has moved the core of the guts of the solution to a separate project so we can manage it separately just leaving the Game.cs code to run the game handling the graphics device, spritebatch’s and so on.

We’re not done yet as you still need to tidy up a few things, first off go and update all the namespaces in the new class library for the files above to match the libraries namespace, in my case you go from “MonoGameLightningDemo1” to “MonoGameLightningDemoLib”.  Next let’s sort out the references:

Add a solution reference from the game project to the lib project
Add a reference to the “MonoGame Windows OpenGL” dll in the library project (careful you get the right one)

(Check you select the correct version by looking at it’ source directory as ALL releases now have the same name!!)

To finish up now update the game1.cs and add a new using statement so that the Game class knows where to find the effect/game code:

using MonoGameLightningDemoLib;

Just check and build the project now and it should run as before

I did plan to add multi-touch support to the windows project but it’s unable to recognise touch or gesture events from my machine, could be a simple thing but haven’t had the time to play with it, but it’s coming up and works perfectly on phone and Windows 8 / RT

# Bring in the 8 ball

Now one of the amazing things the MonoGame team brought in with the latest update to version 3 was to add on Content Builder support into VS 2012, granted you will need to install the latest Phone 8 SDK to enable it (as that’s where the content project support comes from) and now you no longer need to spin up VS2010 to actually build content, BIG DEAL!!

Now I’m not going to re-iterate what has already been said, so if you look back at the last article, go and do the following in Visual Studio 2012:

Create a new “MonoGame Windows Store Project” or a “MonoGame Windows Store (XAML) Project  – up  to you
Add a new “MonoGame Content Project” to the solution
Add a “Windows Store Class Library” project to the solution called “MonoGameLightningDemoLib” (or the same as you called the last one)
Add a reference from the Game project to the Lib project
Add a reference to the “MonoGame Widows 8” dll to the Lib project

Now we have a blank Windows 8 solution ready to receive all the content we’ve created already.

With the solution setup we just need to bring in our assets and engine/effect code as is from our existing Windows project, as we did before with the compiled content files we are just going to link to our existing assets.

*Note (lots of these here )

you will probably see the following error message when you open a Windows Store / XAML project in VS2012 with a MonoGame “Content Builder” project in your solution, just ignore it everything is fine..

First right click in the Content project and do “Add Existing Item”, then browse to the un-compiled source content from the previous solution (the png’s and spritefont files), this puts our content in place for building (ensuring you also set the “Build Action” to “Content” again!!).  Next do the same again but this time in the Lib Project and link the code files from the Class Library project we created earlier.

*Note

In both cases be sure to “Add as Link” the files else you are just going to end up with copies everywhere.  An easy sanity test is to look in the directory where the projects are after doing the link and you should find the directories empty.

With everything in place you now just need to repeat the exercise from the last article to copy over the relevant sections in the game1.cs to your new solution (the native part of the project), ensuring to add the additional Using statement to the top of the game1.cs file as above:

*Note

In some cases when I tested this, Visual Studio did not recognise the reference to the code in the Lib project, but on building it was fine. Basically test it and if it works then don’t worry about it

You should now end up with a project looking something like this:

All that’s left is to add the built content files from the Content Builder Project and you’re done.

If you run the project you can now click around as much as you like creating bolts on your Windows 8 machine in the new modern interface.

*Note

For some reason the click position reported by MonoGame seems to be off, could be the code for the original sample but I’ve not looked too deep into it at this point

Source for the series can be found here on codeplex as well as the code drop for this stage here

# Emperor Palpatine enters the room, now bow!!!

Now one lightning bolt is nice but let’s go mental and draw lightning from our fingers, Windows 8 and Windows phone are multi-touch devices after all (4 touches with phone, 10 – 20 with Windows 8)

Adding multi-touch with any XNA project is very simple thankfully, first just a using statement to the “Microsoft.Xna.Framework.Input.Touch” domain to the top of the game1.cs class file:

using Microsoft.Xna.Framework.Input.Touch;

Next we need some state parameters for the touch events, similar to handling the mouse and keyboard.

TouchCollection touches, previousTouches;

We need this or another method so that we can control how many bolts are generated between our touch points, I usually prefer a pool based system but this is effective enough to get the picture.

Finally we just need the code in our Update loop to monitor for touches and strike up the match between each finger:

previousTouches = touches;
touches = TouchPanel.GetState();
for (int i = 0; i < touches.Count; i++)
{
if (touches.State != TouchLocationState.Pressed)
{
continue;
}
if (touches.Count == 1)
{
}
else
{
if(i > 0)
}
}

Now with everything now in place when you run the project and upon touching the screen with several fingers

Feel free to play with the source, for a laugh try using just the touch points directly and discover why a limiting factor is needed, I brought my powerful ultrabook to its knees with a couple of fingers , but some really bright shiny effects.

Source for the series can be found here on codeplex as well as the code drop for this final stage here

# Wrap Up

That wraps it up for the MonoGame variant of this electrifying article, next up how to get the same effects using the upcoming SunBurn Platform API

Stay tuned