RPCS3 Forums

Tested on rpcs3-v0.0.3-2017-09-28-eb8af974_win64

In this case I used OpenGL, however it is better with Vulkan(1280x720)

Firmware Setting: in this case "Load liblv2.sprx only" but I also used "Automatically load requires library"

PPU Recompiler(LLVM) SPU Recompiler (ASMJIT)

Additional Settings(CPU): Enable SPU loop detection, Bind SPU threads to secondary cores.
Additional Settings(GPU): Invalidate Cache Every Frame.
Framelimit: Auto
Preferred SPU Threads: 6
Audio: XAudio2, Downmix to Stereo.


The game is ok, if it's not for the CG parties that have stuttering sound, as in any other stage, like the beginning of the game, it seems to me that this is already in your knowledge, unfortunately I played most of the game time on version NPEB00549, as long as a bug forced me to change version, however I had played until Dante did not control the fire monster moving on a long road, at the gates of Dite City, just destroying the debris of the game block, which happened several times, so at that moment I decided to change version and use BLES00714, I passed that obstacle, but unfortunately it stuck when you have to turn the mechanism to maneuver the big statue with the axe, unfortunately the device can not handle, no command comes out to grab it...
The colors of the game are yellowish, but sometimes when you die, they are adjusted as the original.
I hope this bug can be solved, at least I can continue with the game...

My Specs: 
Cpu:        i7 6900K
Gpu:        GTX 1080
Ram:       32GB 

P.S.: I took the log when the game was still started...
Google TranslaTion

Here you can see the video, unfortunately it is without audio, it's just part of the bug, so you realize it. The video stops at 250 views.
http://www.videosprout.com/video?id=8a7a...fc7b9d8281

From version 0.0.5-6750-367f0395_win64 to rpcs3-v0.0.5-6769-2eae0645_win64 i have this error

F {SPU[0x2000000] Thread (ears_job_ps3CellSpursKernel0) [0x00de4]} class std::runtime_error thrown: Not supported: event mask 0x420
(in file Emu\Cell\SPUThread.cpp:1766)
F {SPU[0x2000003] Thread (ears_job_ps3CellSpursKernel3) [0x00de4]} class std::runtime_error thrown: Not supported: event mask 0x420
(in file Emu\Cell\SPUThread.cpp:1766)
F {SPU[0x2000001] Thread (ears_job_ps3CellSpursKernel1) [0x00de4]} class std::runtime_error thrown: Not supported: event mask 0x420
(in file Emu\Cell\SPUThread.cpp:1766)
F {SPU[0x2000002] Thread (ears_job_ps3CellSpursKernel2) [0x00de4]} class std::runtime_error thrown: Not supported: event mask 0x420
(in file Emu\Cell\SPUThread.cpp:1766)

the version rpcs3-v0.0.5-6748-fd8aae57_win64 is working with Dantes Inferno BLES00714

Do not create duplicate threads, a thread already exists for this game ID. I moved your post into the correct thread.

Also, I have reported the regression to developers. They even know the exact cause from the specific line of code so hopefully will be fixed soon.

(05-19-2018, 04:08 PM)Asinine Wrote: [ -> ]Do not create duplicate threads, a thread already exists for this game ID. I moved your post into the correct thread.

Also, I have reported the regression to developers. They even know the exact cause from the specific line of code so hopefully will be fixed soon.

Hi Asinine

I'm sorry about the duplicate thread will not happen again

and many thanks for forwarding Dante's Inferno can start again normally.

Elad's mgs4 fixes are also fixed huge demon statue issue, i guess the game is Playble now

Dante's Inferno now Playable...but we still have old glitches

there is no rendering of the background:

rpcs3
[attachment=17579]

ps3
[attachment=17580]

if there are more of them , I will add this post

ps. just now I noticed that I have a game BLES00713...however, I do not think that the difference is great , but if necessary, I can make a repost in the appropriate topic

cutscene glitch after videocut


log rpcs3-2.rar ...near the end

That cutscene issue only appears during a few cutscenes with that demon guy, it was moved to playable regardless due to the serious issues with the game being fixed. It's not quite perfect yet.

For the background issues, our tester didn't notice them but you can try enabling write color buffers, and if that doesn't fix it you can try force cpu blit.

enabling write color buffers with(without) force cpu blit does not help...even in native resolution