I'm not sure I should be having an issue with running this game, but I do appear to be. Just to start off, I'm running Arch 64-bit with an AMD FX4300, Radeon 7850 with the 13.11 catalyst drivers, wine 1.7.5. I'm using the Steam version of this game (NFS:HP -2010), similarly to an unresolved bug that was reported, I'm having the game start, come to the first loading screen and then it freezes. I never even get to give the game my key. I did install the msxml3 package as suggested by the appDB page, but to no availe. Also worth mentioning, this is a prefix created by playonlinux specifically for steam. and no other games are installed in that prefix.
The aforementioned bug:
http://appdb.winehq.org/objectManager.p ... &iId=22486
Any ideas and suggestions are greatly appreciated.
Need for Speed: Hot Pursuit (2010) + AMD Radeon 7850
Re: Need for Speed: Hot Pursuit (2010) + AMD Radeon 7850
TomSloan we don't officially support playonlinux we have issues with some patches and stuff they auto install thinking they are being helpful.
The ubuntu wine ppa has 1.7.6 hopefully 1.7.7 soon.
https://appdb.winehq.org/objectManager. ... &iId=19444
The official support script way for steam says you would have used winetricks if you were using a automated tool.
Please do 3ddriverissues checks http://wiki.winehq.org/3DDriverIssues there is a possibility you have missed installing 32 bit video card drivers.
TomSloan also you have not shown us what command you are running game with. Appdb notes the NFS11.exe does not work. Launcher.exe is the one to run.
Also was the wineprefix setup as a WINEARCH=win32 prefix. If a prefix is not WINEARCH=win32 you should not use winetricks on it. Even playonlinux is having extra failured because of creating win64 prefixes.
The ubuntu wine ppa has 1.7.6 hopefully 1.7.7 soon.
https://appdb.winehq.org/objectManager. ... &iId=19444
The official support script way for steam says you would have used winetricks if you were using a automated tool.
Please do 3ddriverissues checks http://wiki.winehq.org/3DDriverIssues there is a possibility you have missed installing 32 bit video card drivers.
TomSloan also you have not shown us what command you are running game with. Appdb notes the NFS11.exe does not work. Launcher.exe is the one to run.
Also was the wineprefix setup as a WINEARCH=win32 prefix. If a prefix is not WINEARCH=win32 you should not use winetricks on it. Even playonlinux is having extra failured because of creating win64 prefixes.
Re: Need for Speed: Hot Pursuit (2010) + AMD Radeon 7850
I've taken some time to implement some of your suggestions, namely updating wine to 1.7.7 and reinstalling steam via winetricks. So far so good, here's where the trouble starts:
The outpute of
is
However, I can confirm that 32-bit 3D drivers are installed. Otherwise native steam and steam games wouldn't work and Portal 2 via wine-steam wouldn't work, let alone work nearly flawlessly.
Secondly, Steam does not create a Launcher.exe. To run the game, I simply click "Play" via steam. Browsing the games folder in my steam wine prefix, there isn't even a NFS11.exe, only a bunch of appid_####.exe files.
The outpute of
Code: Select all
WINEDEBUG=+wgl wine your_3d_app.exe &> wine.log
Code: Select all
bash: WINEDEBUG: command not found
Secondly, Steam does not create a Launcher.exe. To run the game, I simply click "Play" via steam. Browsing the games folder in my steam wine prefix, there isn't even a NFS11.exe, only a bunch of appid_####.exe files.
Re: Need for Speed: Hot Pursuit (2010) + AMD Radeon 7850
TomSloan ok what is your system.
env WINEDEBUG=+wgl wine your_3d_app.exe &> wine.log
Most systems I work on the env command is presumed automatically by Bash.
If you used a run dialog not everything is designed to be placed them them. The Line in a pure termianl instruction.
http://appdb.winehq.org/objectManager.p ... ngId=81760 Turns out in the steam version they have changed a few things and its not very compadible.
env WINEDEBUG=+wgl wine your_3d_app.exe &> wine.log
Most systems I work on the env command is presumed automatically by Bash.
If you used a run dialog not everything is designed to be placed them them. The Line in a pure termianl instruction.
http://appdb.winehq.org/objectManager.p ... ngId=81760 Turns out in the steam version they have changed a few things and its not very compadible.