Robot Foot Games Helping you improve your games as we improve our own. :)

30May/1114

Saving/Loading using EasyStorage with XNA 4.0

This tutorial is made with XNA version 4.0. If you're still using 3.1 you can use this tutorial (which is a little outdated (Nov '09) but it should work).

Trying to get saving and loading to work on a 360 can be a pain at first, but it's pretty easy as long as you set it up correctly. I'm using Nick Gravelyn's EasyStorage which you'll have to download in order to follow along (I'm using changeset 57440 for this tutorial so grab that version for best compatibility). I'm going to create a mock-up game using the Xbox 360 Game State Management (4.0 version) to try and make this more accessible to everyone instead of using the Platformer Starter Kit like in the previous tutorial. You should be able to rip all of the saving/loading code straight from here and drop it into your own game.A good suggestion if you're on the newer side is to go through this tutorial and get it working in a blank copy of the Xbox 360 Game State Management example BEFORE you try to just drop it into your game. Once you get it working you'll get a little confidence boost and you'll have some understanding of how it works.


 

Adding the files to your project

First off, we need to transfer all of the necessary files to our blank copy of the GSM (game state management). All you have to do is drag the EasyStorage folder (found at GS4 > EasyStorage in the download above) to the very base of your project. Your base folder should look like this after the move. I named the blank copy of the Xbox 360 GSM "EasyStorage_4.0" so whatever you named your project will show up there instead.

EasyStorageFolder

Inside of Visual Studio we need to add the project and add a reference to it. In the solution explorer right click on the VERY TOP item (mine's named "Solution 'EasyStorage_4.0'"). Navigate to Add > Existing Project... > (find the location of the EasyStorage folder that you moved in the step above) EasyStorage > EasyStorage [Xbox].csproj. When you select that you should see a "EasyStorage [Xbox]" project along side the others.

Let's add the reference now. In the solution explorer expand your main project ("EasyStorage_4.0" for me) and right click on the "References" folder. Click on Add Reference and when the popup opens click on the Projects tab at the top. You should see 'EasyStorage [Xbox]' and just add that. We can move onto setting up our game now.

NOTE: The EasyStorage folder also contains projects for windows and windows phone but we're just focusing on Xbox for this tutorial. If you're also making a windows or windows phone copy of the game you'll have to repeat the step above and add the specific projects and references.


 

Global.cs

I like to create a Global.cs class and store the save device in there so I can save/load wherever in my code I want. Right click on your main project and Add > Class. Name it Global.cs and replace everything in the file with the code below:

 

The comments should explain what each value does. The basic gist is that you should only have one container but you can have multiple files within that save container which allows your code to be much more organized.


 

PressStartScreen.cs

Now we have the framework laid out and we just have to set our SaveDevice before we can use it. I have the following code in my 'Press start to begin' screen which should be a part of any game because you can also find out which controller is controlling everything. Nick Gravelyn has an awesome example of how to support multiple controllers here. You need to make a new class in your Screens folder called "PressStartScreen.cs" and replace the contents of that with the class below.

 

Once you have this new file in your game you'll need to go into Game.cs and find the line that says

and change it to

 

Now when your game starts you'll be presented with a 'Press Start to begin' screen. When you press A or Start it prompts you to choose a storage device and the main menu screen is created. NOTE!! If you only have ONE storage device connected (Ex: you have a hard drive and no memory cards) then you won't get a popup at all, it will automatically choose the storage device found in the background (unaware to you).

A few notes about the above code, because there's a lot going on that will confuse you if you don't understand it. When you hit Start or A it calls the "PromptMe()" method which handles setting up the save device. If you have only the hard drive connected to your Xbox then it will seem like nothing happened because it chooses that automatically. If you have multiple storage devices plugged in (hard drive, memory card) then you will get a pop-up asking you to choose a storage device. Look at the 2 lines in the PromptMe method that end with SaveDeviceEventResponse.Force. SaveDeviceEventResponse has 3 different arguments that you can use:

  • Nothing means nothing happens if you cancel the device selector screen. No save device will be chosen and you won't be able to save anything later on.
  • Prompt means it will ask you to either choose a storage device, or continue without saving.
  • Force means that you MUST choose a save device in order to continue. No ifs, ands or butts about it!

If you chose Prompt or Force and you remove the memory card (if that's the storage device you chose) you'll get a popup saying something along the lines of "reselect your storage device." If you chose Nothing and remove the memory card your game may crash when it tries to save again.

 

Finally, when we select the save device (sharedSaveDevice.DeviceSelected) we assign Global.SaveDevice to the save device so we have access to it later when we want to save/load. We also load the main menu when they choose a device.ANOTHER NOTE! If you change the SaveDeviceEventResponse to Prompt or Nothing and you don't choose a save device the menu won't load. This is because we have the code for loading the main menu inside the block of code for when our save device gets selected. You'll have to modify this if you want to allow users to continue w/o a save device.

 

MORE NOTES: I've always used SharedSaveDevice which means 1 save per Xbox. If you want different gamertags to have their own save games you'll have to use a PlayerSaveDevice instead of SharedSaveDevice.


 

OptionsMenuScreen.cs

If you're working in a copy of the Xbox 360 Game State Management then you should have a file called "OptionsMenuScreen.cs" in your Screens folder. Open that up because we're going to change it up so you can save your game options. I'm just going to use the default options they give us but in reality you might have options in here to change the volume of your sounds or select some preferences.

 

Inside of the constructor (public OptionsMenuScreen()...) method let's add this block of code to the VERY bottom (we can also remove the FIRST "SetMenuEntryText();" call since we call it after we try loading previous values):

 

You'll also need to add "using System.IO;" to the top.

 

Since everything that we're trying to read is a string we need to convert it to the same type as the variable we're setting it to. That's where values like "int.Parse(...)" and "bool.Parse(...)" come from. The first one converts the string to an integer while bool.Parse(...) converts the string to a bool.

 

Now that we can load values, we need to add our save functionality! We're going to save when the user backs out of this screen (by pressing B or pressing the Back button) so we need to override the OnCancel method. Add this in the Handle Input region if you still have it, or just add it underneath the constructor.

 

NOTE: I didn't deal with saving/loading the "Ungulate" variable so that will also default to the initial value when you try it.


 

And that's everything! Here's a couple suggestions to keep everything organized.

  • When saving/loading stuff we're writing/reading from a file. The first value you write MUST be the first value you read. When writing this I accidentally wrote 4 lines to the file (saving) and when I tried reading them (loading) the order was messed up. I had to delete my save file and fix the order to get it to work again.
  • When you move to saving game data make a new file name in the Global.cs file (I have a couple examples commented out in there) and just move the saving/loading examples in OptionsMenuScreen.cs into the file where you're working with your game code. All you'll have to do is change "Global.fileName_options" in the save/load arguments to your new name and change what you're reading/writing.

 

I know this can be pretty confusing at first, but once you finally get it, it'll be smooth sailing from there on!

 

Comments (14) Trackbacks (0)
  1. This was super helpful–the first actually understandable reader I’ve seen so far! Thanks so much!

    The only thing I would suggest would be to have the project name be something like TUTORIAL GAME or something. Naming it Easy Storage and having to drag the Easy Storage 4.0 files into the folder made the image very confusing–which was I dragging where?

    • The name of the project is EasyStorage4.0 and you drag the Easy Storage folder into that from wherever you downloaded it from. I’ll have to go through it sometime and make the naming convention a little easier to understand.

      • Jeff–Yes, I understood the differences between the two, it just took a little while to figure whether your solution was Easy Storage or Easy Storage 4.0. Either way, this was still by far the clearest tutorial on how to save on the xbox that I’ve seen yet. Thanks for doing this!

  2. Would this work for XNA development on PC, besides the XBox and Windows phone?

  3. Most helpful documentation on understanding how to save/load files. I was wondering, could we not have used e.PlayerIndex in PressStartScreen.cs to figure out which player is the one starting the game. like so:
    {
    PromptMe(e.PlayerIndex);
    }
    private void PromptMe(PlayerIndex playerIndex)
    {

    ScreenManager.AddScreen(new MainMenuScreen(), playerIndex);

    }

  4. Hi, nice article I’m trying to implement this and am getting the following error:
    Object reference not set to an instance of an object.
    on this line
    if (Global.SaveDevice.FileExists(Global.containerName, Global.fileName_options))

    Also – I’m confused as to what the containerName is – is this a folder in the savedevice which the file is saved in? how is this assigned outside the global.cs?
    public static string containerName = “YourGame_Save”;

    Thanks.

    • The containerName is the name of the save file so when you look for the save, it’ll show up as “YourGame_Save” so it’s probably a good idea to change it. As for that error, it sounds like you’re not assigning something properly. Does your Global.cs file have a ‘containerName’ and ‘fileName_options’ variable? You can feel free to change the name of those variables to something that’s more understandable for you, just make sure you change it wherever else you wrote it.

      • Thanks I see, so ‘containerName’ is the actual file (e.g. txt) and ‘fileName_options’ is basically a (e.g. string) header name within that file?

        You’re right on the error is wasn’t assigned prior to use, I was also running/looking for the file on PC but realised this works on XBOX – I can see the file now on the memory stick.

        I’m trying to get this to load/save from a struct of high score data – playername, score, level – like a top 20 list and then display on screen using spritebatch – do you have any tips? How do I pass data lists and then read and display.

  5. Arrggghhh…….why so compicated, why XNA does not just have a class with to methods:
    InputStream RedaFile(string filename)
    void WriteFile(string filename, OutputStream outp)

    and all stuff like “disconnected USB while running game” will be handeled correctly by default, and if you wish u could change it , but if you don’t want to loose time you just can use theese two methods

    • That’s why there’s tutorials like this one. :) Anyways, a simple, built in, component like you mentioned would still need customizing/modifying to work properly in everyones’ games. Doing the implementation/research yourself makes sure you know how it works fundamentally so if you encounter a problem you have an idea on how/why it happened so you can fix it.

  6. Hi Jeff, first of all thanks for these great tutorials, you’ve taught me alot and really helped me get into and understand XNA.

    My question is in regards to the game crashing if the player removes the MU after being forced to choose a storage device, would that crash mean that the game gets a fail in peer review? If so how would you go about solving that problem?

    • A crash in any location will cause your game to fail. It sounds like you might be saving/loading something and not using a Try/Catch block when you remove the MU. Whenever you attempt to save or load data make sure to use something like the following:
      try
      {
      //attempt to save data
      }
      catch ()
      {
      //if something went wrong, we end up in here
      }


Leave a comment

(required)

No trackbacks yet.