@kwahoo
I would not say that rage is so demanding. i played it with my old nv 8800 gts 512 @ 1920x1200 without aa using wine and it was fast enough. often games that have got console ports are NOT so demanding as pc only games. of course when you want to enable cuda mode then you need to compile the needed wine lib as well, did not do that for this game. you can not play it with intel oss drivers however, win + hd 4000 would work. fglrx sucked badly with wine. did not check it with that game, but fglrx has got some weird wine "optimisations". when you compare glxinfo -l to what you get when you copy the binary to wine (basically any name with w in front had this effect for me) then the vendor reported switches from amd to ati. Also a few settings report lower numbers, most likely due to a bug. Feel free to compare yourself. The diff in the bug report does not show the amd -> ati change.
Maybe somebody wants to rename the wine BINARY to zine or so. It does not apply for scripts.
I would not say that rage is so demanding. i played it with my old nv 8800 gts 512 @ 1920x1200 without aa using wine and it was fast enough. often games that have got console ports are NOT so demanding as pc only games. of course when you want to enable cuda mode then you need to compile the needed wine lib as well, did not do that for this game. you can not play it with intel oss drivers however, win + hd 4000 would work. fglrx sucked badly with wine. did not check it with that game, but fglrx has got some weird wine "optimisations". when you compare glxinfo -l to what you get when you copy the binary to wine (basically any name with w in front had this effect for me) then the vendor reported switches from amd to ati. Also a few settings report lower numbers, most likely due to a bug. Feel free to compare yourself. The diff in the bug report does not show the amd -> ati change.
Maybe somebody wants to rename the wine BINARY to zine or so. It does not apply for scripts.
Comment