Diablo 3: Reaper of Souls - Ultimate Evil Edition [BLUS31437]
Started by xbox360rulz




59 posts in this topic
Ley
Member


0
2 posts 0 threads Joined: May 2018
02-20-2019, 07:39 PM -
#41
(01-27-2019, 05:54 AM)crispy81 Wrote: I've managed to get through the game, using Vulkan, Write Colour buffers and using LLVM and ASMJT, but get Memory Access Violations at random, way too many times. Come close to throwing my controller at my monitor in frustration a few times. All versions of Diablo 3, regardless of settings, all suffer from MEM: Access Violation errors.. Even as of the latest build.

If not for that, the game runs at 60fps, perfect graphics, sound stutters when you pick up an Lore book and it starts playing, but otherwise fine.  Lot of work still needed on the Diablo 3 games, but it has come a long way.

Same here. I tried everything. Sadly, still no fix.  Sad
CPU: Intel i5 6600k @ 3.50Ghz / GPU: Nvidia GTX 1060 6Gb / Ram: DDR4 16Gb 2133Mhz / Windows 10 Pro x64.
Tudeski
Member


0
15 posts 0 threads Joined: Feb 2019
02-24-2019, 09:35 AM -
#42
If you play the Adventure Mode and want to enter the Nephalem Rift, make a Backup of your "home" Folder. (Savegames)

If the Game crashs in the Rift you loose your Rift Keys.

Playing it with Interpreter Fast, but it can crash also in this Mode with "Mem Violation" or  "Desync". Sometimes its possible to play 60-90 Minutes.
crispy81
Member


0
166 posts 17 threads Joined: Jan 2018
03-10-2019, 12:01 AM -
#43
RPCS3 v0.0.6-7840-a43e7c17 Alpha | HEAD
Intel® Core™ i7-8700K CPU @ 3.70GHz | 12 Threads | 31.93 GiB RAM | AVX+ | TSX

I don't seem to be seeing any mem access violations now.. It either just randomly locks up or produces the following, which is new, never seen this before.

F {SPU[0x2000002] Thread (CellSpursKernel2) [0x04de8]} class std::runtime_error thrown: Impossible far jump: 00000000870845d8 -> 000000000075b8f0
rionix88
Member


0
3 posts 0 threads Joined: Jul 2018
04-04-2019, 02:46 PM -
#44
   
RPCS3 v0.0.6-7931-3bfe921a Alpha | HEAD
Intel® Core™ i5-6402P CPU @ 2.80GHz | 4 Threads | 7.92 GiB RAM | AVX+
GPU: 'GeForce GTX 1060 6GB' running on driver 416.34.0.0

able to pass the character selection screen into the game, then stuck there.
only able to listen to music but character does not move.
setting change to vulcan, other setting are default.


.rar   RPCS3 diablo.log.rar (Size: 932.58 KB / Downloads: 5)
prostra78
Member


0
2 posts 0 threads Joined: Mar 2019
04-08-2019, 04:13 PM -
#45
hi all you do nice work diablo 3 reaper of souls games freezing but not crashing i hav this message

init_param=*0xd003f130)
E {PPU[0x1000000] Thread (main_thread) [0x0019e2f0]} 'cellPadSetActDirect' failed with 0x80121107 : CELL_PAD_ERROR_NO_DEVICE [1]
E {PPU[0x1000000] Thread (main_thread) [0x0019e2f0]} 'cellPadSetActDirect' failed with 0x80121107 : CELL_PAD_ERROR_NO_DEVICE [2]
E {PPU[0x1000000] Thread (main_thread) [0x0019e2f0]} 'cellPadSetActDirect' failed with 0x80121107 : CELL_PAD_ERROR_NO_DEVICE [3]
E {PPU[0x1000000] Thread (main_thread) [0x01331ee4]} 'sys_fs_stat' failed with 0x80010006 : CELL_ENOENT, “/dev_bdvd/PS3_GAME/USRDIR/CPKs/enUS_CacheAct1.cpk” [1]
S {RSX Decompiler Thread} RSX: New program compiled successfully x3
F {PPU[0x1000000] Thread (main_thread) [0x00cc766c]} MEM: Access violation reading location 0x0
LilBlinx
Member


0
1 posts 0 threads Joined: Jul 2019
07-23-2019, 12:33 PM -
#46
rpcs3-v0.0.6-8411-85b1152e_win64

Pretty much default settings this is what I've changed:

Settings:
PPU: LLVM
SPU: LLVM
Renderer: Vulkan
Resolution: 1280x720
Audio: Xaudio2

I have random memory access violation and stuttering with Audio whenever an enemy is spawned. In both Vulkan and OpenGL.


.rar   RPCS3.rar (Size: 1.43 MB / Downloads: 2)


.rar   TTY.rar (Size: 175 bytes / Downloads: 1)
This post was last modified: 07-23-2019, 08:25 PM by LilBlinx.
crispy81
Member


0
166 posts 17 threads Joined: Jan 2018
07-26-2019, 07:25 AM -
#47
Yes, all versions and all editions are plagued with MEM Access violations. Think it's in the too hard basket to fix currently.
crispy81
Member


0
166 posts 17 threads Joined: Jan 2018
09-28-2019, 03:19 AM -
#48
RPCS3 v0.0.7-8794-feabe711 Alpha | HEAD | Firmware version: 4.83
Intel® Core™ i7-8700K CPU @ 3.70GHz | 12 Threads | 31.93 GiB RAM | TSC: Bad | AVX+ | TSX


F {SPU[0x2000001] Thread (CellSpursKernel1) [0x05e40]} MEM: Access violation writing location 0xffdead00
F {SPU[0x2000004] Thread (CellSpursKernel4) [0x05e40]} MEM: Access violation writing location 0xffdead00
F {SPU[0x2000003] Thread (CellSpursKernel3) [0x05e40]} MEM: Access violation writing location 0xffdead00
F {SPU[0x2000002] Thread (CellSpursKernel2) [0x05e40]} MEM: Access violation writing location 0xffdead00
crispy81
Member


0
166 posts 17 threads Joined: Jan 2018
11-18-2019, 01:32 PM -
#49
RPCS3 v0.0.7-9151-9dab0575 Alpha | HEAD | Firmware version: 4.85
Intel® Core™ i7-8700K CPU @ 3.70GHz | 12 Threads | 31.93 GiB RAM | TSC: Bad | AVX+ | TSX


F {SPU[0x2000002] Thread (CellSpursKernel2) [0x05e40]} MEM: Access violation writing location 0xffdead00
F {SPU[0x2000003] Thread (CellSpursKernel3) [0x05e40]} MEM: Access violation writing location 0xffdead00
aziz-ops
Member


0
2 posts 0 threads Joined: Nov 2019
11-19-2019, 06:40 PM -
#50
RPCS3 v0.0.7-9159-cd6b6c8a Alpha | HEAD | Firmware version: 4.85
AMD Ryzen 5 1600 Six-Core Processor | 12 Threads | 7.94 GiB RAM | TSC: Bad | AVX+

I get ride of those acces violation errors by using "Interpreter (fast)" in PPU decoder and "LLVM" in SPU decoder


Forum Jump:


Users browsing this thread: 1 Guest(s)