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

PCSX2 missing automatic Software FMV Fix #3900

Closed
SHuth78 opened this issue May 13, 2021 · 5 comments
Closed

PCSX2 missing automatic Software FMV Fix #3900

SHuth78 opened this issue May 13, 2021 · 5 comments

Comments

@SHuth78
Copy link

SHuth78 commented May 13, 2021

Currently Batocera includes a development version of PCSX2. (Can't really tell wich, the config app doesn't say in about)
Unfortunately somewhere since 1.6.0 the PCSX2 devs chose to remove the Automatic Software FMV game fix.

As far as i could find this is due to it causing issues when the game already runs in Software mode.
But really, who runs their games in Software mode?

This gamefix is essential to fix FMV problems in many, many games.
Popular examples being Kingdom Hearts, Grandia 3 and FFX-2.

Therefore i'd like to suggest "downgrading" to stable 1.6.0 if possible.

@SHuth78 SHuth78 changed the title PCSX2 missing automatic Software FMV Fix. PCSX2 missing automatic Software FMV Fix May 13, 2021
@liberodark
Copy link

That is not possible to downgrade too many features is on 1.7.0 dev

@nadenislamarre
Copy link
Collaborator

i guess we shoudl find why " the PCSX2 devs chose to remove the Automatic Software FMV game fix."
there is proably a very good reason.

@SHuth78
Copy link
Author

SHuth78 commented May 16, 2021

Here is the statement:
PCSX2/pcsx2#3806

And here is the ongoing thread for (some) affected games:
PCSX2/pcsx2#3805

So basicly the ongoing work broke the hack, and they chose to ignore it in favor of fixing the HW renderers.
Sure makes sense in the long term but alreay half a year has passed and the HW renderers still have mostly the same issues, so 1.6.0 is still the better option imho.

@nadenislamarre
Copy link
Collaborator

reverting to 1.6.0 is not easy. 1.6.0 was a 32 bits version and we changed our way to do and switch it to 64 bits now that it is allowed by developent versions. The performances increased seriously with the dev versions (mainly thanks to that), and on my computer, it is night and day. For sure, we will not come back to 1.6.0 => not simple, and performances are really under.
what we can do is to upgrade the dev version (for 32, not 31).

@SHuth78
Copy link
Author

SHuth78 commented May 17, 2021

reverting to 1.6.0 is not easy. 1.6.0 was a 32 bits version and we changed our way to do and switch it to 64 bits now that it is allowed by developent versions. The performances increased seriously with the dev versions (mainly thanks to that), and on my computer, it is night and day. For sure, we will not come back to 1.6.0 => not simple, and performances are really under.
what we can do is to upgrade the dev version (for 32, not 31).

If it's that much trouble it's not worth it. I forgot about the whole 64bit thing tbh.
Lets live with the way it is and hope the next stable PCSX2 has a solution.

@SHuth78 SHuth78 closed this as completed May 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants