XNA On Windows Phone 7
Download as PPTX, PDF0 likes924 views
This document provides an overview of creating games for Windows Phone 7 using XNA Game Studio. It discusses reasons for using the Windows Phone platform, introduces XNA and basic game programming concepts like the game loop and using textures and sprites. It also covers input handling, trial mode integration, performance optimization, and publishing games to the Windows Phone Marketplace. The document is meant to guide developers through the process of dreaming up an idea, building a prototype, polishing the game, and getting it into players' hands.
XNA On Windows Phone 7
- 2. Learning ObjectivesWhy Windows Phone 7?What is XNA?XNA Game Programming BasicsDream. Build. Play.Next Steps…“The hardest thing about creating your first game is finishing it. – @OwenGoss
- 3. Why Windows Phone 7?
- 4. What is XNA?** Disclaimer: Items are not to scale.
- 5. The Basics“Focus on gameplay! There's no point in having the latest, greatest tech in a game if the gameplay is terrible. - @Justin_Hebert
- 6. The Game LoopInitialize()LoadContent()The LoopUpdate()Draw()UnloadContent()
- 7. Demo #1: Stepping into the Game Loop
- 8. Textures
- 9. Sprites
- 10. Demo #2:Adding Textures and Sprites
- 13. TombstoningFor games, when the Back button is pressed during gameplay, the game can choose to present a pause context menu or dialog or navigate the user to the prior menu screen. Pressing the Back button again while in a paused context menu or dialog closes the menu or dialog.
- 15. Dream
- 16. The Idea
- 17. It could be new…
- 18. …Or a new Twist
- 19. We’re going to borrow an Idea
- 20. Build
- 21. Alien Game LabThree Pillars of Game DevelopmentPrototypePerformancePolishURL: http://hmbl.me/4BSBKO
- 22. Prototyping
- 25. Game State ManagementURL: http://hmbl.me/4BSHGB
- 26. Demo #4:Creating a Screen
- 28. Enums are Handy
- 30. Array vs List
- 31. struct vs class
- 32. Trial ModeAn application must not invoke either of the Trial APIs in a tight loop. For example, a game application must not invoke either of the Trial APIs while in a game loop. The API should be called infrequently and the value returned should be cached bool isTrial = Guide.IsTrialMode;
- 34. Polishing
- 36. Game FeedbackThis requirement does not apply to applications that play sound effects through the Microsoft.Xna.Framework.Audio.SoundEffect class, as sound effects will be mixed with the MediaPlayer. The SoundEffect class should not be used to play background music. SoundEffect alienFired = Content.Load<SoundEffect>("Tank_Fire");alienFired.Play();
- 37. Play
- 38. Side Load
- 40. Next Steps…
- 41. Q & ASorry, I don’t give out Game Ideas
Editor's Notes
- #2: Welcome out to the Windows Phone Developer Briefing:[Intro]- Cory Fowler- ObjectSharp- Games Hobbyist
- #4: Consumer facing PhoneXbox Live IntegrationFamiliar Development StorySilverlightXNAC# or VB.NET
- #5: Brings Managed Code to Games DevelopmentCross Platform Development between ZuneWindows PhoneXbox360Windows 7All on One Code Base
- #7: The XNA Framework like most games runs on a Game LoopInitialization ConstructorLoadContentLoad up main graphics required for gameplayThe LoopUpdateUser input Collection and Calculation of Sprite PositioningDrawRe-Draw the sprites on the ScreenUnloadContentGarbage Collection and Freeing up resources
- #8: Open Visual StudioCreate new Game ProjectReview Code Blocks for The Loop
- #9: Image files which are loaded into a game.There is a good chance that your game with be someone in the ballpark of 60-70% Textures.Your game can only take up 90MB of RAM while running.
- #10: Sprites are images that move independently to the rest of the game.A Sprites position and other attributes are maintained in a instance of a class or struct.
- #11: Add in two Textures and load them onto the screen with SpriteBatch.Draw
- #12: Currently the only Sensor supported by the Phones APIs is the Accelerometer.
- #24: Make sure that your Architecture is part of your prototype.Plan for when the phone is Connected…
- #25: Plan for when the Phone is Disconnected…
- #26: Knowing the Architecture Story of your Game will aid you in Laying out the Flow of your Screens.You can also find the Game State Management Project Template in the Extension Manager.
- #27: Open AlienGame [Start Here] and create Pause ScreenInherit MenuScreenCreate MenuEntry for ResumeCreate MenuEntry for QuitAdd to MenuEntries Collection
- #29: Enums are great for tracking state, which in a game there is a LOT of state.Enumsalso help make your code easier to ready, which allows you to use your brainpower for the Math.Smaller Operating cost than using Strings.
- #30: Boxing is a processing intense operation.
- #31: Arrays – Memory Allocation is going to be consistentList – Basically any hand rolled POCOAvoid - boxed
- #32: structs are optimal for objects up to 16bytes in size and are good candidates for using arrays.Classes are a good choice if the size of the object is going to fluxuaterepetetively
- #33: The Typical response time of this method is 6 MillisecondsShould only be called during Initialize and Activated