RPCS3 Forums

Full Version: Earth Defense Force 2025 [BLUS31160]
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
rpcs3-v0.0.1-2017-02-19-47fdaf69_win64

Shows one screen.
RPCS3 v0.0.4-6338-54fbde0de Alpha | HEAD
Black screen instead of gameplay.
[Image: ZKaW47G.png]
[Image: xH2N9Vw.png]
RPCS3 v0.0.4-6343-6828fbf65
Ingame, not sure why it was black for grantkane. Both OpenGL and Vulkan work fine, exactly the same status as the PSN version.
RPCS3 v0.0.6-7786-a36d3af3 Alpha | HEAD
Intel® Core™ i7-8700K CPU @ 3.70GHz | 12 Threads | 15.92 GiB RAM | AVX+ | TSX
! RSX: Found vulkan-compatible GPU: 'GeForce GTX 980 Ti'

ingame


[Image: attachment.php?aid=12681]


Gameplay with fps Vulkan 24min

https://drive.google.com/file/d/1rHSoZLx...sp=sharing

log file in Attachment
No, this is not playable. Your dipping down to 17fps with an 8700k and audio + game speed breaks at that frame rate. Going to have to issue another warning for this one. Because as you can see, another moderator believed your report and moved it to Playable even though it's not up to our Playable standards. This is how we end up with a inaccurate compatibility database, and these bad reports do far more harm than good.
RPCS3 v0.0.17-12446-6a7324ab Alpha | HEAD
Intel® Core™ i7-7700HQ CPU @ 2.80GHz | 8 Threads | 15.96 GiB RAM | TSC: 2.808GHz | AVX+ | FMA
Operating system: Windows, Major: 10, Minor: 0, Build: 18363, Service Pack: none, Compatibility mode: 0
Found vulkan-compatible GPU: 'NVIDIA GeForce GTX 1070' running on driver 471.11.0.0
Firmware version: 4.88

stats: playable

it's fine and no crash or freeze at all

log file and screenshots in Attachment
RPCS3 v0.0.36-17757-f38a61bd Alpha | master | FW 4.92

Windows 10
i7-10870H
3070 Laptop GPU
32 GB 2933 MHz RAM

Like the previous post, I would call this playable. I played for 6 hours over the past month and had zero crashes during that time. In quiet areas it will run around 60 fps, but will spend most of its time between 30-40 fps. It will only drop below that when there's a lot going on.

The log file was over 300 MB uncompressed and over 12 MB compressed, so I had to split the log file into two.