"You do ill if you praise, but worse if you censure, what you do not understand."
- Leonardo da Vinci
More pages: 1 ... 11 ... 21 ... 31 ... 41 ... 51 ... 60 61 62 63 64 65 66 67 68 69 70 ... 81 ... 91 ... 101 ... 111 ... 121 ... 131 ... 141 ... 151 ... 161 ... 171 ... 181 ... 191 ... 201 ... 211 ... 221 ... 231 ... 241 ... 251 ... 261 ... 271 ... 281 ... 291 ... 301 ... 311 ... 321 ... 331 ... 341 ... 351 ... 361 ... 365
Query FailedJackis
Thursday, June 3, 2010

When I started working as a programmer, I was "19 years old nerd" (well not nerd actually, but 19 years old), and we used to have much overwork there, especially before deadlines. I have been working there for about 2 years and then quitted after we have whole week-end of extra-work and a night of bug-fixing, so at sunday I came there at 11 am and leaved only monday at 13 am. And when at tuesday I came a bit late (at 12 instead of 11) - I was fined for that. That fine was the last straw
After that I worked in a company which made entertainment training simulators. Not game industry, but very close to it. When I joined it, it has no simulators ready at all, so we participated in the whole building process from the very beginning. It was very interesting and I liked my job very much, until I got a wife So I had to share my time between work and home. I used to stay at work for 9-10 hours, and I have to mention about the start time - it was 12 am (because our boss came to work at 2-3 pm and leaved it at 11-12 pm), so he wanted everybody to be on their places at 8-9 pm, when he began his daily pass-by. But when I got married and we started to think about babies, it became clear I have to optimize my time. So I talked to my boss about that but with no success, so after 5 years of hard-working I decided to find something calm
Now I'm working in navigational simulators industry for a little bit more then a year. We have strict working hours and I have A LOT of spare time in the evening. Firstly it was rather uncommon to me... 7 pm and I'm at home...But my wife was happy, so as my small daughter also
sqrt[-1]
Thursday, June 3, 2010

I actually got in trouble with a manager once for consistently not working 8 hours - even though state law sets my max hours to 7.5 and my contract also states this.

I also work in games, but overtime has never really been much of an issue - what is a pain is working on a project with another studio not in the same time zone. The 4am starts are not fun.
Bjorke
Thursday, June 3, 2010

I have a theory about overtime: overtime doesn't really improve a blown schedule, but it leaves people feeling that they somehow DID something about it. And then blew the schedule.
Humus
Monday, May 31, 2010

Filip: Well, even with big particles the main bottleneck is going to be ROPs anyway, so spend those transistors on a few more ROPs instead please.

Dan: I don't know about main RAM, I would have to double check, but you can do arbitrary writes to video memory at least. We used that feature in JC2 for a depth buffer conversion pass to trade performance for memory. It was very tricky to transform from one swizzled surface format to another differently swizzled one and keep both reads and writes fairly linear in memory. If you don't do that, performance drops to nearly a halt. It took me a week to get it working, but in the end I was ended up very close to theorethical max bandwidth.
jon w
Monday, May 31, 2010

720p? 540p with 2xAA for the win!
(Yeah, I'm looking at you, Gears...)
Dan
Monday, May 31, 2010

I heard the 360 had certain shader instructions to write stuff directly to main RAM. Is that true? Couldn't it be abused for this purpose?
valoh
Sunday, May 30, 2010

Imo the main design fail is that the EDRAM is GPU write only. Imagine you could directly sample from EDRAM, then the design would really shine or at least would make you forget the tiling pain. Do the image processing completely in EDRAM without touching the main bus and use it as large texture cache for texture heavy batches. Ok, and you would want hw resolves independent of the GPU, so that you can resolve and render in parallel.
Filip
Sunday, May 30, 2010

Oh you're so right.. the pain of "tiling", render-resolve logic and other stuff. I've been saying for years now that EDRAM is pain in the ass and a bad idea, but people usually don't agree.
The only good thing is the fill rate with big particles and similar stuff, but I'd still prefer writing to main RAM directly (and have some more shader transistors instead of EDRAM).

But who could predict that the deferred rendering was going to become mainstream?
More pages: 1 ... 11 ... 21 ... 31 ... 41 ... 51 ... 60 61 62 63 64 65 66 67 68 69 70 ... 81 ... 91 ... 101 ... 111 ... 121 ... 131 ... 141 ... 151 ... 161 ... 171 ... 181 ... 191 ... 201 ... 211 ... 221 ... 231 ... 241 ... 251 ... 261 ... 271 ... 281 ... 291 ... 301 ... 311 ... 321 ... 331 ... 341 ... 351 ... 361 ... 365