-
Notifications
You must be signed in to change notification settings - Fork 0
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
Mass Effect 3 #99
Comments
@shinra-electric do you have a log? The black background could be due to shader error |
There doesn't seem to be anything useful in the log (that I can see) This error did show up in Terminal when trying to run the intro cutscene though: |
I managed to capture a gpu trace from in-game, where the HUD is working: (Looks like file.io was bought over by Limewire. I didn't know Limewire still existed...) |
@shinra-electric Looks like there are some strange issues with framebuffer fetch in this game. Could you please try turning it off in |
@shinra-electric great! The low FPS would probably require some profiling, but I doubt that it's bottlenecked. More like it's waiting for something. Could you please try this build to see if it works even with framebuffer fetch enabled? |
With this build, the title screen and menus are working even with the framebuffer fetch enabled. |
I'm not sure if you changed anything related to Vulkan in that build, it's crashing on launch:
Edit: |
@shinra-electric that’s a regression that has been merged to main Cemu (so macOS no longer works on it 🙂), but it’s a very easy fix (and should get fixed soon). But if the menus are working then I supposed that there was the same issue ingame |
Yep, in-game is working. Here is a gpu trace from the intro cutscene |
@shinra-electric does this image appear later in the intro? |
Wait, you said that it's in game? |
As for the strange patterns on hands, that seems to be caused by a corrupted normal texture/incorrect decoding of it |
No, it doesn't. Here is a video of the intro on YouTube starting at 3:19.
Yes, I had to use Vulkan to get past the intro video and make a save, then when loading with Metal with the test build, in-game works. Edit: Did you mean the gpu trace? No, that's from the intro when it drops to 2fps. |
Vulkan has quite a few rendering issues too, but the intro plays at full speed. |
Oh, alright, so the trace is still from intro. In that case, it's even more interesting, since it seems like the intro has already finished running from the game's perspective. Could you maybe try running it from Xcode and sending the console output? Might be another GPU hang |
Here is the lldb output. There was nothing new printed there when it started going into the intro sequence. |
I see. Don’t know what could cause it then |
I tried this build with framebuffer fetch off, but it doesn't render in-game. (Same as with framebuffer on) |
@shinra-electric but it did render in-game on the build that broke Devil’s Third? Also, does the menu render correctly (with framebuffer fetch off) |
Yes, I mentioned it was working here. (Actually, for in-game I said I would report back later, which I did here).
No, the whole thing is the same as with framebuffer fetch on. Title screen, menu and in-game. |
Description
Gets to the title screen, background doesn't display.
Main menu doesn't display, but works in the background.
Loading screen works (I used Vulkan to create a save so I could get past the main menu).
Most of the intro cutscene runs at less than 2fps, blackscreens after a certain point.
Black screen in-game (audio works, I don't think the game is running)
Screenshots
Title Screen:
Main Menu (menu works in background):
MoltenVK status
Goes in-game with Vulkan, though there are graphical issues.
Title Screen:
Main Menu:
In-game cutscenes:
In-game:
GPU Traces
Title screen and Main Menu:
https://file.io/IgGb9vh8szHs
Cemu Metal version
testing2.1.0
Mac
M1 Pro
macOS 15.2
Similar reports
Issues
page yetThe text was updated successfully, but these errors were encountered: