Video Presentation : http://tv.adobe.com/watch/max-2013/mastering-multiplayer-stage3d-and-air-game-development-for-mobile-devices/ • The use of Stage3D across web and mobile deployments (with Adobe AIR) . • The challenges encountered when attempting to maintain high-performance specifications on mobile devices . • Being agile in a pre production game development • We'll show how we have jump our of the predefined sandbox to develop creative solution on well known problem.

1. 1

2. Frima Studio
2

3. Session Takeaways
 Iterative pre-production process is good for you
 How to think mobile
 How to keep multiplayer simple
 Flash is still a good option
 Your happiness is important
3

4. Sprint Oriented Session
4

5. Brainstorm Workshop
5

6. Overview - Brainstorm Workshop
 Target device
 Technology to use
 Flash Stage3D vs other technologies
 Past Adobe Timeline recap
 Art adjustment from initial prototype
6

7. Target device
 Cross-Platform
 Web
 iPad2 and up for iOS
 Nexus 7 and up on Android
 Sub-Platforms
 Amazon
 OUYA
 SHIELD
7

8. Android Performance
 30 cycles = 9 FPS
 Epic Citadel
 Shadowgun
 Dead Trigger
8

9. Profiling and Debugging tools
9
Adobe ScoutNVIDIA PerfHUD ES
Intel GPA

10. Technology
 Engine
 Connected backend
 ActionScript programmers
 Seamless ports
 High risks
 Heavily change renderer
 Number of enemies on screen
 Crowd system
10

11. Stage3D GPU Reach
 Stage 3D GPU Reach
 FP11 : 60-70%
 FP11.2 : 70-85%
 FP11.4 : 90%
 WebGL
 WebGL support on mobile is weak
 http://webglstats.com/
 Unity Plugin
 Depends on audience
11

12. Art adjustment
 Art problems
 A guy allergic to peanuts
 Who probably lives with his mother
 Art = later
 Placeholders
12

13. Adobe Gaming Recap
13

14. Brainstorm Conclusion
14
 Recap
 It’s cold where we work
 Target iPad2, Tegra3, Web
 Android GPU performance reality check
 Profiling tools are your friends
 Yes! We use Flash!

15. Disclaimer
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Etiam nibh tortor, posuere in facilisis at, consequat semper leo.
Morbi mauris massa, placerat dictum ultrices sed, pretium et sapien. Donec sed lobortis urna. Aenean malesuada nisl
euismod odio euismod pellentesque. Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis
egestas. Integer fringilla lacus ut erat pulvinar vitae porta risus aliquam. Sed vel suscipit nulla. Donec gravida felis aliquam
mauris rutrum ac luctus est viverra.
Vivamus facilisis, orci ac sollicitudin dignissim, leo risus malesuada eros, nec tempus enim orci quis lacus. Lorem ipsum
dolor sit amet, consectetur adipiscing elit. Nunc eget nunc id nisl ultrices cursus vitae sagittis lectus. Aliquam id lacus lorem.
Aliquam erat volutpat. Aenean eleifend, orci eu tristique suscipit, risus mi vulputate ante, vitae porttitor nisi purus
malesuada velit. Nunc libero magna, iaculis id hendrerit vel, aliquam euismod nisi. Aliquam erat volutpat. Duis vel erat quis
erat posuere fermentum. Integer a libero sed nisi ullamcorper vehicula id sit amet mi. Nullam ornare sollicitudin ante non
dignissim. Quisque vestibulum massa ut mi cursus ut auctor erat sollicitudin. Cras lacinia, neque sed commodo
consectetur, nulla justo facilisis nunc, interdum dictum augue dolor sed dui. In vel dolor magna, eget volutpat ligula. Morbi
vulputate arcu sed mi luctus vehicula. Proin euismod mi sit amet diam commodo mattis.
Donec non dictum elit. In hac habitasse platea dictumst. Integer commodo consequat nibh a luctus. Etiam est lacus, ornare
eu tempus et, tincidunt vitae turpis. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos
himenaeos. Integer pulvinar, erat ut tristique semper, quam justo congue lorem, quis mattis magna sapien at nisi. Cras urna
lectus, blandit quis tincidunt vel, tristique vel urna. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere
cubilia Curae; Phasellus sed purus lectus.
15

16. Sprint I
16

17. Overview – Sprint I
 Feature
 Creep
 Animation Driven Locomotion
 Gameplay
 Placeholder everything
 Attack without animation
 Basic Character movement
17

18. Creep
 Marching square
 Running on Android
 Initial = 150 ms
 Opcode (Azoth) = 20 ms
 8x8 Partitioning (2 - 4 ms)
 64 Meshes and Indexes
 Camera Culling
 uploadfromVector
 uploadFromByteArray
18

20. Character motion (ADL)
 Problem
 Foot sliding
 Solution
 Animation Driven Locomotion
 How
 Tools and exporter
20

21. Foot Sliding
21
 3d Studio Max exporter using AMF C++

22. Power walking
22
 Get the programmer to like it
 Still give control to the designer
 Artist feared it would look
like Power Walking
 Let them control the speed
 Avatar.RunAt(5 km/h).please();
 Animation multiplier

