We could use a replay for an intro, I've thought of this before. We'll need some good replays for this...maybe we should have a replay contest to see who can come up with the best one? Right now it's only possible to record one replay at a time (recording another replaces the file if you don't move it), though we're thinking about a way to record many, and play whichever you want.
Menu graphics/widgets could use a facelift. I don't have time at the moment, but you're welcome to work on some graphics. The original buttons and other graphics for the GUI were made using
Inkscape. You can find the SVG originals in our art repository:
http://svn.vdrift.net/viewvc.py/trunk/te...vdrift-art
To make a complete "skin" for VDrift you can replace/modify any or all of the files in this directory, and its subdirectories (except tracks):
http://svn.vdrift.net/viewvc.py/trunk/da...large/gui/
(By the way, to view any of those files in the SVN browser, first click on the file, then click the "download" link on the following page. If you want to download the whole SVN repositories
see the FAQ.)
Car selection: we've been kicking this around for a while, the practice game menu is very simple and temporary, we hope that eventually there will be more to the game than just practice
Joe has started
another thread about this in Feature Requests, let's discuss it there so we can keep it all in one thread.
For cars, we'd definitely like to have some original cars (we do have a few), but the concern with adding higher poly count models, is that we will make the game inaccessible to some people with slower computers and especially video cards. The game already requires a decent amount of power to run at a very high resolution. However, if someone would like to take our models and "touch them up" to create a more detailed set of models then we could make a setting that would allow people to choose low quality cars or high quality cars. The same could probably go for tracks. It's just a matter of the time it takes to create all that data.
