Forums

I've been thinking about making a release to get some feedback on the new GUI.

There are a few issues that would be nice to fix:
- Translations(gettext support?)
- Racing tracks in reverse direction has been reported as being broken(haven't tested yet)
- Analog gauges HUD option(there have been issues with rendering?)
- Garage cam animation(rewrite/simplify camera code)

Should we push a release asap or address the above issues first?

Please note. I am the only active core developer atm, thus fixing could take some time. Hence, if you've got some time to spare and are interested in C++/game programming contributions are very welcome. In case of issues or questions related to VDrift code/implementation post them here or on github, I am happy to assist.

We have made some pretty big, user visible changes from the last release, so I say release as soon as possible, and target your issues above for the next release. However, I have found a fair number of bugs:
- The view distance setting seems to reset to very low whenever a game is played.
- The motion blur and music volume settings reset to blank after a restart.
- After playing a track in reverse, the garage background is also in reverse, so the car can't be seen.
- Adding new controls don't use sensible event type and trigger settings e.g. changing the throttle sets the type to 'Once' so the control doesn't seem to work ingame (also relevant for GUI controls).
- Text in the new control page doesn't have a background.
- If escape is not set as the cancel control the new control page text is wrong (this might be a WONTFIX)
- The DSN and F40, and probably others to crash the game with the following when trying to change to them:

I could probably fix most of these myself, but don't have time atm. The mac release might be delayed too (I want to update boost before the release).
Finally, well done on all your work so far, you've been amazing. I've already heard positive comments from several VDrift users and non-users when I've shown them the recent changes. The next release, whenever it is, will be awesome!

Thanks a lot for the testing and bug report Timo. I'll go through your list and fix asap.

Release early, release often. Do an unstable/testing release now, do a stable release once you're happier with it.

Quote:- The DSN and F40, and probably others to crash the game with the following when trying to change to them:
Code:
ERROR: Failed to load volan.joe from:, /Users/timothyfurlong/Library/Preferences/VDrift/cars/F40, /Users/timothyfurlong/Documents/Development/VDrift/Dev/Timo6/vdrift/vdrift-mac/build/Debug/VDrift.app/Contents/Resources/data/cars/F40, /Users/timothyfurlong/Documents/Development/VDrift/Dev/Timo6/vdrift/vdrift-mac/build/Debug/VDrift.app/Contents/Resources/data/carparts, /Users/timothyfurlong/Documents/Development/VDrift/Dev/Timo6/vdrift/vdrift-mac/build/Debug/VDrift.app/Contents/Resources/data/trackparts
ERROR: Failed to load steering wheel.
ERROR: Error loading car: F40

I went through the car list. All load without problems. Could you try deleting the vdrift user folder(/Users/timothyfurlong/Library/Preferences/VDrift?) to be sure the latest/svn version is used?

I hope to make the release this weekend. Windows version will ship with SDL2/Force Feedback, will use a custom SDL2 control map I think.