Code reviews are one of the best things you can do to improve code quality, but the process isn't a silver bullet. These are my observations on what works and what doesn't work when it comes to implementing code reviews.
@Guiseppe: XNA also has a lot of stuff that Ogre doesn't, such as input, networking, sound, etc. I tend to agree though that the way forward is not pure C . Using C as an embedded scripting language within a C framework might be the best way which is what ...
@Sean: Fillrate is essentially the number of pixels drawn. If you split a triangle into several smaller triangles that cover less total screen area then you reduce the number of pixels drawn and hence the fillrate. Since fillrate is the bottleneck for most games these days it is more important ...
The final shot looks great. I don't really see the effect of the rim-lighting control channel though. Maybe you could make the contrast for the different material types greater
@Sutthipong The whole team need to understand what the rules are and what are the exceptions for particular project or no body will bother following the rule and wreck havoc. You put it better than I possibly could, thanks
A lot of that dirtiness should be cleaned up or at least detected by your data tools. I've never really seen that to be a problem to be honest. Sure you get a few cases where someone makes a really inefficient model or bit of code, but that will be ...
I think a total rewrite is usually a bad idea. You should consider just doing some heavy refactoring of the current tool instead. Set aside some time in the schedule for this. Put every bug and annoyance with the tool into a backlog and work through it, refactoring the code ...
