Star Wars force unleashed [Screen Overlay problem]
Levan7 opened this issue · comments
I am using the PPSSPP v1.4-56-gb1a530b Windows 64 bit build and started Forced unleashed and noticed that the game has a screen overlay in game, the menus work fine.
Does v1.3 have his problem ?
Can you test v1.3-xxx to find out which version first have problem in
http://buildbot.orphis.net/ppsspp/index.php?m=fulllist ?
@sum2012
Ok i found a problem with my report, when i was regressive testing. I noticed that sometimes the 1.3.xx builds get that over layer and sometime they don't (default settings) even the PPSSPP v1.4-56-gb1a530b didn't get that over layer after few tries
I was messing with this for some time and it's like ppsspp is caching and if it chases properly the first time then every time you start the game the screen is ok but if you delete the mstick and start the game and it will show you the overlay then every next time you start you will have a problem with the screen.
I think the problem occurs on the first loading screen.
Try this: Right click on the game to get the game ID (4 letters, 5 numbers).
Then open assets/compat.ini and enter the game ID under [ClearToRAM] like the others.
Does that help?
@hrydgard
Well it fills like it did help, at least couldn't reproduce after trying multiple times.
i made a entry
under [ClearToRAM]
[hashtag] Star Wars: The Force Unleashed
ULUS10345 = true
Possibly related: #3064
-[Unknown]
Still an issue on v1.5.4-376-g3aca9e3ca
However i think it happens when i fast forward the ladings
The software rendered isn't getting the same issues
Still have an issue on the latest ppsspp version 1.6.2
but restarting the ppsspp fix the issue.
Does this only happen when using frameskip, fast forward, or alternate speed? Or does it happen even if you don't use those features?
-[Unknown]
Default Settings this screen overlay still happen and only happen in the 1st boot/start of the game after that I changed from buffered rendering to skip-buffer effects and restart the ppsspp it's fix the problem
and I think 4XMSAA also help to fix this issue since I always enable that in the developers options in Android Settings 😅
How about now?
I have the same problem on Android with version 1.9.3-164.
Tried various settings but nothing remove those lines.
Don't fast-forward on the loading screens and it should be OK. Use Rendering Mode = Buffered.
I don't use fast forward and I'm already in buffered mode, still I have those red lines.
Posted this in the closed (seemingly identical) issue by mistake. #3064 (comment)
@Levan7 @jullebarge @2bndy5 Could you create a frame dump.? Doesn't matter if the frame dump is created on PC or Android.
https://github.com/hrydgard/ppsspp/wiki/How-to-create-a-frame-dump
I had to switch the backend to Direct3D 9.
I can reproduce this on my phone (Adreno 650, driver version: 512.501.0) but not on my PC (GTX 1070, driver version: 461,40) both using the Vulkan renderer. So this might be a driver bug.
This seems to be fixed in 1.11 bit there are other problems now.
The scene seems a bit too dark, fog is too strong on character models and the lightsaber trail effect has a weird checkerboard pattern. The lightsaber pattern appears to be a regression in 1.11.
Game on actual hardware for reference (specifically the brightness):
We have applied Adreno driver fix
What do you mean, is there a workaround for a driver bug in PPSSPP now? If so, can you link the commit, I'm curious.
Could you try exporting a GE frame dump of the lightsaber problem? These help a lot. Just make sure to export it when you see the issue - it's almost like a screenshot. If you make it while the issue isn't happening, it won't help.
See here for instructions - it's not hard and works on Android too:
https://github.com/hrydgard/ppsspp/wiki/How-to-create-a-frame-dump
You can zip that and then drag and drop it into a reply here.
-[Unknown]
The lightsaber bug only happens when hardware transform is turned off, so I'm not sure if this is actually a regression.
Also noteworthy that I can reproduce it on Windows (Nvidia, Vulkan renderer).
ULES00982_0009.zip
The fog/brightness bug does not happen on Windows with the Vulkan renderer. It does happen with D3D11 though.
And I also managed to get the overlay again. This time on Windows with Vulkan.
I can't reproduce this using the dump both OGL and VK backend.
I tried this game the red screen overlay still present on both OpenGL and Vulkan, but in OpenGL this game is heavily lag unlike Vulkan this game is running full speed.
OpenGL
Vulkan
I tasted this and noticed that it happened on PC Vulkan when fast forwarding in loading maybe the emulation has problems when loading faster or slower than it should ?
@Levan7 try this cheat code
_C1 Red Overlay Fix
_L 0xE001ADAE 0x003E94BE
_L 0x203E94BC 0xADA00000
I tried that cheat code both OpenGL and Vulkan and result is good 👍
Vulkan performance for my POCO M3 is slower than OpenGL in 4x resolution
OpenGL:
Vulkan:
And I'm not using red overlay cheat.
good to know, thanks!
Vulkan performance for my POCO M3 is slower than OpenGL in 4x resolution
OpenGL:
Vulkan:
And I'm not using red overlay cheat.
With red overlay cheat code this game is running full speed at 4X rendering resolution on my RedmiNote 9
OPENGL
VULKAN
The red overlay is the cause of lag on my phone 🤷
@Panderner I also notice on your screenshots that is too dark compare to mine 🤣
I tested Windows 10 PC The Brightness is ok for OpenGL and Vulkan but it's too dark for D3D9 and D3D11
@Gamemulatorer Red Overlay Fix cheat can cause graphical glitches and FMV videos does not display
Here's a Title Screen:
Adding this game to PixelDepthRounding compat.ini sometimes fix this red overlay screen issue on my phone.
OpenGL
Vulkan
Redmi Note 9 Mediatek Helio G85 Mali G52 MC2 GPU
Only sometimes?
I don't know how that setting could be related though..
Only sometimes?
I don't know how that setting could be related though..
On OpenGL 5 out of 10 tries the screen overlay will show up but on Vulkan only twice out of 10 tries the red overlay screen show up.
This still occuring issue is annoying.
This issue is very rare to happen using the latest git but yeah still annoying issue.
This still occuring issue is annoying.
@mojojojodojo Try my work around if your playing this game on pc see ~ #12949 (comment)
In #15026, it was reported that somehow remote disc streaming can affect this. That makes me think that perhaps, in some way, IO timing might be at play here. Even using Fast, the timing when RAM is updated is slightly impacted by the IO speed since it's run on a thread.
-[Unknown]
Yeah putting I/O at "simulate UMD delays" seem to help.
Changing I/O method doesn't really fix this the only solution I found is by adding this game to Force04154000Download compatibility.
Cambiar el método de E / S realmente no soluciona esto, la única solución que encontré fue agregar este juego a la compatibilidad Force04154000Download.
In fact, if it fixes the problem.
But this way.
When the problem is active.
When you change the I / O, the error is fixed.
No matter which option you choose.
By the way, can you tell me where do I get compat.ini, in android? On PC I get it easy, but on android I can't get it.
Here's the proof!
⬇️
Force04154000Download OFF
Screenrecorder-2021-10-20-09-59-05-756.mp4
Screenrecorder-2021-10-20-09-59-23-431.mp4
Force04154000Download ON
star.wars.clone.wars.mp4
star.wars.force.unleashed.mp4
Here's my compat.ini file @CristobalManga
⬇️
compatibility.zip
@Gamemulatorer Your compat.ini does fix the graphics issue, but it makes the game speed unplayable. Please stop spamming this fix. I'd rather see this issue resolved in a more sustainable way.
@CristobalManga I think the compat.ini file needs to be created in the PSP/SYSTEM folder on your android device's internal storage. The directory should already exist once the PPSSPP emulator is installed. However, here is the warning at the top of the compat.ini file:
This file is not meant to be user-editable, although is kept as a separate ini
file instead of compiled into the code for debugging purposes.The uses cases are strict:
- Enable fixes for things we can't reasonably emulate without completely ruining
performance for other games, such as the screen copies in Dangan Ronpa- Disabling accuracy features like 16-bit depth rounding, when we can't seem to
implement them at all in a 100% compatible way- Emergency game-specific compatibility fixes before releases, such as the GTA
music problem where every attempted fix has reduced compatibility with other games- Enable "unsafe" performance optimizations that some games can tolerate and
others cannot. We do not currently have any of those.This functionality should NOT be used for any of the following:
- Cheats
- Fun hacks, like enlarged heads or whatever
- Fixing general compatibility issues. First try to find a general solution. Try hard.
TL;DR -> compat.ini is not a viable solution
@unknownbrackets @mojojojodojo I look forward to your investigations.
@Gamemulatorer Your compat.ini does fix the graphics issue, but it makes the game speed unplayable. Please stop spamming this fix. I'd rather see this issue resolved in a more sustainable way.
Im just suggesting a workaround lol 😂
I also mentioned about the performance penalty in #12949 (comment)
I fixed mine by just switching on Auto Frame Skip in the settings. Set Frame skip to 1 and Frame skipping type to Percent of Fps (not sure if this actually did anything but all of my games still run fine).
This issue can be fixed by adding this game to AllowLargeFBTextureOffset see ~ #15691
Hello...
Unfortunately, the bug is still present, but this time it's not red, but transparent (Like this: #15691 (comment)), it even looks like a CRT filter, with vertical lines, hehehe.
Strangely, the bug occurs in the first Starkiller mission and the third mission in Raxus Prime. The Darth Vader quest and the Jedi Temple quest do not have the bug. And I didn't play the game to the end so I can't say if the bug recurs in other stages.
All the rest of the effects work like a charm! The frame rate is also very good and I haven't seen any other bugs.
The game has been tested in DirectX 9 and OpenGL. Not tested in DirectX 11 as my Laptop (Windows 7 Ultimate 64-bit - i5 2.64 GHz - 4GB DDR3 RAM and Intel HD Graphics 1000) is very old and doesn't support this API.
Note: I used version 1.13.
Thank you for everything!
@SilentMRG use hack setting lower resolution for effects (reduce artifacts) set to aggresive to fix the crt line graphic glitch.
I would consider the pseudo CRT filter as a new issue. Even if it a regression, it should get its own thread/issue.
use hack setting lower resolution for effects (reduce artifacts) set to aggresive to fix the crt line graphic glitch.
It worked my man! Thank you very much! =D You saved my hours of fun. \o/