Quotes of All Topics . Occasions . Authors
It is clearly a bad idea to try to just move games from other platforms directly over, but I'm sure we will see a lot of it, especially as the handsets surpass the hardware capabilities of previous generation consoles.
The situation is so much better for programmers today - a cheap used PC, a linux CD, and an internet account, and you have all the tools necessary to work your way to any level of programming skill you want to shoot for.
Focused, hard work is the real key to success. Keep your eyes on the goal, and just keep taking the next step towards completing it. If you aren't sure which way to do something, do it both ways and see which works better.
High-end BREW phones aren't nearly as limited a gaming platform as you might think - they are a lot more powerful than an original Play Station, for example. Java phones, however, are saddled with a huge disadvantage for gaming.
To this day, I run into people all the time that say, whether it was 'Doom', or maybe even more so 'Quake' later on, that that openness and that ability to get into the guts of things was what got them into the industry or into technology.
I did take some value out of looking at the extreme simplicity of implementation that the tight resource limits required. I do feel that modern games are often abstracted a lot more than is really necessary, and it leads to robustness issues.
I think that first-person shooter is a stable genre that's going to be here forever, just like there are going to be driving games forever. There's something just intrinsically rewarding about turning around a corner and shooting at something.
Honestly, I spend very little time thinking about past events, and I certainly don't have them ranked in any way. I look back and think that I have done a lot of good work over the years, but I am much more excited about what the future holds.
The great games are the space sims and driving sims and these experiences where you're basically sitting at a table with nothing happening in front of you. A lot of interesting things are evolving there. There are great games that can be made.
Developing games for the PC and consoles is all about everything and the kitchen sink. In many ways, you don't have design decisions to make. You do it all. So I enjoy going back to making decisions about what's important as I'm working on a game.
It's been great that every title that we've done internally has been a huge success, but when you've got 50 or 100 people on there, all their families and everyone counting on you there, the idea of 'What if you screw up once?' or 'What if the market changes?'
We were happy with funding 'Rage' on our own nickel for years. We intended to do the same with 'Doom 4'. We had offers early on for 'Rage'. People offered us X million dollars. But we carried the risk, and when we finally signed a deal, it was X plus $10 million.
One of the things we joke about in the FPS development is it's so hard to get the player to actually bother to look at all the cool stuff you've been doing. You spend a lot of time making really cool things, and usually the player isn't looking where you want them to.
The idea that I can be presented with a problem, set out to logically solve it with the tools at hand, and wind up with a program that could not be legally used because someone else followed the same logical steps some years ago and filed for a patent on it is horrifying.
One of the reasons microcomputers progressed so fast is people are willing to accept crashes. It's faster to build something and try it, even if it means you'll have to rebuild later... If you spent too much time building and massaging one vehicle, you don't learn anything.
After the acquisition of id by Zenimax, we had sort of taken the mobile platform team down to a skeleton crew. We were left with about two people who were finishing up the previous obligations on that. The rest had just been dispersed and absorbed by the other teams in the company.
Programming in the abstract sense is what I really enjoy. I enjoy lots of different areas of it... I'm taking a great deal of enjoyment writing device drivers for Linux. I could also be having a good time writing a database manager or something because there are always interesting problems.
We had staffed up to do 'Doom 4' internally in parallel with 'Rage'. We also had our mobile and 'Quake Live' departments. We were taking a lot of steps to kind of provide a little bit more scope and protection for ourselves. And we certainly were listening to offers from all the majors about acquisition.
I am greatly proud of the fact that 'Doom' is one of those things where everything that has a 32-bit processor has had 'Doom' run on it, and I think that's been one of the great aspects of having it be open source: having everything out there means that people have maintained that and kept it up to date.
To the game code, the world is still just a tile map, but for rendering, each map was exported as a general-purpose 3D model, and the artists could then go through it and spend the polygons any way they liked, without the limits of line-of-constant-z software rasterization that we lived with on the mobile phones.
It is true that the gameplay for 'Orcs&Elves' was designed around the limitations of mobile phones, and that if we were starting completely from scratch for the DS, we would probably do things a bit differently, but the bottom line is that when we sit a random DS player down with the game, they have a lot of fun.
With 'Rage,' it was a little bit different because this was going to be the public's first interaction with the 'Rage' IP. Early on, right after the tech demo, there was some marked concern internally how much of a bad thing it would be if the game went out and it wasn't well released and people got a bad taste off it.
The stereoscopic panoramic videos that we're showing on Samsung VR are getting a lot of positive traction. It's exciting when you see creative types - whether from the music, film, or video industries - look at this stuff. The gears are turning in their head almost immediately about how they can use it as a new medium.
The cornerstone of our Tech 5 development platform is this uniquely textured map or world, where every surface doesn't have a repeating texture on it. It can all be stamped and modified due to the work done on it. The core technical question to be resolved on this was how do we get that media set to be playable on the iPhone.
Some cynical people think that every activity must revolve around the mighty dollar, and that anyone saying otherwise is just attempting to delude the public. I will probably never be able to convice them that that isn't always the case, but I do have the satisfaction of knowing that I live in a less dingy world than they do.
It is a shame that homebrew development can't be officially sanctioned and supported, because it would be a wonderful platform for a modern generation of programmers to be able to get a real feel for low level design work, to be contrasted with the high level web and application work that so many entry level people start with.
Oculus really started popularizing a new approach using cellphone screen technology, a wide field of view, and super-low-latency sensor tracking. It's not crappy stuff that doesn't work and makes everybody sick. When you experience Oculus technology, it's like getting religion on contact. People that try it walk out a believer.
At its very core, virtual reality is about being freed from the limitations of actual reality. Carrying your virtual reality with you, and being able to jump into it whenever and wherever you want, qualitatively changes the experience for the better. Experiencing mobile VR is like when you first tried a decent desktop VR experience.
With ZeniMax, they have a lot to be proud of. 'Fallout 3' is one of the favorite games of so many of our people. But they had zero overlap with the things we do. We do the best shooters in the world. It's a perfect hand and glove fit. We started talking about this before they rolled out 'Fallout 3'. We watch them roll it out worldwide.
Obviously, virtual reality is where I've placed my bet about the future and where the excitement is going. At this point, I could say it's almost a lock. It's going to be magical - it is magical - and great things are coming from that. Along the way, I was focused on the first-person shooters. I said we should go do something on mobile.
Sharing the code just seems like The Right Thing to Do. It costs us rather little, but it benefits a lot of people in sometimes very significant ways. There are many university research projects, proof of concept publisher demos, and new platform test beds that have leveraged the code. Free software that people value adds wealth to the world.
In the information age, the barriers [to entry into programming] just aren't there. The barriers are self imposed. If you want to set off and go develop some grand new thing, you don't need millions of dollars of capitalization. You need enough pizza and Diet Coke to stick in your refrigerator, a cheap PC to work on, and the dedication to go through with it. We slept on floors. We waded across rivers.
The Escalation programmers come from a completely different background, and the codebase is all STL this, boost that, fill-up-the-property list, dispatch the event, and delegate that. I had been harboring some suspicions that our big codebases might benefit from the application of some more of the various “modern” C++ design patterns, despite seeing other large game codebases suffer under them. I have since recanted that suspicion.
I really think, if anything, there is more evidence to show that the violent games reduce aggression and violence. There have actually been some studies about that, that it's cathartic. If you go to QuakeCon and you walk by and you see the people there [and compare that to] a random cross section of a college campus, you're probably going to find a more peaceful crowd of people at the gaming convention. I think it’s at worst neutral and potentially positive.
The important point is that the cost of adding a feature isn't just the time it takes to code it. The cost also includes the addition of an obstacle to future expansion. Sure, any given feature list can be implemented, given enough coding time. But in addition to coming out late, you will usually wind up with a codebase that is so fragile that new ideas that should be dead-simple wind up taking longer and longer to work into the tangled existing web. The trick is to pick the features that don't fight each other.