Q. looking for a good all round pc just for gaming, rough specs 8gb ram 3ghz quad processor 1gb video card etc etc
i have never brought a gaming pc before so i have little knowledge of good makes or models, any advise is much appreciated.
budget is max £450-£500 but i would like to spend as little as poss preferably around £350 bur doubt thats possible
thanks
i have never brought a gaming pc before so i have little knowledge of good makes or models, any advise is much appreciated.
budget is max £450-£500 but i would like to spend as little as poss preferably around £350 bur doubt thats possible
thanks
A. Since you live in the UK as do I there should be a couple of decent computers in currys/pc world.
This computer is £530 but if you look up the name on youtube there's a video of someone unboxing it and a video of them using it to play battlefield 3.
http://www.currys.co.uk/gbuk/advent-dt2410-desktop-pc-17291826-pdt.html
This computer is £530 but if you look up the name on youtube there's a video of someone unboxing it and a video of them using it to play battlefield 3.
http://www.currys.co.uk/gbuk/advent-dt2410-desktop-pc-17291826-pdt.html
Jobs with computer games?
Q. I'd like to learn more about potential careers in the gaming industry. I'd be interested in career paths, job titles, requirements for jobs, and the like. I'm interested more in the coding side of things than in the art aspect. Just brainstorming for my future cause I enjoy computer programming and love games. Let me know
A. This will really depend on the company you apply for.
Generally, coders will be split between the 'Engine' team and the 'Gameplay' team, where engine deal with with console specific issues (PS3 / XBOX integration etc), and maybe the audio system, physics, that sort of thing. They probably won't be working on a single game though.
The Gameplay team will be writing code specifically for the game in production. Ideally the code they write will be platform independent (it's the engine teams job to make sure that code works across all necessary consoles). They'll be talking to artists and designers a lot, and trying to make stuff 'fun'.
In smaller companies where you might only have a couple of programmers, these roles will be less well defined - you'll probably be doing bits of engine and gameplay.
The gameplay team may be split up further into sections (either formally or not) such as A.I., Audio, Physics, etc (though, any of these might be Engine! It all depends).
Career progression wise, you might start off as a Graduate programmer or Junior. Then Programmer, Senior programmer, and finally Lead programmer. Some places may have an 'Architect' (this guy will design the codebase initially, maybe choosing various coding paradigms and standards that the gamplay team should adhere to). There will also probably be a Technical Director of some sort, who probably won't be doing much programming anymore - just making sure all the tech teams are running smoothly.
You probably don't need to worry about what kind of programmer you want to be just yet - just get your foot in the door, and then try and get onto different teams and see what you like.
EDIT:
Requirements for job:
If you're going in as a graduate / junior with no experience, a demo is useful (but not necessary!)
A relatively good degree is often requested in computer science, A.I, physics or math, or something similar.
You'll almost certainly be given some sort of technical test, C++ probably, and maybe some maths or general problem solving.
They'll ask you about games! (And about their games). What have you played recently, what did you like / dislike? Try and view games from a professional angle - appreciate good / bad design.
Datascope has some good advice:
http://www.datascope.co.uk/graduate_advice_programmer.html
Generally, coders will be split between the 'Engine' team and the 'Gameplay' team, where engine deal with with console specific issues (PS3 / XBOX integration etc), and maybe the audio system, physics, that sort of thing. They probably won't be working on a single game though.
The Gameplay team will be writing code specifically for the game in production. Ideally the code they write will be platform independent (it's the engine teams job to make sure that code works across all necessary consoles). They'll be talking to artists and designers a lot, and trying to make stuff 'fun'.
In smaller companies where you might only have a couple of programmers, these roles will be less well defined - you'll probably be doing bits of engine and gameplay.
The gameplay team may be split up further into sections (either formally or not) such as A.I., Audio, Physics, etc (though, any of these might be Engine! It all depends).
Career progression wise, you might start off as a Graduate programmer or Junior. Then Programmer, Senior programmer, and finally Lead programmer. Some places may have an 'Architect' (this guy will design the codebase initially, maybe choosing various coding paradigms and standards that the gamplay team should adhere to). There will also probably be a Technical Director of some sort, who probably won't be doing much programming anymore - just making sure all the tech teams are running smoothly.
You probably don't need to worry about what kind of programmer you want to be just yet - just get your foot in the door, and then try and get onto different teams and see what you like.
EDIT:
Requirements for job:
If you're going in as a graduate / junior with no experience, a demo is useful (but not necessary!)
A relatively good degree is often requested in computer science, A.I, physics or math, or something similar.
You'll almost certainly be given some sort of technical test, C++ probably, and maybe some maths or general problem solving.
They'll ask you about games! (And about their games). What have you played recently, what did you like / dislike? Try and view games from a professional angle - appreciate good / bad design.
Datascope has some good advice:
http://www.datascope.co.uk/graduate_advice_programmer.html
Powered by Yahoo! Answers
Tidak ada komentar:
Posting Komentar