|
10 posts in this topic
|
|
02-12-2017, 05:28 PM -
RPCS3 v0.0.1-3-aff0484 Pre-Alpha
Quote:·F {PPU[0x1000000] Thread (main_thread) [0x00aaf1d0]} struct vm::access_violation thrown: Access violation reading address 0xe0044034
01-12-2018, 02:33 AM -
RPCS3 v0.0.4-6305-51a2b43d8 Alpha | HEAD
Quote:·F 0:00:15.844527 {PPU[0x1000010] Thread (GFX Raw SPU Interrupt PPU Thread) [0x00afbfec]} MEM: Access violation writing location 0xd0101f90 ![[Image: 61SFtb9.png]](https://i.imgur.com/61SFtb9.png)
05-21-2018, 03:05 AM -
RPCS3 v0.0.5-6814-6fd402bcf Alpha | HEAD
The game freezes after pressing START. ![[Image: VjrQewI.jpg]](https://i.imgur.com/VjrQewI.jpg)
05-26-2019, 11:39 PM -
Needs proper report filed so we can open an issue and fix the regression, if it is one.
This post was last modified: 05-26-2019, 11:39 PM by Ani.
Desktop: Ryzen 7 5800X, Radeon RX 6800 XT, 2x8G DDR4 3600MHz, Manjaro Linux
Laptop: Ryzen 9 5900HX, Radeon RX 6700M, 2x8G DDR4 3200MHz, Manjaro Linux Old Desktop: AMD FX-8350, Radeon R9 280X, 2x4G DDR3 1600MHz, Manjaro Linux
08-16-2019, 07:09 AM -
Rango is ingame, it had regression, now it's fixed can't found when regresion happened and can't tell when it was fixed, perhaps one of the latest Elad's fixes, but it's ingame only game has some problems with saves so if you'll run the game for the second time you'll have some Acces violation, so for now is better to use "Continue without saving"
the game itself runs good on LLVM's very stable
This post was last modified: 08-16-2019, 07:52 AM by xcedf.
08-16-2019, 08:17 AM -
Needs log and build name.
02-07-2020, 03:42 AM -
RPCS3 v0.0.8-9523-edcd2fc1 Alpha | HEAD | Firmware version: 4.85
Intel® Core™ i9-9900KF CPU @ 3.60GHz | 16 Threads | 15.91 GiB RAM | TSC: Bad | AVX+ | TSX Operating system: Windows, Major: 10, Minor: 0, Build: 18363, Service Pack: none, Compatibility mode: 0 ·! 0:00:00.000000 RSX: Found vulkan-compatible GPU: 'GeForce GTX 1070' running on driver 441.87.0.0 stats: playable ingame stable at 29 to 30fps all the time. it's fine and no crash or freeze at all log file in Attachment
soon
|
|
|
