I have the same problem with a 9400M but its working after several
restarts of the app.
Thanks, good to know - perhaps it's the 'Mobility' (M) chipset
that's spooking it. It's a bit hard to debug (trackmania) - it
has a builtin table of video devices it 'knows' about, and at
startup it compares what it finds against devices in the table.
It pretty much is going to get this wrong a lot of the time ;
for example, although my iMac has a hd5670 with 512mb vram, the
wine code present the game with a 'fake' device descriptor of
hd3200 ; the game logic then concludes I have 131mb video ram.
The detected and/or configured settings are written to binary
encoded runtime files, so one would need sit there for a while
with a hexeditor to investigate if there were any critical bytes
one could change ... but, as the startup detection itself is
failing, any edits are likely to be overwritten, so it really
misses the point...
...the real trick would be to present a video device interface
that the startup auto detection/benchmark routine construed to
be a (more) valid entry in it's internal table ; in fact, getting
startup to work 'properly' would be half the battle here...and
would possibly have to work first anyhow...unfortunately I don't
have a Mac with nvidia mobility chipset...so it's going to be
up to the user to try all the graphics settings...