http://bugs.winehq.org/show_bug.cgi?id=16889
Summary: Very bad performance in Monolith games (NOLF, F.E.A.R.) Product: Wine Version: 1.1.12 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: zarquon@t-online.de
Many Monolith games show very bad performance (at least in some levels). The most extreme one is naturally F.E.A.R. (although AFAIK I have everything set to medium and optimized my WINE settings according to AppDB, e.g. hardware shaders and offscreen rendering to FBO), but since I also encountered rather hefty performance problems in the much older "No one lives forever" series I think the bottleneck is probably code typically used in many Monolith games, isolating which may be much simpler in older games like NOLF, as opposed to pretty cutting edge stuff like F.E.A.R. I have an x86_64 dual core Linux system with 4 GB of main memory and an Nvidia GF7900GS with 512MB RAM, which can run even Prey under Wine like a charm. In F.E.A.R. OTOH, frame rates dropped to something like 4 FPS on the most extreme occasions, despite medium settings. When I monitored my graphics card's temperatures during one session, it looked like it wasn't really doing much, so the bottleneck has to be somewhere in the emulation layer.
Looks like you can download a demo version of NOLF here: http://www.fileplanet.com/49582/40000/fileinfo/No-One-Lives-Forever-Demo
and NOLF2 would be here: http://www.gamespot.com/pc/action/noonelivesforever2asihw/download_2880459.h...