New Important People in VR Robert Brackenridge – Virtuix Nathan Burba – Survios Ray Davis – Epic
VC’s to Approach The Venture Reality Fund Envelop VR – Bob Berry Accel – Kobie Fuller prefers tech to games DFJ – Bubby Murarka prefers tech to games Boost VC – Jeff Wasson – is willing to write riskier, smaller checks (aka games). FACT: In 2015 700 million of investment went into vr
How to Succeed in VR
Get market exposure
Have passion about what you are building
Have fresh perspective and be insane when making a VR product ~Kobie
VC’s find it hard to invest in content creation studios – they are not venture scale. VC’s are not looking for story or character.
Games or content success is hard to predict – so make a scalable idea if you want investors
Know the business model of a venture firm before pitching
Be honest and authentic with VCs
Valuation is mostly determined by negotiation in an emerging market for start ups
New Tech to Check Out
Gpuopen.com open source graphics by AMD
Book Recommendation: “Ender’s Game” by Orson Scott Card, if you saw the movie but have not read the book, prepare yourself for a deep exploration of the human survival instinct, warfare, and theory of the mind in what is perhaps Card’s greatest novel.
I recently developed a standardized design process for my team at BrainRush because we had so much design work that it needed to start being distributed to members that were not previously ordained as “designers”.
If you do not create a Design Document before implementing a design, you will find yourself conceptualizing solutions to problems while working rather than just quickly implementing items off of an already solved list. Determining development solutions on the fly can lead to lulls in attention of “what to do next” and make for a slower development process. Of course, a Design Document does not need to be followed in extreme detail, but it certainly serves to expedite the process of implementation and keep a nice record of work progress.
At BrainRush, we follow the Design Document template below to complete a design task: a creative task that a developer must complete before implementing a substantial feature into a game. Design Documents do not work for everyone, but in order for teams to share responsibility, trust one another’s design sensibilities, and maintain transparency of intention, it is always best to have a preconceived set of solutions and tasks before programming, modeling, and developing a feature.
Design Document Requirements:
Written List of Core Design Elements
All of the core pieces of programming functionality required for a design to work from start to finish
All of the art assets that will be required for the design to be visually complete from start to finish
All of the audio assets that will be required for the design to be aurally engaging from start to finish
A paragraph about how all of the programming, art, and audio will work together in the completed state of the design.
A paragraph about major challenges or unknowns that will need to be confronted during the design process
A paragraph about the goals behind the design and what the user will ideally experience with the completed version of the design
Technical Design / Drawings / Flow Charts
A technical design for a strictly programmatic design can be
A highly detailed pseudo code word documents that outlines the functions and variables of each class
A flowchart or diagram for the flow of input data, classes and their relationship to one another, and changes of state that may occur in the application.
A level design, UI design, or 3D Art Design can be
A hand or computer drawn sketch organizing the visual elements with text description of each element
A series of images that represent the different visual states in which a design may appear and how they transition between one another
NOTE: Hand drawn/written documents are encouraged and are to be photographed and uploaded to the design document in addition to written text of sections 1 and 2
Submit the document for manager/peer review
Book Recommendation: “Drawing on the Right Side of the Brain” by Betty Edwards for anyone looking to improve their drawing and perception skills. This book provides foundational insight into how to interpret images you want to draw such that you can break them down into elements and procedures rather than feel overwhelmed by their complexity.
caRPG-13 is the early prototype of a game in which human beings have all become hover cars and consume gas to survive. When a car runs out of gas, it dies just like a human would if it ran out of oxygen or food. Just like humans, these cars can also fall in love. I wanted to make a game where you felt romantic feelings toward a car while struggling to survive in an apocalyptic, resource starved, labyrinthian city. The goal of the game is to reach the top of the city and get into an escape pod before it is too late – time is always ticking and gas is always being spent.
So far, all art assets in caRPG-13 are modified versions from a failed racing game I worked on a year ago – shout out to the artists who made these – you know who you are. The practical thing about using hover cars as humans is that you do not have to worry about animations of any sort, so you can focus on programming other features – in my case I am most interested in NPC AI and character interaction and how they can fit into a game’s design and emotional experience.
I am modeling caRPG-13 off of the famous game Pathologic by using resources vs time to propel the game objectives forward. However, unlike Pathologic which focuses on the simulation of a complex, evolving society, caRPG-13 will focus on character evolution over time and aim to derive narrative meaning out of non-static character interaction.
While Pathologic was a masterpiece, it left a little to be desired in terms of character interaction. With a whole cast of interesting characters all you could do with them was go into one of their houses and talk. These main characters did not move and could not react to you in physical space. In games, it seems that the most common way to interact with characters in a non-violent way is through quests and text trees. While these are a nice staple for storytelling, there are certainly many other ways to build relationships between characters – namely through physical action. What I want to do in caRPG-13 is experiment with a few new types of non-violent interaction between a player and NPC that may enrich the emotional consequences of player agency in the game. In my next blog post, I will talk about the romance that evolves between two lucky cars in caRPG-13. Please subscribe.
Book Recommendation: “The Death of Ivan Ilyich” by Leo Tolstoy, a novella for those who prefer to work hard and make tons of money rather than address their deeper personal issues.
My name is Pablo Leon-Luna. I work at a company called BrainRush in Santa Monica where I develop corporate Unity Games and attempt to build backend web technology using NodeJS. This is how I survive in Los Angeles.
However, when I am not at work I am developing my current game project: CaRPG-13, writing about video games, reading assorted books, and teaching myself to draw. I wanted to write a book called “Mechanics of Dread” inspired by the game Pathologic by Ice Pick Lodge and how it affects the future of games as an art form, but then I realized that writing a book was too much of a time commitment so I am going write this blog instead. Future posts will be about video game theory, software development, tech company culture, and the development of CaRPG-13. At the end of each post I will recommend a book. Please subscribe.
Book Recommendation: “Excavating Kafka” by James Hawes for those who want to explore how history distorts our understanding of an artist’s life and the meaning of his work.