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
simd.hpp vec_alloc verification failed since #11403 (Rosetta) #11409
Comments
What's the CPUID of VirtualApple btw? Can't find what capabilities it supports. |
Still getting the error when opening any game in the latest commit: |
Are you sure you're on latest commit @Red1860? There is no verification in line 120 anymore so your error should be impossible to trigger. Did you compile master yourself or are you using a build downloaded from somewhere? |
Very strange, it should be fixed in master. |
If this is still If the error message points to some different line or file then you'll need to tell which one it is. |
So I was trying to build it from source but I am getting this error
|
Building rpcs3 on mac isn't straightforward, there's a bunch of things that need to be done (including setting up and using x86-64 homebrew applications instead of the native ones). We don't have official build instructions yet, they will be added in future once things stabilize a bit. #11222 contains some vague instructions but some parts of it are out of date already. We will probably get an update from nastys once he has time to test this for himself. |
I've built master but now I get this error:
|
|
Thanks, I fixed bug |
Yep, #11413 fixes it. Thanks! |
Quick summary
Since #11403, launching any game results in:
Details
This seems to affect M1 Macs running RPCS3 with Rosetta. It doesn't seem to affect Intel Macs.
Commenting out line 120
ensure(~vec_allocated);
results in an error at line 373ensure(!g_vc->emit(op, r, std::forward<Args>(args)...));
, and removing the ensure around that line fixes the issue and RPCS3 is able to launch games.I've also tried deleting
Caches/rpcs3
andApplication Support/rpcs3
.0. Make sure you're running with settings as close to default as possible
1. Please provide exact build (or commit) information that introduced the regression you're reporting.
https://cirrus-ci.com/task/5042319962406912
2. Please attach TWO logs:
RPCS3_broken.log
RPCS3_noensure.log
6. Please provide your system configuration:
The text was updated successfully, but these errors were encountered: