Tried it for a few minutes. Seems to be running at a solid 30fps.
Venom had less than a year to do the port, and worked very hard on it, spreading the work across all 3 cores and relying on 'low level' code for optimisation.overclocked said:These damn ports.. It was better than Q4 but still skipped frames and other visual issues. These games should be at 60fps.
I doubt he's actively developing the D3 codebase on 360 at all.RobertR1 said:It looks like that the D3 engine simply does not port well to the 360. Quake 4 was a mess and this is margainlly better. I wonder if Carmack will heavily revise the engine to be more effecient when coupled with 360's architecture since the 360 is his focus point?
Subtlesnake said:The texture resolution was reduced for space, not performance reasons, so I guess that's just an engine issue.
Why would it be important?Acert93 said:I wonder if they are using 3Dc for normal map compression.
Subtlesnake said:Venom had less than a year to do the port, and worked very hard on it, spreading the work across all 3 cores and relying on 'low level' code for optimisation.
I wonder if the CPU was the holdup, due its in-order nature - and perhaps performance didn't scale so well over multiple cores.
The texture resolution was reduced for space, not performance reasons, so I guess that's just an engine issue.
wrong choice in gpu perhaps? (or do u want a more politically correct answer, ok then now the xb360 gpu is a great idea from a forward thinking perspective but its a prototype/experiment aka something u dont wanna ship, yet they have in the xb360!!! a fixed plaform, why i dont know perhaps the decision taker at ms was a gambler on crack)czekon said:yes if mid range PC can achieve solid 30fps why X360 can't solid 60??