Just for the sake of sanity check, I just tested today with a fresh install of the rpcs3 emulator, fresh installed Nvidia driver version 460.89 DCH (it's the regular driver, no need to use vulkan beta driver). Same exact settings for the emulator as shown on the previous video I recorded above. Daytona USA version NPUB30493. Same PC configuration. RPCS3 v0.0.14-11690-28658653 Alpha (todays latest version as at the time of this post).
Result: it runs flawlessly with no issues whatsoever. No texture corruption, no flickering, nothing wrong. The only differences is that I ran without freesync this time and I also installed the latest PS3 firmware version 4.87, but it both doesnt matters for the test anyway.
So yes, it's working with full LLVM support. If it's not working for you, try a clean install of RPCS3 emulator and GPU driver before posting here, and use the same settings as the ones shown in the video. if you use AMD GPU for rendering the game, that possibly could be the problem though. I didn't bother to test using my RX550 for this.
Just wanted to add that the this version works perfectly, iv done a few races this my old, and only, computer
with the ps4 game pad
Intel® Core™ i5 CPU 750 @ 2.67GHz | 4 Threads | 8.00 GiB RAM | TSC: 2.665GHz
However as digo said, you need to download the latest gpu drivers from nvidia
461.40-desktop-win10-64bit-international-whql.exe
There seems to bee some error in the log, but doesn't seem to affect the game.
Cheers!
Missing log file, you uploaded something that wasn't the log file
Still borked.
What I tried:
Fresh RPCS3 install.
Fresh nvidia drivers, with clean installation
Downloaded game from a web source instead of my dump (in case it was a bad dump)
Default settings on rcps3.
With all that, still shows garbled graphics.
RPCS3 v0.0.14-11698-fad89f1c Alpha | HEAD | Firmware version: 4.87
AMD Ryzen 5 2600 Six-Core Processor | 12 Threads | 15.95 GiB RAM | TSC: 3.394GHz | AVX+ | FMA3
Operating system: Windows, Major: 10, Minor: 0, Build: 19041, Service Pack: none, Compatibility mode: 0
RSX: Found vulkan-compatible GPU: 'GeForce GTX 1660 SUPER' running on driver 461.40.0.0
Im guessing its something to do with either my CPU or Windows version (2004, still doesn't download 20H2). Or both
(02-06-2021, 03:53 PM)Ani Wrote: [ -> ]Missing log file, you uploaded something that wasn't the log file
oops, there we go.
RPCS3 v0.0.14-11702-0057c89e Alpha | HEAD | Firmware version: 4.87
Intel® Core™ i5 CPU 750 @ 2.67GHz | 4 Threads | 8.00 GiB RAM | TSC: 2.665GHz
Operating system: Windows, Major: 10, Minor: 0, Build: 16299, Service Pack: none, Compatibility mode: 0
RSX: Found vulkan-compatible GPU: 'GeForce GTX 660' running on driver 461.40.0.0
(02-06-2021, 11:26 PM)nandru Wrote: [ -> ]Still borked.
What I tried:
Fresh RPCS3 install.
Fresh nvidia drivers, with clean installation
Downloaded game from a web source instead of my dump (in case it was a bad dump)
Default settings on rcps3.
With all that, still shows garbled graphics.
RPCS3 v0.0.14-11698-fad89f1c Alpha | HEAD | Firmware version: 4.87
AMD Ryzen 5 2600 Six-Core Processor | 12 Threads | 15.95 GiB RAM | TSC: 3.394GHz | AVX+ | FMA3
Operating system: Windows, Major: 10, Minor: 0, Build: 19041, Service Pack: none, Compatibility mode: 0
RSX: Found vulkan-compatible GPU: 'GeForce GTX 1660 SUPER' running on driver 461.40.0.0
Im guessing its something to do with either my CPU or Windows version (2004, still doesn't download 20H2). Or both
Did you restart pc or close user session. If I dont do this i was noticing a few things
1. A frame drop (from 60 to 40) and lag during racing (probably my slow computer)
2. At a certain part of the circuit (passing by the start) i always get a frame drop (down to 40 fps for 1 second), however if iv launched rpsc3 just after a close session its hardly worth mentioning
Your pc should pulverize mine, mind you i think this is the only game i can play
cheers!
You still didn't upload log file, you uploaded some copy paste into a .txt file
Log file is RPCS3.log
(02-07-2021, 12:14 PM)Ani Wrote: [ -> ]You still didn't upload log file, you uploaded some copy paste into a .txt file
Log file is RPCS3.log
ah directly from RPCS3.log
Cheers
(02-07-2021, 10:04 AM)Tomcat Wrote: [ -> ]Did you restart pc or close user session. If I dont do this i was noticing a few things
1. A frame drop (from 60 to 40) and lag during racing (probably my slow computer)
2. At a certain part of the circuit (passing by the start) i always get a frame drop (down to 40 fps for 1 second), however if iv launched rpsc3 just after a close session its hardly worth mentioning
Your pc should pulverize mine, mind you i think this is the only game i can play
cheers!
Yep. The issue isnt frame drops, is that graphis are still all over the place ingame with LLVM PPU Recompiler. One thing I could try is booting linux and see if there are corrupted there... Will do and report back!
EDIT: Nope. Linux is also affected.
RPCS3 v0.0.14-11706-44ab5055 Alpha | HEAD | Firmware version: 4.87
AMD Ryzen 5 2600 Six-Core Processor | 12 Threads | 15.65 GiB RAM | TSC: 3.394GHz | AVX+ | FMA3
Operating system: POSIX, Name: Linux, Release: 5.4.0-65-generic, Version: #73-Ubuntu SMP Mon Jan 18 17:25:17 UTC 2021
RSX: Found vulkan-compatible GPU: 'GeForce GTX 1660 SUPER' running on driver 460.39.0.0
I can confirm: Daytona USA (NPUB30493 & NPEB00630) is broken using the PPU "Recompiler LLVM", only is playable on "Interpreter", but is slow!
RPCS3 Version:
rpcs3-v0.0.14-11767-b86ec2ff _win64
Game:
DAYTONA USA [NPUB30493]
DAYTONA USA [NPEB00630]
Status:
Ingame.
Config default:
https://www.youtube.com/watch?v=tra8sacw6rA
Saludos!
(02-07-2021, 01:34 PM)Tomcat Wrote: [ -> ] (02-07-2021, 12:14 PM)Ani Wrote: [ -> ]You still didn't upload log file, you uploaded some copy paste into a .txt file
Log file is RPCS3.log
ah directly from RPCS3.log
Cheers
I have been viewing one of the other daytona threads, but here is my log, have tried almost every version released and still has texture issues with LVM, still i have a very old modified release that works.
Have done clean install of nvidia drivers, and cleared all cache, and tested with a lot of different settings to see if it changed anything