Game: Racer Driver - GRID
Installer MD5's: 035a1fe8d2d57b7146cb26422c6d7878 setup_race_driver_grid_2.1.0.8-1.bin
b9fb8635c41d2b13e898df2c80283dde setup_race_driver_grid_2.1.0.8-2.bin
1f4a7a2c36212a3ede5915c700578c74 setup_race_driver_grid_2.1.0.8.exe
WineHQ AppDB link: https://appdb.winehq.org/objectManager.php?sClass=version&iId=28327 Distro: Linux Mint Mate 17.3 (64bit)
Kernel version: 3.19
Graphics card: Nvidia Geforce GTX 960 2GB
Graphics driver & version: Proprietary / version 375.26
Wine version(s) tested: Wine 2.0rc-3 Staging
Winetricks: d3dx9_36 (native then built in), also installed the redistributable Dx9 package and the OpenAL that came with the game.
How Well Does It Run: Unless you set the Shadows to Low or Disabled the game will crash within the first few seconds after starting a race. With CSMT/Game's Ultra Settings (minus Shadows)/1920x1080 Res, game runs very well however it will crash after about 30 minutes of gameplay.
Just a general observation with some modern 32bit games on Wine: They tend to crash once the virtual memory hits 4GB. A couple of them that come to mind are:
Guild Wars 2 (32bit client), thankfully they created a 64bit executable for this popular MMO and now I can play it for well over 5 hours without a single issue, but the 32bit client will crash after 1 hour or so of gameplay.
Path of Exile: This one's well optimized, took me 3 hours straight of gameplay to get it to crash.
As for GRID itself: I've ran the game a second time, approximately 22-28 mins after I after I started it, it crashed again producing the following error:
err:d3d:resource_init Failed to allocate system memory.
wine: Unhandled page fault on read access to 0x00000000 at address 0xba94f3 (thread 002b), starting debugger...
It is worth nothing that despite the message it's the virtual memory that becomes full, not the physical one, the game itself uses less than 1GB of physical ram.