-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
MotorStorm: Arctic Edge ghosting issue #15241
Comments
Can you try the latest ppsspp build? |
Does it happen with:
Typically, those settings may help ghosting. I can imagine during a boost, they may have wanted to show a "trail" of the car to emphasize how fast the boost was making it go. -[Unknown] |
Tried, no luck. Also tried a bunch of other settings and combinations. |
This is only can reproduce on OpenGL? how about Vulkan? |
Have you tried to change the Rendering mode from Buffered rendering to Skip buffered effects (reset the game if it's on during the change)? I had something similar happen in my own issue #15232 changing that settings seems to have fixed it. |
I tried both. Didn't notice any difference.. |
Tried, no luck. |
FIXED: Thank you everyone for your help! |
I don't think skipp buffered rendering is the right solution. |
I have a likely similar issue about this but can only reproduce on vulkan. |
The over-bright issue you're facing can be fixed by using a cheat that disables bloom. |
Cheat and not using default settings on ppsspp is not a proper fixed. My issue there is not over bright, watch my screen recording. |
That's weird! I'm using the same version of ppsspp on my OnePlus 7T with latest Android 11 version. Everything is working fine on my phone, but then again I'm using the European version of motostorm that fixes the broken shadows. Plus I'm not using any cheats or hacks/fixes. |
Try my work around fix @SolidSnake013 |
@SolidSnake013 no feedback? |
It does run without but looks really bad, don't want reports of this.
How is this now? |
You do still seem to have a corrupt speedomoter graphic though :/ |
Software rendering also behave like that in speedometer. |
Everything looks okay up until 815/896, which looks like this (512x296, the game has some internal AA): Then through 845/896, it scales it down to 480x272, which still looks fine. 846/896 seems to use a capture of the previous frame at (0x0417c000) to apply the motion effect. 847/896 through 862/896 then update that screenshot for the next frame. That's when it goes to draw the speedometer from 0x041b4c00, at 863/896. The texture is CLUT4, bufw=128, 128x128, so it's 8KB. It looks completely corrupt: The CLUT looks maybe believable, though. Just to map out VRAM a bit: 0x04000000 - 0x04098000: presumably other framebuffer? (extra 8 height to align height to 16, no gap) The front/back looks quite funny. I almost wonder if only the CLUT is wrong: The speedometer itself looks also quite corrupt: What's interesting here especially is you can mostly see the corruption ends at a certain point 2/3 through the texture. Basically it looks like everything after the boost framebuffer is corrupted. Mapping out the VRAM makes it easy to see that the corruption lasts from the boost framebuffer (0x0417C000) until about 0x041C0000, which happens to be 256 * 272 * 4 later. And that's exactly the region/scissor setting for that framebuffer. Based on verts, the game only ever draws to 256x128, and in fact textures from it using 256x128. My guess is that:
I'm not sure what's reading the frame, we may be able to use the block transfer create framebuf thing to avoid a copy if the CPU doesn't need it, but I think it does for those environmental effects. Does this render correctly in the software renderer without using a save state? Edited framedump without any bloom issues (but the VRAM is already corrupt here, looks wrong on PSP as well): -[Unknown] |
Game or games this happens in
UCES-01250 - MotorStorm Arctic Edge
What area of the game / PPSSPP
Using boost causes a static image to float on screen.
Doesn't appear while regular driving, only appears when using boost.
What should happen
It shouldn't appear.
Logs
No response
Platform
Android
Mobile phone model or graphics card
OnePlus 7
PPSSPP version affected
V1.12.3
Last working version
No response
Graphics backend (3D API)
OpenGL / GLES
Checklist
The text was updated successfully, but these errors were encountered: