New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Regression] Virtua Tennis 4 World Tour Mode (#10706) #12892
Comments
@AniLeo Logfiles:- Not working with 12644 Working with 12640 Log implies that it can be resolved with Atomic FIFO, but doing so still causes the crash in the latest master. Ditto for increasing Driver Wake Up Delay. Game crashes, followed by the emulator crash, with a segfault error. |
Any update on this? |
Not working (updated today to latest version) |
Can you upload a log with the latest version? The logs in the original post are quite old by now |
Crash log from a more recent master (0.0.28-15171) Same thing happens, Log implies that it can be resolved with Atomic FIFO, but doing so still causes the crash in master. Ditto for increasing Driver Wake Up Delay. Game crashes, followed by the emulator crash, with a segfault error. |
Still not working with last version... Could be really great to debug World Tour mode :) |
Tried with all FIFO accuracy settings, none worked Log from |
This issue is still alive, emulator crashes when starting World Tour mode no matter the configuration. |
Quick summary
Virtua Tennis World Tour Mode stopped working starting on PR #10706
Working: v0.0.17-12640-24d7374a
Broken: v0.0.17-12644-a346767a
Sourced from Reddit comment following user investigation: https://www.reddit.com/r/rpcs3/comments/yem9u7/virtua_tennis_world_tour_mode_not_functioning/iu0rwm8/?context=3
Opening the ticket with the Need Information label as log files are required
Details
No response
Build with regression
v0.0.17-12644-a346767a
Attach two log files (from solarmystic)
Not working with 12644
RPCS3.log
Working with 12640
RPCS3.log
Attach capture files for visual issues
No response
System configuration
No response
Other details
No response
The text was updated successfully, but these errors were encountered: