Ninja Gaiden Sigma [BLUS30036]

The random crashes in this game are also fixed with Removal of the MFC Thread (#4335) too, in other words, rpcs3-v0.0.5-6639-90e0bade_win64 and later builds have fixed the rare random crash.

RPCS3 v0.0.5-6692-98b715d8c Alpha | HEAD   0.0.5-6692
Intel® Core™ i7-3930K CPU @ 4.2GHz | 12 Threads | 13.92 GiB RAM | AVX    gtx 1060 6g
playable 35~60 fps   80% 60 fps and just using 25~30 % of my cpu power   if you have a better cpu maybe you will get locked 60fps 
no game braking bugs or crashes  but the company logo video intro runs like slid show for me   any fix???

no fix for videos yet, they will play frame by frame for now.

I would like to request anyone with the knowledge on frame rate code on emulators to take a look on Ninja Gaiden Sigma for RPCS3 please? At moment if we cap it at 30fps it runs at half speed I wish we could cap it to 30fps keeping fullspeed, just like the VITA ver. does.

At 30fps it will be playable on most cpus, even on laptops.

this game was working fine but now it just give me just white screen and sound
pleas help

At the last version of RPCS3 my Ninja Gaiden Sigma drop from 60fps to 35 at every corner I cross. Even after loading the whole scenario is no more than 50fps.


What happened ? I already played more than 10 hours of game play at 60 fps

I7 7700K
16 GB RAM
GTX 1060 6GB

Now here something for those who can't get fullspeed all time in Ninja Gaiden Sigma, it makes the game run like if it was running 30fps, just like VITA ver.

In your rpcs3 folder open "config.yml" and edit "Enable Frame Skip: false" to Enable Frame Skip: true, now save the file and you're good, enabling Frame Skip improves a lot performance for old CPUs eliminating various slowdowns, you may still get fps drops here there cause but it almost doesn't happen here with an i7 3770 at 4.23GHz.

Now I just wish we could get one CE Table for this game with the following features:

* Costume Select (on Sigma you can only select a costume on new game and then never)
* Yellow Orb modifier (Money) (even I could do this but it's hard get CE working I couldn't get it even with the big endian )
* Weapon edit/modifier (so we can have Dark Dragon Blade at beginning)

Anyone with an AMD GPU try this game? I have a RX580 using Vulkan and getting lots of stuttering and CPU is a R5 2600X with 3200 CAS 14 RAM so that shouldn't be an issue. There's videos of people play this with a R5 1500X and even a GTX 660 that are getting perfect 60 FPS.

Perfect fully playable
 

i can't see any problem in this game...



------------------------
((Test on  RPCS3 v0.0.8-9462-48a847d1 Alpha))
Link Patreon for Help developer https://www.patreon.com/Nekotekina

-------------------
Better in Vulkan

--------------------

Speed   : Full (60 FPS)
Movie   : Perfect Work
Graphic : Perfect  Work
Music   : Perfect Work


 
The log file:-

  RPCS3.log.gz (Size: 665.2 KB / Downloads: 10)
___________________________________
CPU:- Intel I7-6800K @ 3.40 GHz (OverClock 4.5 GHz)
GPU:- GTX 1080
Motherboards:- ASUS X-99A-II
RAM:- 32.0 GB (3000 MHz)

I am having a problem booting this title, I have attached the logs. Am using standard configuration for RPCS3, have a valid firmware, have been using the ps3-disc-dumper utility to dump my games without issue, but I never get past the following error:


RPCS3: fatal error
Verification failed:
(in file D:\a\1\s\Loader\PSF.cpp:118)

I am running this with AMD RX-470 GPU, 16GB RAM, i7-6700K CPU, game is loaded in a directory on the SSD with ~70GB free space (it is not in program files directory). I am trying to boot from a dumped game on a separate mass storage drive.

The folder location noted in error detail doesn't exist on my system, D: refers to a BD drive on my machine.

Logs attached. There isn't much there because the process does not get very far.

I haven't asked around on Discord yet, but for some reason when I set this game to 1080p, it runs in a squished 3:4 box, from what it looks like (yes, taller than wide). Everything else seems good, though text doesn't seem to scale right when I use the resolution scaling. Just in case anyone else runs across the same issue!