Ridge Racer 7 3D (NPUB30457) cannot get ingame !

I cannot make the game Ridge Racer 7 3D (NPUB30457) ( US version ) go ingame at all, no matter I try all possible configurations ( OpenGL, Vulkan, LLVM Recompiler, Interpreter, ASMJIT Recompiler, all kind of Firmware Settings and different GPU Additional Settings ). 
Sometimes the intro images appear but then freeze, and then pressing button "start" I can hear the sound of the game showing that it is running but there is no image ( no cars, no landscapes, no menus ) so it is impossible to play. Other times I only get a black screen and no intro. 

I use rpcs3-v0.0.5-6722-7cb46723_win64 because I found it is a stable build, I tried also the latest november builds but the game crashes the emulator. In rpcs3 v0.05-6722 I can run most games named as "playable" in Compatibility list of the site, at 10-60 fps, depending on the game ( some run 30-60 fps but have big lag at times ). 
I know my computer is old and probably will not get high fps, but my intention is to test the game, I just want at least to be able to go ingame and see how the speed is while playing. 

There are many videos in YouTube where people show they can play the full game without issues. I don´t know what happens in my case, if it is a matter of CPU or lack of RAM.

My specs are Windows 10 Pro 64 bits - Pentium Dual Core E5700 3 GHZ with 4 GB RAM, and my graphic card is Nvidia GT 640, with Nvidia driver 391.35 - 64bit. 
In the file config.YML I have "Use LLVM CPU: generic" because my cpu is wolfdale. If I use openGL I tick "LLE libvdec.sprx" and put "Use Legacy OpenGL Buffers: true" in my config.YML as it is suggested for the game in Compatibility list.

I attach a file with RPCS3 log and TTY log in txt and rft format. I will be very grateful for any help in order to fix the issue.

Please find the attachment in the following link:

https://drive.google.com/file/d/1N1sCpL5...sp=sharing

Legacy OpenGL Buffers are for RenderDocs only, disable it. LLE libvdec may not be needed.
Why are you using CPU generic, does it crash if you don't?

Your GPU drivers are too old, update them. Some older drivers have issues that affect RPCS3.

Also, try with this build: https://ci.appveyor.com/api/buildjobs/cv...0_win64.7z

Legacy OpenGL Buffers are for RenderDocs only, disable it. LLE libvdec may not be needed.
Why are you using CPU generic, does it crash if you don't?

Your GPU drivers are too old, update them. Some older drivers have issues that affect RPCS3.

Also, try with this build: https://ci.appveyor.com/api/buildjobs/cv...0_win64.7z

Many thanks for your prompt reply. I did all that you suggested, updated my graphic drivers to the latest available, also used the build you recommended.

About why I am using CPU generic, it is because I took the idea from something I read in a forum. If I leave this line in config.YML without "generic", ( this is unmodified ), the emulator calls the cpu "penryn", but it works the same as when I use "generic". There is no difference in how the emulator behaves if I use generic or leave the CPU unnamed in config.YML.

I tried different configurations, but in all cases the game shows a white screen and then an error message appears saying that I must close the program ( so it crashes the emulator, the same that happened in latests november 2018 builds ).

The game used to run better in older builds, mostly in rpcs3 - v0.04 from 2017, as far as I could test. At least the screen was black or showed partially the intro, had background sound, and it didn´t crash the emulator in those older rpcs3 versions.

It draws my attention that when the emulator stops working, it shows the following error log:

F {PPU[0x1000006] Thread (TTFontRender Thread) [0x00284e20]} MEM: Access violation reading location 0x20

This error appears in lilac color in the log screen at the end. What does this error mean ? Can you suggest any clue about how to fix it ?

I need the full log file to find out what's causing that memory access violation.

Get such log file while using the latest build available on the website, if it outputs that memory access violation.

Your first log shows that the game crashes due to

·W 0:07:55.795840 {PPU[0x100004d] Thread (bnusCoreDecoderAT3PThread) [0x00399d00]} sys_memory: sys_memory_allocate(size=0xe0000, flags=0x200, alloc_addr=*0x0)
·F 0:07:55.796045 {PPU[0x100004d] Thread (bnusCoreDecoderAT3PThread) [0x00399d00]} MEM: Access violation writing location 0x0

This may be a bug with the emulator, as it's not accounting for NULL alloc_addr. This behavior will be checked on a real PS3 to find out what is the correct implementation, but it's a different issue than the one you indicated on your most recent post.

I need the full log file to find out what's causing that memory access violation.

Get such log file while using the latest build available on the website, if it outputs that memory access violation.

Your first log shows that the game crashes due to

