RPCS3 v0.0.5-7320-fb5cdf97 Alpha | HEAD
Intel® Core™ i7-8700K CPU @ 3.70GHz | 12 Threads | 31.93 GiB RAM | AVX+ | TSX
Vulkan - default settings.
Graphics are good, sound is good, good framerate. Unfortunately random crashes from memory violation errors.
Crashes a wee bit less with Sound Loop Detection deactivated and SPU cores set to 2.
Still too much crashes to be tolerable, in my opinion.
RPCS3 0.0.5-7458 Alpha
Had problems getting past character creation screen and got stuck on compiling shaders loop.
These changes did the trick for me:
Changed rpcs3.exe process priority to real time
Vulkan instead of OpenGL
Disabled "Enable SPU loop detection"
Game looks great and performs well. Havent encountered a crash, but sound stutters in certain areas.
i5 7600K
GTX 1070
16gb RAM
SSD
Windows 10
(10-25-2018, 04:47 PM)tryhard01 Wrote: [ -> ]RPCS3 0.0.5-7458 Alpha
Had problems getting past character creation screen and got stuck on compiling shaders loop.
These changes did the trick for me:
Changed rpcs3.exe process priority to real time
Vulkan instead of OpenGL
Disabled "Enable SPU loop detection"
Game looks great and performs well. Havent encountered a crash, but sound stutters in certain areas.
i5 7600K
GTX 1070
16gb RAM
SSD
Windows 10
i use those as default emulator ,it freezes on character select nevertheless
(05-23-2018, 02:28 AM)organicchemistry_01 Wrote: [ -> ] (05-22-2018, 12:21 PM)Unforgiven Wrote: [ -> ]Care to share this specific build please?
Here you go https://ci.appveyor.com/api/buildjobs/k3...f_win64.7z
There was still however few fatal here and there, still in game and not yet playable but definitely finishable.
With this i was able to get into game,get character, start it. And it would freeze right after entering world.
Any specific settings u used?
--edit
meh its no use, if i change anything i get stuck at autosave , startup screen, otherwise i can get into game and freeze after entering world
Stuck (Not Freeze) At Autosave screen
RPCS3 0.0.5-7627-64ea7bf8 Alpha
Gtx 1060 6gb | Intel® Core™ i7-8700 CPU @ 3.20GHz | 16gb ram | Windows 10 Pro 64-bit
Yeah, because you're using an old build. It was fixed, update.
Have you guys tried LLVM? I'm running some tests now, haven't nocied any crashes with LLVM yet, but I haven't played more than 30 minutes on build 7739.
(01-23-2019, 08:22 PM)Slyponto Wrote: [ -> ]any improvements keem85?
No unfortunately not. I tried again yesterday and it freezed after literally 20 seconds with LLVM active. I'm gonna pay a close attention to this one.
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.