-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
415607E2 - Spider-Man 3 #203
Comments
This comment was marked as resolved.
This comment was marked as resolved.
Tested on: xenia-canary/xenia-canary@3675d6a Finished tutorial, swung around the New York for about 3 minutes. FPS in 60-90 range with shaders cached, |
My hardware really isn't as up-to-date (Xeon E3-1270 v3, GTX 1070, 16GB RAM), without readback resolve and vsync disabled I get around 60-70FPS when swinging around the city and above 100 FPS when standing at the top of higher buildings, it's equal to my performance in SM3 PC version with removed 30FPS cap. With RR however it's around 30FPS (could say stable 30) when swinging and 35-40FPS when standing at the top of a building depending how much of the city is in the view. May shader caching have anything to do with this? I only have the cache stored in cache_host folder, from what I read there's no pre-caching feature in Xenia. Also is there a chance you have some performance optimizations enabled in your Xenia config? |
Well you said it yourself, it's not capped at 30FPS. |
Validation
Xbox 360 Marketplace link
https://marketplace.xbox.com/en-US/Product/Spider-Man-3/66acd000-77fe-1000-9115-d802415607e2
Xenia version
https://github.com/xenia-canary/xenia-canary/commit/97d36d6bcce6fd60952c9d6172d98a24c50e0232/
Issues
Overall the game is in a playable state, however there's a major lighting issue which can only be resolved by enabling readback resolve which caps the game at 30 FPS. Seeing i.e. Nier has a patch removing such cap it would be great to possibly have it for SM3
Log
xenia.zip
Screenshots
Labels
state-playable gpu-readback gpu-shader-errors
The text was updated successfully, but these errors were encountered: