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

GUI: Bring "SPU GETLLAR Busy Waiting Percentage" to UI #16827

Open
TigiHof opened this issue Mar 8, 2025 · 13 comments
Open

GUI: Bring "SPU GETLLAR Busy Waiting Percentage" to UI #16827

TigiHof opened this issue Mar 8, 2025 · 13 comments

Comments

@TigiHof
Copy link

TigiHof commented Mar 8, 2025

Quick summary

"F.E.A.R. 2 - Project Origin" has severe screen flickering and constant crashes!

Details

Release rpcs3-v0.0.32-16614 seems to have introduced the described problems, if only subtly. Subsequent releases since then seem to have made the problems worse, so that "F.E.A.R. 2" currently is completely broken and unplayable.

The last release that works perfectly fine for me is rpcs3-v0.0.32-16611.

Log:
rpcs3-v0.0.32-16611-feff2ba0_win64.log

RSX capture:
BLUS30251_rpcs3-v0.0.32-16611-feff2ba0_win64_capture.rrc.gz

Release rpcs3-v0.0.32-16614 introduces slight flickering to the "Press to continue" text and to the "X button" icon in the game menu.

Image

Also to the video sequence that begins after not pressing any button in the main menu for 60 seconds.

Image

Much worse is that rpcs3-v0.0.32-16614 is also the first release where "F.E.A.R. 2" begins to randomly crash (see log). This can take several minutes in this version.

Log:
rpcs3-v0.0.32-16614-5b973448_win64.log

RSX capture:
BLUS30251_rpcs3-v0.0.32-16614-5b973448_win64_capture.rrc.gz

As said before, these symptoms have become worse in subsequent releases: the flickering is much more intense and the crashes much more frequent. Of course this also the affects the gameplay itself (if you are able to make it beyond the menus without a crash in the first place).

Crash log from the current release rpcs3 v0.0.35-17581-26495a84:

rpcs3 v0.0.35-17581-26495a84_win64.log

Please let me know if you need any additional info!

Build with regression

v0.0.32-16614-5b973448

Attach two log files

rpcs3-v0.0.32-16611-feff2ba0_win64.log

rpcs3-v0.0.32-16614-5b973448_win64.log

rpcs3 v0.0.35-17581-26495a84_win64.log

Attach capture files for visual issues

BLUS30251_rpcs3-v0.0.32-16611-feff2ba0_win64_capture.rrc.gz

BLUS30251_rpcs3-v0.0.32-16614-5b973448_win64_capture.rrc.gz

System configuration

No response

Other details

No response

@digant73
Copy link
Contributor

digant73 commented Mar 8, 2025

so it is broken since #15623

@AniLeo AniLeo added the CPU label Mar 9, 2025
@AniLeo AniLeo changed the title [Regression] F.E.A.R. 2 - Flickering and Crashes [Regression] F.E.A.R. 2 - Flickering and Crashes (#15623) Mar 9, 2025
@TigiHof
Copy link
Author

TigiHof commented Mar 9, 2025

This issue is obviously related to #16008 where the same problems are described for another LithTech engine game. I also tried "Condemned 2 - Bloodshot", yet another game with this engine. Result: same errors! So clearly an engine related bug.

@elad335
Copy link
Contributor

elad335 commented Mar 9, 2025

set "SPU GETLLAR Busy Waiting Percentage" to 101 in config yml of the game.

@TigiHof
Copy link
Author

TigiHof commented Mar 9, 2025

set "SPU GETLLAR Busy Waiting Percentage" to 101 in config yml of the game.

Yes, that works! The game runs perfectly fine with this setting!

@elad335 elad335 closed this as completed Mar 9, 2025
@elad335
Copy link
Contributor

elad335 commented Mar 9, 2025

Closed because it is known that the default behaviour is a performance hack, though most titles are fine with it and are benefited from it. Should be added to wiki.

@TigiHof
Copy link
Author

TigiHof commented Mar 9, 2025

In what way is simply closing this issue an acceptable solution? Do you really expect every user who wants to play "F.E.A.R. 2" to manually edit the config file?

@AniLeo
Copy link
Member

AniLeo commented Mar 9, 2025

Why can't this behaviour simply be part of Accurate SPU GETLLAR?

@elad335
Copy link
Contributor

elad335 commented Mar 9, 2025

Why can't this behaviour simply be part of Accurate SPU GETLLAR?

Accurate GETTLAR is not a setting anymore, but maybe a checkbox can be added to set this value to 101 specifically.

@elad335 elad335 reopened this Mar 9, 2025
@elad335 elad335 added the GUI label Mar 9, 2025
@digant73
Copy link
Contributor

digant73 commented Mar 9, 2025

I (as user) don't know why some settings are hidden and/or their meaning/effects. But if they are the only way to make some games properly working then the setting should be available in the GUI. Maybe providing a self explanatory name and description (than SPU GETLLAR). It seems that this setting could potentially fix other games using the same engine, so pretty important.

@elad335
Copy link
Contributor

elad335 commented Mar 9, 2025

We have many settings affecting compatibility of games, we expect users to turn none of them on unless they are instructed to by the wiki or on forums or on discord.

@elad335 elad335 assigned AniLeo and Megamouse and unassigned elad335 Mar 9, 2025
@elad335 elad335 changed the title [Regression] F.E.A.R. 2 - Flickering and Crashes (#15623) GUI: Bring "SPU GETLLAR Busy Waiting Percentage" to UI Mar 9, 2025
@AniLeo
Copy link
Member

AniLeo commented Mar 9, 2025

This should either be a checkbox or just the default behaviour, what's the performance penalty?

@kd-11
Copy link
Contributor

kd-11 commented Mar 10, 2025

Agree, users should never have to open config.yml unless instructed to do so by a developer for debugging purposes.

@elad335
Copy link
Contributor

elad335 commented Mar 10, 2025

@AniLeo Performance panelty is pretty high, for P5 it's about 30% looking at the pr results.
Should be a checkbox, but when it's not set to 101 it should save the previous value on load and restore it on save so it won't override values set in config.
In gui it can be called "Disable SPU GETLLAR Spin Optimization"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants