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

VBA Next and 32bit achievement conditions #126

Open
Alfex3 opened this issue Sep 19, 2019 · 5 comments
Open

VBA Next and 32bit achievement conditions #126

Alfex3 opened this issue Sep 19, 2019 · 5 comments

Comments

@Alfex3
Copy link

Alfex3 commented Sep 19, 2019

Putting a value over 0x7fffffff in an achievement condition causes the game not to load if using VBA Next core. It will just show a black screen.

@Alfex3
Copy link
Author

Alfex3 commented Sep 19, 2019

Posted in the wrong place. It works perfectly in RALibretro. It's a RetroArch issue.

@Alfex3 Alfex3 closed this as completed Sep 19, 2019
@Alfex3 Alfex3 reopened this Sep 19, 2019
@Alfex3
Copy link
Author

Alfex3 commented Sep 19, 2019

Noticed this is about vba-next, so it's the right place

@negativeExponent
Copy link
Contributor

achievement condition? where is that. if this is for RaLibretro, they are maintaining their own core.

@Alfex3
Copy link
Author

Alfex3 commented Sep 19, 2019

Sould I close this issue and open it in RetroArch repository? I was editing the achievements from Final Fantasy Tactics Advance to make them compatible with european ROM. I got a private message from an admin in RetroAchievements, telling me that 32bit values over 7fffffff break RetroArch support. I checked the 4 cores which are said to be compatible with achievements in Libretro docs and the other 3 unlocked achievements, but when I tried VBA Next, a black screen appeared. Then I tried other games and they worked fine. Then, I opened another game with RAVBA and I modified an achievement by adding a condition like the one I described, and when I loaded the game in RetroArch with VBA Next it only showed a black screen.

@negativeExponent
Copy link
Contributor

this may be fix in this PR #135

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

2 participants