A Tale Of Ten SDKs: Cross-Platform Development Best Practices - Unite LA
Download as PPTX, PDF2 likes280 views
This document discusses best practices for cross-platform game development across 10 SDKs. It recommends testing early on all target platforms, planning for the widest range of hardware specs, using polymorphism to share common patterns between platforms, automating build processes, and considering unique platform features. The document also provides tips for console development, such as starting the application process 12 months before release, choosing a supported Unity version, and reviewing certification documentation early.
A Tale Of Ten SDKs: Cross-Platform Development Best Practices - Unite LA
- 1. A Tale of Ten SDKs: Cross-Platform Development Best Practices Bryant Cannon Lead Developer Night School Studio @LaserCannon
- 5. Why port to so many platforms? • Expand the capabilities of your game • Give customers multiple ways to play • Get your game to the largest audience possible!
- 6. Tip #1: Test early and often Don’t make porting a last minute task! Makes it easier to know: 1. What’s my minimum spec? 2. What are the differences? 3. What are the complications?
- 7. Night School Solution: •Run on platform very early. •Run on platform in build reviews • Rotate platforms if necessary
- 8. Tip #2: Plan for you spec range Identify strongest and weakest platforms Plan EVERY resource-intensive feature to scale for both (The wider the gap, the more time you’ll need)
- 9. Night School Solution Quality Monitor: • Responder class notifies anything of a quality settings change • Example: a behavior that turns off a transparent object qualityMonitor.onQualityChanged • We set up special Quality settings for each console/mobile platform
- 10. Tip #3: Use Polymorphism Find the common patterns between each platform “User” “SaveManager “Achievement”
- 11. Tip #3: Use Polymorphism Don’t do what we did on Oxenfree:
- 13. GameInstancing AfterpartyGameController ZB4PlatformController AfterpartyGameInstance Game ZB4SaveMgr ZB4UserMgr ZB4PresMgr
- 14. Tip #4: Automate Build Processes Try to keep builds to a one-click operation • Minimize the amount of steps to build • Write a batch build script
- 16. Night School Solution BuildScheme Asset that contains build configuration data such as: • #defines • Platform keys • Level list • Compilation options • And more!
- 17. Tip #5: Consider unique platform features Goal: make each port feel like it was specifically designed for that platform. • HD rumble • Controller speakers • Network connectivity • Touch screen
- 19. Console development 101 • Begin the application process 12 months before your release date. • Download the tools and familiarize yourself as early as possible.
- 20. Console development 101 What you’ll need: • Platform SDK • Unity platform support module • Platform plugins for Unity
- 21. Console development 101 Deciding on a Unity version, consider: • Is your Unity version currently available for this platform? • What version of the SDK is needed by this version of Unity? • Will this version of the SDK still be supported for submission?
- 22. Console development 101 Day School Studio Game: Battlefire 3 Platform: Zbox 4 My Unity version: 2017.3.1 Unity 2017.3.1 Zbox 4 SDK v3.06
- 23. Console development 101 Zbox 4 SDK Version Unity version OK to submit 1.0.0 Unity 2.6.0 NO 2.0.0 Unity 5.6.1p3 NO 2.0.7 Unity 2017.1.0 NO 3.0.0 Unity 2017.2.0 NO 3.0.6 Unity 2017.3.1 NO 4.0.0 Unity 2018.1.0 YES 5.0.0 Unity 2018.1.1 YES
- 24. Console development 101 Plugins: • Consider Async functionality • Familiarize yourself with the functionality of each • Keep track of the plugin version
- 25. Console Development 101 Read certification documentation early! • Identify the requirements that apply to you • Identify the requirements that contradict your design goals