Skip to content
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

Open
4 tasks done
OkaymanXXI opened this issue Feb 7, 2024 · 4 comments
Open
4 tasks done

415607E2 - Spider-Man 3 #203

OkaymanXXI opened this issue Feb 7, 2024 · 4 comments
Labels
gpu-shader-errors Graphics shader issues, such as things being too bright, dark, or the wrong color. state-gameplay Title has functional gameplay.

Comments

@OkaymanXXI
Copy link

OkaymanXXI commented Feb 7, 2024

Validation

  • I've read the FAQ.
  • The Xenia build used is from a canary branch. (not MLBS/AlexVS/master/pull requests, etc)
  • This issue isn't for help (tech support) with Xenia, or a game.
  • I've checked if this game doesn't already have a compatibility report.

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

210159516-3293dfec-0865-46df-ae43-baadcf5268f4

Labels

state-playable gpu-readback gpu-shader-errors

This comment was marked as resolved.

@Sowa95
Copy link

Sowa95 commented Feb 7, 2024

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, vsync disabled and readback_resolve enabled. Standing at the top of a building and looking at the edge of a map well over 100 FPS. Definitely not capped at 30.

Spider-Man 3 avg
Spider-Man 3 max

@OkaymanXXI
Copy link
Author

OkaymanXXI commented Feb 8, 2024

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, vsync disabled and readback_resolve enabled. Standing at the top of a building and looking at the edge of a map well over 100 FPS. Definitely not capped at 30.

Spider-Man 3 avg Spider-Man 3 max

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?
P.S: In comparison SM Web of Shadows runs smooth enough to me with vsync disabled without a need in readback resolve

@Sowa95
Copy link

Sowa95 commented Feb 10, 2024

With RR however it's around 30FPS (could say stable 30) when swinging and 35-40FPS when standing at the top of a building

Well you said it yourself, it's not capped at 30FPS. Readback_resolve is one of the most demanding settings, that's why performance takes a big hit. Shader cache is automatic, what I meant by that is recorded FPS in my screenshots were not taken during shader compilation (it may stutter quite a bit at first). I was using default config with vsync disabled and readback_resolve enabled.

@Margen67 Margen67 added gpu-shader-errors Graphics shader issues, such as things being too bright, dark, or the wrong color. state-gameplay Title has functional gameplay. and removed gpu-shader-errors labels Sep 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gpu-shader-errors Graphics shader issues, such as things being too bright, dark, or the wrong color. state-gameplay Title has functional gameplay.
Projects
None yet
Development

No branches or pull requests

3 participants