Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I have since fired up the game again and didn't have to tweak anything this time to make it run so probably whatever I was trying to fix was patched anyway.
End Edit.
I have created a rar file which contains two d3d9.dll files which should improve performance for Prototype 2. I had to put the files into a rar file as Dropbox doesn't seem to like DLL files being used as download links.
Anyway, once you open the rar file which can be done with a free program called WinRAR (google it if you don't have it) you will find two files, one called d3d9_windowed and one called d3d9_fullscreen. All you have to do is choose which method you wish to use, remove either the _windowed or the _fullscreen portion of the filename and then move the file into your Prototype 2 install directory.
If you have any questions, please ask in this discussion. I did not create these files and I would like to give kudos to the creators. The next reply explains where the windowed file came from and the full screen dll file is the one that was originally made for Fallout New Vegas which I found on F:NV Nexus.
http://forum.cheatengine.org/viewtopic.php?t=554972&sid=c487d90e84421cd0041bcd7d6ac53ed6
I do not frequent these forums I only know about D3D9.dll files. I had a similar problem with the Fallout New Vegas PC port and used a similar file for that.
https://dl.dropbox.com/s/17ctdpwzu5g26da/d3d9_fs.dll?dl=1
I tried using your FullScreen dll, but after a few minutes of play I get fps drops as usual. The Windowed version seemed better, my fps would dip as well, but to a much lesser degree.
OS: Windows 7 Ultimate 64-bit
CPU: AMD Phenom II X4 945 3.0Ghz
RAM: 8GB
GPU: AMD HD 7770 1GB
Driver: CCC 12.11 Beta
With the Windowed dll, I can do about 1-2 full missions before it starts showing signs of fps dropping. Otherwise I would only be able to get up to around half way with 1 mission until the fps drops.
I'm using DirectX 11 for my DirectX version, for catalyst drivers I'm using 12.8 and I also have Nvidia PhysX installed (version 9.11.1111) installed.
Can you give these a try?
For game settings I have turned AA down to low, but all other settings have been turned to high. I usually get around 40-45 FPS. Granted this game is a port so I expect little more.
My rig:
Intel i7 running at 4 GHZ
12 GB RAM
Radeon HD 6900 with 2 GB
I'm using bandicam to limit my FPS to 30, otherwise the camera gets all jerky and unplayable. But at least now I can play P2. Kudos to Very Shiny!
I have a question though, I haven't used Bandicam before, can you give some more information on the software? Perhaps it would be useful to know for future ports of games in trying to optimize them.
I too have DirectX 11 installed, and I have Nvidia PhysX installed but I'm not sure of the version. I'm pretty sure PhysX isn't the problem here so I didn't waste time with that. My settings in game have differed, I tried all LOW and then all HIGH with vsync ON. When I try to set vsync OFF my game just stops working completely.
Regarding to the Bandicam FPS limiter, that might actually work if there was a way to change the code in-game. I understand this is a console port and from my knowledge consoles only run at a maximum of 30fps. My guess is that this game wasn't properly coded to run at 60fps or higher and causes fps drops.
Bandicam is a capture tool similar to FRAPS, but in addition to being able to capture video it has a basic FPS limiter integrated. As many console ports are programmed to run with 30 FPS, limiting your FPS can do amazing things. In this case without the FPS limiter I would have about 50-60 FPS which makes the controls and the camera movement jerky and unresponsive. Nvidia drivers nowadays have a FPS limiter integrated into the system tools, but with an ATI card using a tool like bandicam or dxtory is the only way to limit the FPS.