Your SlideShare is downloading. ×
Advent of the Analytical Artist
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Advent of the Analytical Artist

134
views

Published on

Advent of the Analytical Artist: How Much Code Could a Coding Artist Code if a Coding Artist Could Code Code …

Advent of the Analytical Artist: How Much Code Could a Coding Artist Code if a Coding Artist Could Code Code

First presented at the 2014 East Coast Gaming Conference in Raleigh, NC, USA on Wednesday, April 23rd - "Whether it’s the right brain, left brain argument or the disparate nature of the two groups, artists and engineers often appear to be on opposite ends of the developer spectrum. Often do the two domains brush against each other, and with the ever expanding indie game scene, there is an increasing need for individuals to possess both skills, but what effect does a split focus have on the developer? How much coding ability should an artist have, and how technically artistic does an engineer need to be? This talk explores the intersection of art and engineering."

Published in: Software, Technology, Design

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
134
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. H O W M U C H C O D E C O U L D A C O D I N G A R T I S T C O D E I F A C O D I N G A R T I S T C O U L D C O D E C O D E ? A D V E N T O F T H E A N A LY T I C A L A R T I S T #ArtCode
  • 2. B E N J A M I N TAY L O R G A M E D E V E L O P E R B A C K G R O U N D : • W I T H R E D O C TA N E S I N C E 2 0 0 0 • S T U D I E D G A M E D E V E L O P M E N T AT C A R N E G I E M E L L O N ' S E T C U N D E R J E S S E S C H E L L ( T H E A R T O F G A M E D E S I G N ) • A R T D I R E C T O R , W I L L W R I G H T ' S S T U P I D F U N C L U B • G A M E E N G I N E E R , S I M C I T Y, E A M A X I S • G A M E E N G I N E E R , U N A N N O U N C E D , N E X O N
  • 3. B E N J A M I N TAY L O R G A M E D E V E L O P E R B A C K G R O U N D : • W I T H R E D O C TA N E S I N C E 2 0 0 0 • S T U D I E D G A M E D E V E L O P M E N T AT C A R N E G I E M E L L O N ' S E T C U N D E R J E S S E S C H E L L ( T H E A R T O F G A M E D E S I G N ) • A R T D I R E C T O R , W I L L W R I G H T ' S S T U P I D F U N C L U B • G A M E E N G I N E E R , S I M C I T Y, E A M A X I S • G A M E E N G I N E E R , U N A N N O U N C E D , N E X O N G A M E D E V E L O P E R T R A N S L AT O R
  • 4. E N G I N E E R I ’ V E W O R K E D A S A N A R T I S T A N D A S A N Adelaide ‘08Seoul ‘11
  • 5. U N D E R S TA N D I N G S Y N TA X Coding “Language” P E T E R PA U L R U B E N S M A R K R O T H K O A L E X R O S S
  • 6. A D V E N T O F T H E A N A LY T I C A L A R T I S T O B J E C T I V E N E S S RISK A RT E N G I N E E R I N D I E A A A
  • 7. Q U E S T I O N S F O R T H I S TA L K A D V E N T O F T H E A N A LY T I C A L A R T I S T W H AT D O I N E E D T O K N O W ? H O W C A N I B E M O R E C R E AT I V E ? H O W M U C H S H O U L D I K N O W ?
  • 8. T H E PAT H T O U N D E R S TA N D I N G A D V E N T O F T H E A N A LY T I C A L A R T I S T
  • 9. T E A C H M E H O W T O C O D E S H U T U P A N D
  • 10. W H E R E T O S TA R T • Start Visual • Reduced Friction in Deployment • “Object-Oriented” • Add Interactions to Initial Object • Create Other Objects and Define Relationships
  • 11. Y O U R S E L F rect( ) C H E C K Y O U R S E L F B E F O R E Y O U
  • 12. T H E R E C TA N G L E • Many languages provide built in graphics libraries. • The rect( ) function takes 4 arguments: x, y, width, and height. • A draw function will use the rect information to render a rectangle.
  • 13. W H E R E T O S TA R T • Start Visual • Reduced Friction in Deployment • “Object-Oriented” • Add Interactions to Initial Object • Create Other Objects and Define Relationships
  • 14. O N T H E R U N • WYSIWYG (“What you see is what you get”) - ex: Adobe Dreamweaver • Consider using a template • Check the console / debug log for bugs • Hung up? Use print( ) or trace( ) functions.
  • 15. W H E R E T O S TA R T • Start Visual • Reduced Friction in Deployment • “Object-Oriented” • Add Interactions to Initial Object • Create Other Objects and Define Relationships
  • 16. B E F O R E A F T E R T H I N K F U N D A M E N TA L LY • Scaffold • Start with general concepts / broad strokes • ex: a Character object • Enemies as well as the Player are a type of Character • Slowly add fidelity / details
  • 17. W H E R E T O S TA R T • Start Visual • Reduced Friction in Deployment • “Object-Oriented” • Add Interactions to Initial Object • Create Other Objects and Define Relationships
  • 18. T H E K E Y T O I N P U T • First create the action and have it deploy at runtime. • Then map that action to an input, such as a keystroke, mouse movement, etc. • There are often libraries included for input, and you can add more! • Not a game until its interactive
  • 19. W H E R E T O S TA R T • Start Visual • Reduced Friction in Deployment • “Object-Oriented” • Add Interactions to Initial Object • Create Other Objects and Define Relationships
  • 20. C O N D I T I O N E D F O R S U C C E S S • Conditional statements: if(true){“do something”} • Collisions, limits, return • Create a “listener” in your object. • Loops, tests, switch and check methods
  • 21. A N D E X P L A I N T H I S poly tri W E S H O U L D
  • 22. T H E T R I A N G L E • aka Polygon, sometimes shortened to “poly” or “tri” • Fundamental building block of game art • How a GPU “thinks” • Also a unit of measurement
  • 23. 20k tri’s = 1 poly mesh = 1 Leon
  • 24. S C I E N C E I N F O R M E D A B I L I T Y
  • 25. S U M M E R P R O G R A M M I N G C O U R S E P E N N S TAT E U N I V E R S I T Y 1 9 9 2 W H E R E I S TA R T E D :
  • 26. S N A K E , W R I T T E N I N Q B A S I C T H A T V I S U A L C A M E F R O M T H I S C O D E :
  • 27. A C A S E A G A I N S T K N O W L E D G E A D V E N T O F T H E A N A LY T I C A L A R T I S T
  • 28. M A G I C U N I N F O R M E D A B I L I T Y
  • 29. I N T E R S E C T I O N O F A R T A N D E N G I N E E R I N G C A R N E G I E M E L L O N ’ S A R C H I T E C T U R E P R E C O L L E G E , I N S E A R C H O F T H E
  • 30. A R C H I T E C T I N 2 0 0 2 , I WA N T E D T O B E A N
  • 31. TA S S O K AT S E L A S M E E T I N G M Y H E R O
  • 32. – TA S S O K AT S E L A S , T O M E I N 2 0 0 2 “Don’t become an architect.”
  • 33. • Tasso was an artist. • The distinctive castle-like brick buildings of Pittsburgh were designed by Katselas. • …but they weren’t built by him. • The age of the architect was over in his mind.
  • 34. T R U S T, FA I T H , A N D O T H E R O L D FA S H I O N E D I D E A S • Most don’t want to know. • You don’t have to know everything to be good. • You can’t know everything. • People love to be surprised.
  • 35. S C I E N C E I S M A G I C E X P L A I N E D
  • 36. T H E C O S T O F C R E AT I V I T Y A D V E N T O F T H E A N A LY T I C A L A R T I S T Aristotle Plato The School of Athens - Raphael Socrates
  • 37. S O R C E RY U N I N H I B I T E D I N V E N T I V E N E S S
  • 38. S T I L L P U N I S H A B L E M O R E T H A N 2 M I L L E N N I A L AT E R • Dangerous Ideas • One: Corrupting the Youth • Two: Impiety • The games industry has been the scape goat of entertainment media for decades. Why?
  • 39. I S I T E T H I C A L T O L E A D S O M E O N E A S T R AY F O R T H E E X T R A D ATA P O I N T ? Q U E S T I O N :
  • 40. D O N ’ T W E WA N T C H A N G E ? • Afraid to offend. • Reluctant to talk. • Trying to find comfort in an uncomfortable world. • Interactions are becoming shallower and shallower.
  • 41. T O B E W E I R D I S T O B E E V I L • It’s an innovator’s job to invent the future. • The games industry isn’t run by innovators. • Indies can innovate, but only should to a small extent if they want to be accepted.
  • 42. N O N - O B J E C T I V E A R T O U T O F T H E E T H E R
  • 43. – H E N RY F O R D “If I had asked people what they wanted, they would have said faster horses.”
  • 44. E N O U G H T O … U N D E R S TA N D D O M A I N S M I T I G AT E R I S K V E N T U R E B U T S T I L L …
  • 45. I N S P I R I N G A G E N E R AT I O N R U N T H E R I S K O F A T Y O U R E X P E N S E
  • 46. K N O W T H Y S E L F A D V E N T O F T H E A N A LY T I C A L A R T I S T
  • 47. – A S S O C I AT I O N F O R C O M P U T I N G M A C H I N E RY, 1 9 5 9 "If computer programming is to become an important part of computer research and development, a transition of programming from an art to a disciplined science must be effected."
  • 48. K N O W - I T- A L L I N F O R M E D B U T R E S T R I C T E D P I G E O N H O L E D F O C U S E D B U T U N I N F O R M E D D A N G E R O U S O U T- O F - T O U C H B U T U N I Q U E A N D O R I G I N A L
  • 49. A L L O F T H E S E PAT H S L E A D T O N E W H O R I Z O N S U N D E R S TA N D T H A T
  • 50. C H O O S E Y O U R P O I S O N A D V E N T O F T H E A N A LY T I C A L A R T I S T
  • 51. T H A N K Y O U ! @Benjamin_Taylor Post your thoughts on the topic via Twitter with the hashtag #ArtCode

×