·W 0:07:55.795840 {PPU[0x100004d] Thread (bnusCoreDecoderAT3PThread) [0x00399d00]} sys_memory: sys_memory_allocate(size=0xe0000, flags=0x200, alloc_addr=*0x0)
·F 0:07:55.796045 {PPU[0x100004d] Thread (bnusCoreDecoderAT3PThread) [0x00399d00]} MEM: Access violation writing location 0x0

This may be a bug with the emulator, as it's not accounting for NULL alloc_addr. This behavior will be checked on a real PS3 to find out what is the correct implementation, but it's a different issue than the one you indicated on your most recent post.

This time I have used the latest build from the download section, this is rpcs3-v0.0.5-7496-0e0a82e5_win64.
I tried first with OpenGl and then with Vulkan. 

By the way, about CPU "generic" that I use, it is because in some cases if I leave "LLVM CPU" in config.YML untouched, without any name, the games crash the emulator. 
Do I have to put any different name there from "generic" ? My CPU is Wolfdale, but if I leave LLVM CPU without a name, the emulator uses the name "penryn" ( this is a quad core CPU ) and that usually crashes some games.

Using the above mentioned rpcs3 build, I get a white screen with any configuration tested, and an error message pops up saying that "the program stopped working and I have to close it", it is again the memory violation issue.

( Update: today I tried a new rpcs3 build, which is rpcs3-v0.0.5-7497, tested it and had the same issue as in rpcs3-v0.0.5-7496 )

Please find the logs attachment in the following link:

https://drive.google.com/file/d/12vAJCXT...sp=sharing

Now it dies right after creating a thread as per your log, don't know why unfortunately.

The fix for the first issue you reported is in https://github.com/RPCS3/rpcs3/pull/5338 , but I assume you'll need both issues fixed to go Ingame so you need to wait the second one gets fixed.
According to other users, this game seems to go Ingame after that fix, and they can't reproduce this last issue you're having.

Now it dies right after creating a thread as per your log, don't know why unfortunately.

The fix for the first issue you reported is in https://github.com/RPCS3/rpcs3/pull/5338 ,  but I assume you'll need both issues fixed to go Ingame so you need to wait the second one gets fixed.
According to other users, this game seems to go Ingame after that fix, and they can't reproduce this last issue you're having.

Thanks again, but I don´t quite understand what you said about other users can´t reproduce the last issue.

Does this mean that it is a new issue ?  As I am using the same configuration as other people who reported they could get ingame 
( I downloaded the logs so as to know the configuration they used ), it seems this issue happens only to me, so it´s weird.

Is this game CPU and/or RAM depending ? This is, do I need an i5 or i7 CPU with lot of RAM to run the game ? 

I will be grateful again for making all this clear.

The game suffers from different issues. Two of them were already fixed on latest builds, but there may be more.

I recommend keep trying with latest builds.
As for why it works on some hardware and not in other hardware, unfortunately I don't know what's the constraint.

The game suffers from different issues. Two of them were already fixed on latest builds, but there may be more.

I recommend keep trying with latest builds.
As for why it works on some hardware and not in other hardware, unfortunately I don't know what's the constraint.

I tried the game on latest build rpcs3-v0.0.5-7505-3c7f02d9_win64

Again the emulator stops showing a white screen, with the following error in purple color at the end of the log screen:

F {PPU[0x1000005] Thread (TTFontRender Thread) [0x002ce258]} MEM: Access violation reading location 0x20

I wonder if this error has something to do with "libfont.sprx", as when the module corresponding to this file is compiled it shows some issues in red or orange, while the ones corresponding to other "sprx" files don´t show issues and the lines while compiling appear in green ( in the log screen ).

I have been also thinking that this game may need a special hardware to run, at least a Quad Core with TSX and AVX instructions, which my CPU lacks as it is only a Dual Core.

I also noticed that on the latest 0.05 builds of November the playable games are running much slower than on previous builds. As an example when I run Daytona USA with Vulkan I can easily reach 30-40 fps ( with slowdowns at times ) on rpcs3-v0.0.5-6675-bd1d4de4_win64, but on the latest build ( v0.05-7505 ) the speed with Vulkan is much less ( about 3 fps to 15 fps with big lag, with an average 8 fps ), so the newer the build is, the faster the CPU should be to run the same game.

As usual, you can find the logs in the following link:

https://drive.google.com/file/d/1_9Oxa5n...sp=sharing

Is it possible that the issue can be caused by the lack of TSX and AVX instructions of my CPU ?

Out of curiosity OP, can you get in game in the *Non-3D* version of Ridge Racer 7? If so, can I ask, how does it run on your machine?

Also, since we're discussing the 3D version of the game, this may be a dumb question but does that mean that this particular version supports full 3D? For example, can it be played in PC VR headsets like the Oculus Rift or Vive? OP have you tried it?