This title includes a so called 'Performance Monitor' - what it does, is compare the frame-rate achieved during a game session, against the current video detail level and the frame-rate target range specified in the game's video options menu. If this monitor deduces that you may have been able to achieve the target frame-rate range with a higher video details setting, it will prompt you upon exiting the game session of this situation, and whether or not you want to apply higher video detail settings.
Always say NO if this happens -- or better yet, turn off the Performance Monitor altogether.
On this linux box with 3gb system ram/nvidia 9400GT 512mb / emulated virtual desktop ON / game display options at 1024x768x32 with the Performance Monitor's "suggestion" of using HIGH video detail settings (HIGH for all sub components of detail settings) / nvidia 190.53 videocard drivers for linux in twinview mode (only one display used, total size = 2704x1050) the game would reliably crash within the first 300metres of road leaving the pits, and flag a suggestion that you email the steam_debug log generated to Steam support -- instead, when you next start the game, immediately go into the graphics options menu, and then change the global detail settings from HIGH to MEDIUM - the game should run without crashing again.- AMD64 x2 4000+ CPU used (2.11GHz).
You -can- get a higher display detail, by manually setting the detail of individual sub components in the video options menu -- a degree of experimentation/trial and error on the user's part will be needed to arrive at the 'maximum' setting possible for any particular setup/computer hardware being used. If you experience random crashes in this game, first look to the graphics detail settings and set them to LOW, and see if the crashing stops.-- it this fixes it, you can gradually increase the detail level for individual components, until you find the limit of what your hardware can do.
Important Information
Tips are provided by the CrossOver Community and Advocates. They are not
intended to be used for official CodeWeavers Support. For that, please visit our
official support pages.
CodeWeavers or its third-party tools process personal data (e.g. browsing data or IP addresses) and use cookies or other identifiers, which are necessary for its functioning and required to achieve the purposes illustrated in our Privacy Policy. You accept the use of cookies or other identifiers by clicking the Acknowledge button.