Command & Conquer: Red Alert 3 [BLES00506]
Started by GrantKane




5 posts in this topic
GrantKane
RPCS3 Tester


2
2,670 posts 1,777 threads Joined: Aug 2017
02-18-2017, 01:47 AM -
#1
RPCS3 v0.0.1-3-65104b5 Pre-Alpha
Quote:·F {PPU[0x1000000] Thread (main_thread) [0x00abeeec]} struct vm::access_violation thrown: Access violation reading address 0x10
This post was last modified: 08-21-2017, 04:58 PM by GrantKane.
digitaldude
RPCS3 Tester


4
3,031 posts 559 threads Joined: Aug 2017
08-21-2017, 10:55 AM -
#2
rpcs3-v0.0.3-2017-08-18-590ca711_win64

Ingame.

images


Attached Files
.rar   RPCS3RedAlert3.rar (Size: 1.35 MB / Downloads: 13)
crispy81
Member


0
175 posts 19 threads Joined: Jan 2018
09-28-2018, 03:13 PM -
#3
Generally works fine with OpenGL. Crashes randomly with the F {PPU[0x1000000] Thread (main_thread) [0x00c76910]} MEM: Access violation reading location 0x0 message. Otherwise it runs quite well, good framerate. FMV is perfect and in sync. Sound is perfect. Graphics are fine.

It may well be playable. I'll try to play right through and will post logs and screenshots.
crispy81
Member


0
175 posts 19 threads Joined: Jan 2018
11-21-2018, 07:33 AM -
#4
Now runs using Vulkan, default settings. Good framerate, although does have slowdowns, sound hisses and scratches a bit. Apart from the Memory access violation errors, which are random, this game would be playable.
crispy81
Member


0
175 posts 19 threads Joined: Jan 2018
11-24-2018, 01:22 AM -
#5
Played it through to the end, candidate for promotion to playable.

Had about 15 crashes, all at random. Pesky MEM: Access violation error, which locks the game up. Save often is the key.

Vulkan, default settings.

Things to note:

Framerate slowdown happens a bit, but generally held around 20 - 30fps.
Cutscene video/audio out of sync.
Smaller mission briefing fmv is perfect.
Sound has hissing occasionally, but otherwise it's fine.
No real graphics issues, except the ocean sometimes is white or has artifacts/tearing - only on some missions.

I'd say could be promoted to playable, if you can put up with the MEM: Access violation errors. As I've said, these are random, could occur in less than a minute, an hour or several hours later.

I have tinkered with other settings like 'Write Colour buffers' and 'Strict Rendering' but these do not resolve the access violation lockup. OpenGL also doesn't help, and is actually slower, so just stuck with Vulkan.

Screenshots attached. Log is too large to attach.
This post was last modified: 11-24-2018, 01:23 AM by crispy81.


Attached Files Thumbnail(s)
       
crispy81
Member


0
175 posts 19 threads Joined: Jan 2018
08-17-2019, 05:43 AM -
#6
RPCS3 v0.0.6-8511-0d88f037 Alpha | HEAD | Firmware version: 4.83
Intel® Core™ i7-8700K CPU @ 3.70GHz | 12 Threads | 31.93 GiB RAM | TSC: Bad | AVX+ | TSX

Promote to Playable

PPU: LLVM
SPU: LLVM
GPU: Vulkan Default

Extra setting: Write Colour Buffers - enabled.

Graphics are perfect, no tearing, corruption or artifacts.
Sound in game is perfect.
Solid 30 fps at all times

Cutscenes are imperfect. Video and audio get out of sync. One cutscene locks up completely. All can be skipped.

In game video briefings are perfect.

Log and screenshots attached.

For some reason, cannot upload the log (2.39MB)
This post was last modified: 08-17-2019, 05:51 AM by crispy81.


Attached Files Thumbnail(s)
           


Forum Jump:


Users browsing this thread: 1 Guest(s)