24. Sprint Conclusion
24
 Flash can be fast
 Optimized opcode
 uploadFromByteArray
 Customize your flash experience
 Create plugins in Flash IDE, 3dsmax, Maya
 Connect to Flash with sockets
 Editors
 Debuggers and Profilers.

25. Sprint II
25

26. Frame by frame animation
 Inspired by Quake
 Cons
 Bigger file
 Lots of buffers
 No IK Solver
 Pro
 Faster
26

27. Faster but Why ?
 Skeletal animation
 Each frames
 setProgramConstantsFromByteArray (All bonesId and Weight data)
 Frame by frame
 Longer initialization time
 Each Frame
 Tell which vertex Buffer to use
27

28. Networking in IceField
28
var xml:XML = describeType(cTransform);
…
<variable name="mBaseDamage" type="Number">
<metadata name="Customizable">
<arg key="type" value="decimal"/>
<arg key="label" value="Base Attack Dmg"/>
<arg key="min" value="0"/>
</metadata>
<metadata name="Network"/>
</variable>

29. Networked crowd
 Network everything!
 Easy
 But
 50k/sec
29

30. Networking in IceField
30
 Getter and Setter
 Data synchronisation
 Pre-Processor

31. Sprint Conclusion
31
 Something Old
 In 1996, Quake introduced mdl
 3D spritesheets
 Sometimes a good Pro override many Cons
 Something New
 Networking out of the box
 Gameplay programmers friendly
 Still need tweaking for bandwidth

32. Sprint III
32

33. Overview – Sprint 3
33
More…
More Crowd for me……

34. ZombieTycoon
34
What they remember:
• 2000 Zombies
• Stage3D
What they should…
• Intel i7
• Dedicated video card
And now:
• Mobile
• Networked

35. Crowd
35
 Zombie
 A* on a 2D Grid
 Neema
 Navigation Mesh
 Using Flascc
 Granular flow movement
 Back to 2D Grid
 No A*
 sugar sugar

36. Crowd movement
36
Will not work on

38. Critter mower
38
 Worked but too heavy
 Sword as collider
 Sphere collider
 Solution
 Pre-Computed hits position
 Per Animation
 Per Frame

39. 39
Critter mower

40. Critter mower
40

41. Critter mower
41
For (Crowd pos)
{
Grid[pos]=beiber
}

42. Critter mower
42
For (Hit pos)
{
Grid[pos]=dead
}

43. Avatar
43

44. Sprint Conclusion
44
 Generic technique
 Know them but…
 Do something else
 Mobile > FarCry Requirement

45. Sprint IV
45

46. Multiplayer and networking
 Network tools
 UDP vs TCP
 Peer2Peer
 Network interpolation
 From 50k to 5k / sec
46

47. Latency
 Built-in Network tools
 Latency metrics
47

48. Built-in network metrics
48

49. Network tools
 Microsoft Network Monitor
49

50. Network tools
 Network Emulator for Windows Toolkit
 Latency
 Packet loss
 Network errors
50

51. Network tools
 http://wanem.sourceforge.net/
51

52. Network techniques
 High Bandwidth
 Intervals
 CPU Hog
 Limit packet size
 Latency Kills
 Network interpolation
 Predict position
 Smoother results
52

53. Sprint Conclusion
53
 Make networking behave
 Use networking tools to simulate latency
 Use interpolation for position of moving objects
 Implement networking monitors

54. In the meantime in R&D…
54

55. Using 2D in a 3D game
 Flash Display List
 50% CPU on Android
 Starling
 Easy to Implement
 6% CPU
 Can’t block Click
55

56. ASC 2
56
 Better
 Incremental build by default
 Swf size (-35%)
 Performance (+15%)
 Stricter compilation
var Roger:uint = -1;
var Wilfrid:int = 0xffffffff;

57. Other choices
57
 Red Tamarin
 Updating as we speak
 API on top of Redux
 https://code.google.com/p/redtamarin/
 Play Script
 Away3d and Starling
 First performance test are slow
 http://ingweland.com/playscript-benchmark/
 https://github.com/playscript

58. Less known features
 ANE
 GameCenter
 InApp purchase
 Push Notifications
 Rate this app
 flasCC
 Epic citadel
 Existing Algorithms and codebase
 What about Multithreading?
58

59. GLSLTo AGAL compiler
 GLSL2AGAL
 https://github.com/adobe/glsl2agal
 Existing Shaders
 No need to go low-level!
 Some recent fixes
 Matrixes support (up to 2)
 Dynamic access to vertex constant vc[x]
 Fixed m33 operations
 Fixed nrm on constants
59

60. Stage3D Modes
 Facebook
 https://www.facebook.com/groups/stage3d/
 Extended
 July:
 Rectangular textures
 Texture size : 4096
 What’s next?
 http://www.adobe.com/go/flashplayer_roadmap
 I heard that…
 But…
60

61. Do it !
 Be Agile
 Fail Fast
 Be Proactive
 Create Issues
 Be Different
 Tailor Flash
 Be Creative
 This is The Creativity Conference
61

62. SESSION SURVEY on the MAX COMPANION app
 …for your chance to
 Win e-Books
 Win Apple iPod Nano.
62

63. 63