[JAVA][Beginning Java 8 Games Development]

More documents

Recommendations

Info

Chapter 16 ■ Collision Detection: Creating SVG Polygons for the Game Actors and Writing Code to Detect Collision Ascertaining Collision Data Optimization: Calculating Data Footprint for SVG Data Let’s figure out our data footprint optimization percentage. The SVG data culled from the file shown in Figure 16-18, and put into the format we will use in our Bagel() constructor method call, can be seen in the top part of Figure 16-19. Mouse-over both iBshape1svg files, seen in Figures 16-19 and 16-20, and get the file size, or right-click on the file, and use a Properties dialog to find the number of bytes in the files. This should be 97 bytes and 1,605 bytes. Figure 16-19. Open folder in your workstation containing the SVG data, and mouse-over file to see the number of bytes Figure 16-20. Mouse-over the original Fuzzy Select Tool generated SVG data to get the data footprint, and do the math 362 www.it-ebooks.info
Chapter 16 ■ Collision Detection: Creating SVG Polygons for the Game Actors and Writing Code to Detect Collision To find out the data footprint optimization, simply divide these numbers into each other. If you divide 97 by 1605 (97/1605=0.0604) you find that 97 is 6% of 1605, giving you a 94% reduction in data footprint. If you divide 1605 by 97 (1605/97=16.546) it means you have reduced the file by 16.546 times, giving a 16.55X data footprint reduction. These are the inverse (1/x) of each other on the calculator, so you can look at it from either direction. So 1605 bytes is 1,655% more data than 97 bytes, or 97 bytes is 6% (or 94% less data) of 1605 bytes. Any way that you look at it, you have just saved your game a whole lot of memory, processing, and JAR file data footprint, and that is only for one of the sprites! Remember that optimizing your collision polygon to use more than 16 times less memory as well as 16 times less CPU processing overhead can be very significant to the smoothness of your game play once you implement collision detection in your game logic, which we are going to do after we take a look at CodeAndWeb’s PhysEd tool. Creating and Optimizing Physics Data: Using PhysEd I want to take a couple of pages to show you an alternative to GIMP that incorporates both physics and collision into a unified game development tool offering that is extremely affordable relative to all that it does for game development. PhysicsEditor, or PhysEd (or PE) is from CodeAndWeb GmbH, a company owned by another Apress author, Andreas Loew, who writes about iOS Game <strong>Development</strong>. Let’s take a quick look at how we would define our sprite’s collision polygon using this professional game development tool, and then we will be ready to get to collision detection coding. Install and launch PE using the green cube PE icon, and use the Import Sprite button shown in Figure 16-21 to open up your sprite1.png file, and use the zoom slider at the bottom of the screen to zoom in 600%, just like we did in GIMP. Figure 16-21. Launch PhysicsEditor and use the Add Sprites button to open the sprite1.png file and zoom into it 600% 363
Page 1:
www.it-ebooks.info
Page 4 and 5:
Contents at a Glance About the Auth
Page 6 and 7:
Introduction The Java Programming L
Page 8 and 9:
■ Introduction In Chapter 13 you
Page 10 and 11:
Chapter 1 ■ Setting Up a Java 8 G
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Chapter 2 Setting Up Your Java 8 ID
Page 28 and 29:
Chapter 2 ■ Setting Up Your Java
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Profiling Your Java 8 Game Applicat
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Chapter 3 ■ A Java 8 Primer: An I
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Chapter 4 ■ An Introduction to Ja
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Chapter 5 An Introduction to Game D
Page 108 and 109:
Chapter 5 ■ An Introduction to Ga
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Chapter 6 The Foundation of Game De
Page 130 and 131:
Chapter 6 ■ The Foundation of Gam
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Chapter 7 The Foundation of Game Pl
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Chapter 8 Creating Your Actor Engin
Page 172 and 173:
Chapter 8 ■ Creating Your Actor E
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Chapter 9 Controlling Your Action F
Page 194 and 195:
Chapter 9 ■ Controlling Your Acti
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Chapter 10 Directing the Cast of Ac
Page 214 and 215:
Chapter 10 ■ Directing the Cast o
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Chapter 11 ■ Moving Your Action F
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Chapter 12 Setting Boundaries for Y
Page 256 and 257:
Chapter 12 ■ Setting Boundaries f
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Chapter 13 ■ Animating Your Actio
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Chapter 14 ■ Setting Up the Game
Page 304 and 305:
Page 306 and 307:
Page 308 and 309:
Page 310 and 311:
Page 312 and 313: Chapter 14 ■ Setting Up the Game
Page 324 and 325: Chapter 15 Implementing Game Audio
Page 326 and 327: Chapter 15 ■ Implementing Game Au
Page 344 and 345: Chapter 16 ■ Collision Detection:
Page 392 and 393: Chapter 17 Enhancing Game Play: Cre
Page 394 and 395: Chapter 17 ■ Enhancing Game Play:
Page 412 and 413:
Chapter 17 ■ Enhancing Game Play:
Page 414 and 415:
Page 416 and 417:
Page 418 and 419:
Page 420 and 421:
Page 422 and 423:
Page 424 and 425:
Page 426 and 427:
Page 428 and 429:
Page 430 and 431:
Page 432 and 433:
Page 434 and 435:
Page 436 and 437:
Page 438 and 439:
Page 440 and 441:
Page 442 and 443:
Page 444 and 445:
Page 446 and 447:
Page 448 and 449:
Page 450 and 451:
Page 452 and 453:
Page 454 and 455:
■ index Background image (cont.)
Page 456 and 457:
■ index InvinciBagel animation (c
Page 458 and 459:
■ index Modifier keywords access
Page 460 and 461:
Beginning Java 8 Games Development
Page 462 and 463:
This Java 8 Game Development book i
Page 464 and 465:
■ Contents NetBeans 8.0 Is User I
Page 466 and 467:
■ Contents ■■Chapter 5: An In
Page 468 and 469:
■ Contents Creating a Hero Superc
Page 470 and 471:
■ Contents Organizing the .update
Page 472 and 473:
■ Contents Optimizing the Scene G
Page 474 and 475:
About the Author Wallace Jackson ha
Page 476:
Acknowledgments I would like to ack
show all

[JAVA][Beginning Java 8 Games Development]

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?