I completely agree. Games are evolving and becoming more complex. If you were to look inside EA you'd find the "team" behind one game is actually broken down quite a bit into sub teams. There might be three or four guys working on audio for example. There's interaction between groups but the overall picture is broken down now. The guys at EA doing the low-level graphics work aren't even members of specific game teams. They work on common APIs and tools for all their games. When you look at small companies in charge of their own games, most will license their technology outright.
Having said that, "level design" can similarly be broken down. And I think that the Unreal engine is really proving the amateur developer a look at how that's happening. With the Maya PLE included, you can create highly detailed objects outside of UnrealED and then import them. This is important. When looking for a job, you'd be very lucky to find something using all the tools you're familiar with.
The poster sounds like he has artsy interests. I'd recommend the Unreal engine because its bringing together everything. UnrealED with Maya gives you the opportunity to operate as an artist as well as a level designer.
As a side note, I'd also recommend the engine for people who already have programming experience. It's not the best place to start. I started coding with Unreal 1. But after a few years studying computer science in university, I'm really starting to understand the architecture. So yea, modding with the unreal engine has some easy aspects (mutators) but you're going to need some serious dedication and/or outside experience to get really into it and change the game. So if you're doing level design, don't join an amateur programmer for an unreal mod. Designers like to change things... so that's just my warning:)
My residence at UBC just got free internet finally. This is a more mature residence where people normally just get ADSL. Well, it was too expensive to wire so it's all just 802.11g.
Try again;)
(and yes yes, I know you still have to wire up the wireless, just buggin:P)
I personally would say FPS benchmarks make for a good way to review a few new cards which bring nothing new to the table as far as features go... Could be wrong though, we could review the features again....
My guess is that part of the problem is the limited space the manufacturers have to work with. Pumping a lot of air with a tiny fan isn't going to last forever.
That said, it never hurts to vacuum the computer occationally and keep the case up off the ground where it's not as dusty. I haven't had a computer sitting on the floor in my house since my computer room flooded eight or nine years ago. *shudder*
Based on this press release, it looks like a lot of people may be watching how this project is turning out. I'd be interested in what's motivating the city of Houston to dump $15 million into their telephone system. Are they trying to get away from paying the telcos or will residents have access to parts of this system?
I'd love to see my university, UBC, take part in some of these projects. We have a massive campus, with a great wireless network that's free for the students. It'd be great to see some projects set up for additional services once the wireless network reaches full coverage.
Another interesting way the telephone companies may be combating this behavior is by offering free student-to-student calling. I believe it's AT&T doing that around here. You register your university and calls to others who're registered at the same university are free.
I sense a massive battle between the telcos and us freeloaders coming on:)
In the busy hours, you're going to be stopped to pay a cover charge anyways. I doubt it'll slow things down badly. After all, after people get used to it you'd just swipe and pay. Not a big deal.
Mind you, I likely won't be going to any of these bars in the future. Perhaps I'll just stick to the bars I have on campus at UBC.
I don't think the point of this is to judge the best possible code. I think this is a solid way of finding fast thinking intelligent individuals. Lets face it, anyone Google hires will have to conform to how their organization organizes and manages code. Anyone who can win this sort of a contest is going to be able to indent code the right way with a little practice;)
At school now. Just tried it on VS 6.0. There are no service packs installed for VS as far as I can tell, which I find very strange but oh well. It works without any problems or warnings, assuming you
#include
using namespace std;
before your code.
Cheers
Works fine in VS.NET 2003. I'd check to see what you're talking about with 6.0 but I'm at home. Perhaps I'll give it a go tomorrow at school, where I have a variety of platforms to play with.
I recently (Saturday) purchased a rather nice 46" sony projection TV. It's 1080i (HDTV) compatible and has a single DVI input. I'm planning on attempting to configure my computer to output DVI to the TV before I resort to s-video. Apparently it's difficult to get one's computer's DVI output to sync properly with a TV's input. Does anyone know of any resources to help plan this? Or any tips?
Also, the other thing I'm wondering. I've heard that the DVI inputs that are now being placed on most "high end" (lets say $1500 - $2000 +) TVs are intended to be used for the cable/sat/whatever HDTV boxes of the future. If that's true and DVI is being put on TVs with one specific purpose in mind, I wonder if over the next five or so years we're going to see more DVI inputs on our TVs to handle more devices. DVI cables are cheap (compared to, lets say, those $100+ monster component cables) and wouldn't be subject to interference since they're digital. If I was making decisions while designing those TVs, I'd love to keep everyone stuck on component where companies can suck up hundreds of dollars on 4' cables. So what do you guys think the industry is planning on doing with DVI? I've yet to see more then one DVI input on a TV. If they were planning on replacing everything with DVI, I'd expect to see at least two (DVI and your broadcast television). But I'm only seeing one... hrmm. Thoughts?
I completely agree. Games are evolving and becoming more complex. If you were to look inside EA you'd find the "team" behind one game is actually broken down quite a bit into sub teams. There might be three or four guys working on audio for example. There's interaction between groups but the overall picture is broken down now. The guys at EA doing the low-level graphics work aren't even members of specific game teams. They work on common APIs and tools for all their games. When you look at small companies in charge of their own games, most will license their technology outright.
:)
Having said that, "level design" can similarly be broken down. And I think that the Unreal engine is really proving the amateur developer a look at how that's happening. With the Maya PLE included, you can create highly detailed objects outside of UnrealED and then import them. This is important. When looking for a job, you'd be very lucky to find something using all the tools you're familiar with.
The poster sounds like he has artsy interests. I'd recommend the Unreal engine because its bringing together everything. UnrealED with Maya gives you the opportunity to operate as an artist as well as a level designer.
As a side note, I'd also recommend the engine for people who already have programming experience. It's not the best place to start. I started coding with Unreal 1. But after a few years studying computer science in university, I'm really starting to understand the architecture. So yea, modding with the unreal engine has some easy aspects (mutators) but you're going to need some serious dedication and/or outside experience to get really into it and change the game. So if you're doing level design, don't join an amateur programmer for an unreal mod. Designers like to change things... so that's just my warning
My residence at UBC just got free internet finally. This is a more mature residence where people normally just get ADSL. Well, it was too expensive to wire so it's all just 802.11g.
;)
:P)
Try again
(and yes yes, I know you still have to wire up the wireless, just buggin
I personally would say FPS benchmarks make for a good way to review a few new cards which bring nothing new to the table as far as features go... Could be wrong though, we could review the features again....
My guess is that part of the problem is the limited space the manufacturers have to work with. Pumping a lot of air with a tiny fan isn't going to last forever.
That said, it never hurts to vacuum the computer occationally and keep the case up off the ground where it's not as dusty. I haven't had a computer sitting on the floor in my house since my computer room flooded eight or nine years ago. *shudder*
Based on this press release, it looks like a lot of people may be watching how this project is turning out. I'd be interested in what's motivating the city of Houston to dump $15 million into their telephone system. Are they trying to get away from paying the telcos or will residents have access to parts of this system?
:)
I'd love to see my university, UBC, take part in some of these projects. We have a massive campus, with a great wireless network that's free for the students. It'd be great to see some projects set up for additional services once the wireless network reaches full coverage.
Another interesting way the telephone companies may be combating this behavior is by offering free student-to-student calling. I believe it's AT&T doing that around here. You register your university and calls to others who're registered at the same university are free.
I sense a massive battle between the telcos and us freeloaders coming on
In the busy hours, you're going to be stopped to pay a cover charge anyways. I doubt it'll slow things down badly. After all, after people get used to it you'd just swipe and pay. Not a big deal. Mind you, I likely won't be going to any of these bars in the future. Perhaps I'll just stick to the bars I have on campus at UBC.
I don't think the point of this is to judge the best possible code. I think this is a solid way of finding fast thinking intelligent individuals. Lets face it, anyone Google hires will have to conform to how their organization organizes and manages code. Anyone who can win this sort of a contest is going to be able to indent code the right way with a little practice ;)
gah, slashdot raped my post, hehe. That's
#include <iostream>
using namespace std;
At school now. Just tried it on VS 6.0. There are no service packs installed for VS as far as I can tell, which I find very strange but oh well. It works without any problems or warnings, assuming you #include using namespace std; before your code. Cheers
Works fine in VS.NET 2003. I'd check to see what you're talking about with 6.0 but I'm at home. Perhaps I'll give it a go tomorrow at school, where I have a variety of platforms to play with.
I recently (Saturday) purchased a rather nice 46" sony projection TV. It's 1080i (HDTV) compatible and has a single DVI input. I'm planning on attempting to configure my computer to output DVI to the TV before I resort to s-video. Apparently it's difficult to get one's computer's DVI output to sync properly with a TV's input. Does anyone know of any resources to help plan this? Or any tips?
Also, the other thing I'm wondering. I've heard that the DVI inputs that are now being placed on most "high end" (lets say $1500 - $2000 +) TVs are intended to be used for the cable/sat/whatever HDTV boxes of the future. If that's true and DVI is being put on TVs with one specific purpose in mind, I wonder if over the next five or so years we're going to see more DVI inputs on our TVs to handle more devices. DVI cables are cheap (compared to, lets say, those $100+ monster component cables) and wouldn't be subject to interference since they're digital. If I was making decisions while designing those TVs, I'd love to keep everyone stuck on component where companies can suck up hundreds of dollars on 4' cables. So what do you guys think the industry is planning on doing with DVI? I've yet to see more then one DVI input on a TV. If they were planning on replacing everything with DVI, I'd expect to see at least two (DVI and your broadcast television). But I'm only seeing one... hrmm. Thoughts?