Far Cry 2 [BLUS30178]
Started by GrantKane




6 posts in this topic
GrantKane
RPCS3 Tester


2
2,670 posts 1,777 threads Joined: Aug 2017
01-06-2018, 03:40 AM -
#1
RPCS3 v0.0.4-6300-19d181fa Alpha | HEAD
Ingame.
[Image: M7PesIB.png]
[Image: yk4BBFF.jpg]


Attached Files
.7z   RPCS3.7z (Size: 3.84 MB / Downloads: 20)
dio
Unregistered


 
10-06-2019, 11:17 PM -
#2
Status:

Still Ingame, but only because of performance reasons. Might be Playable on stronger hardware.

Required settings:

Write Color Buffers: true

Recommended settings:

Preferred SPU Threads: 2
SPU loop detection: false
Max SPURS Threads: 3
Approximate xfloat: false
Renderer: Vulkan
Disable ZCull Occlusion Queries: true
Resolution Scale: 200
Vblank Rate: 120
Log: {sys_net: Fatal, cellNetCtl: Fatal}

Notes:

- The game seems to find new shaders and SPU modules no matter how many times I reload the same level, meaning that already seen shaders and SPU modules are not being properly recognized.
- The game very heavily spams network requests, which is why its recommended to have the related logging disabled.
- On my machine, using resolution scale quickly resulted in a "VRAM full" situation. Apply accordingly. (I have only 1 gigabytes of VRAM though, worths noting.)
- The game hovers around 5 fps for me (with res scaling at 100%) normally, around 23 fps when looking up at the sky, and around 13 fps with Null renderer. The game runs at locked 30 for @"RainbowCookie" on his AMD R7 1700 CPU with Null renderer, sometimes going even higher up to 40 fps; hovers around 7-10 fps for him otherwise.
- Thanks to @"RainbowCookie"'s testing, the game is confirmed to be fully compatible with the vblank override, hence I listed it among the settings.
- The initial cache building might be rough.
- Both the base version and the updated version perform and behave the same.

My system:

CPU: Intel Core i5 4440 @ 3.1 GHz
RAM: 2x4 GB DDR3 @ 1600 MHz
GPU: AMD Radeon HD 7700 (GHz Edition) (1 GB VRAM)
OS: Windows 8.1 Pro (v. 6.3 b. 9600)
FW: 4.84
EMU: RPCS3 v0.0.7-8834-aa659f3c Alpha

Image proof:

[Image: unknown.png]

Logs:

.gz   RPCS3.log.gz (Size: 817.1 KB / Downloads: 0)
crispy81
Member


0
175 posts 19 threads Joined: Jan 2018
10-08-2019, 12:03 AM -
#3
Using those settings, I get about 10 - 12 fps for the cab ride at the start. Unacceptable to be playable. Once I started playing, was hovering around the 14fps mark. Also unacceptable to be deemed playable.


Attached Files Thumbnail(s)
   
dio
Unregistered


 
10-09-2019, 08:40 PM -
#4
(10-08-2019, 12:03 AM)crispy81 Wrote: Using those settings, I get about 10 - 12 fps for the cab ride at the start. Unacceptable to be playable. Once I started playing, was hovering around the 14fps mark. Also unacceptable to be deemed playable.

What CPU?
crispy81
Member


0
175 posts 19 threads Joined: Jan 2018
10-09-2019, 09:47 PM -
#5
Intel® Core™ i7-8700K CPU @ 3.70GHz | 12 Threads | 31.93 GiB RAM | TSC: Bad | AVX+ | TSX
dio
Unregistered


 
10-10-2019, 08:32 PM -
#6
Definitely not playable then yet, yeah, lol.
techguy95
Member


0
9 posts 0 threads Joined: Aug 2019
01-05-2024, 06:25 PM -
#7
Almost playable for me. Fps jumps from 15-25. Average is 20fps.

Graphics render fine.

Settings: Allow host GPU labels, Write color buffers.

Specs: AMD Ryzen 5 1600 Six-Core Processor | 12 Threads | 15.95 GiB RAM | TSC: 3.200GHz | AVX+ | FMA3

NVIDIA GeForce GTX 1070' running on driver 546.33.0.0.

Firmware version: 4.90.

Playing using: RPCS3 v0.0.30-15914-2a1af17f Alpha | master

Operating System: Win 10.


Attached Files Thumbnail(s)
                       
       


Forum Jump:


Users browsing this thread: 1 Guest(s)