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

Star Wars force unleashed [Screen Overlay problem] #9572

Closed
Levan7 opened this issue Apr 8, 2017 · 57 comments · Fixed by #15696
Closed

Star Wars force unleashed [Screen Overlay problem] #9572

Levan7 opened this issue Apr 8, 2017 · 57 comments · Fixed by #15696
Labels
GE emulation Backend-independent GPU issues
Milestone

Comments

@Levan7
Copy link

Levan7 commented Apr 8, 2017

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.

DebugLog.zip
ulus10345_00000

@sum2012
Copy link
Collaborator

sum2012 commented Apr 8, 2017

Does v1.3 have his problem ?

@Levan7
Copy link
Author

Levan7 commented Apr 8, 2017

@sum2012
Hm, no it doesn't strange
ulus10345_00000

@sum2012
Copy link
Collaborator

sum2012 commented Apr 8, 2017

Can you test v1.3-xxx to find out which version first have problem in
http://buildbot.orphis.net/ppsspp/index.php?m=fulllist ?

@Levan7
Copy link
Author

Levan7 commented Apr 8, 2017

@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
ulus10345_00000

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.

@hrydgard
Copy link
Owner

hrydgard commented Apr 8, 2017

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?

@Levan7
Copy link
Author

Levan7 commented Apr 9, 2017

@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

@unknownbrackets
Copy link
Collaborator

Possibly related: #3064

-[Unknown]

@Levan7
Copy link
Author

Levan7 commented Jan 19, 2018

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

@ghost
Copy link

ghost commented Jun 1, 2018

Still have an issue on the latest ppsspp version 1.6.2
but restarting the ppsspp fix the issue.

@unknownbrackets
Copy link
Collaborator

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]

@ghost
Copy link

ghost commented Jun 1, 2018

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

@ghost
Copy link

ghost commented Jun 1, 2018

and I think 4XMSAA also help to fix this issue since I always enable that in the developers options in Android Settings 😅

@hrydgard
Copy link
Owner

hrydgard commented Aug 9, 2019

How about now?

@hrydgard hrydgard added this to the v1.10.0 milestone Aug 9, 2019
@jullebarge
Copy link

I have the same problem on Android with version 1.9.3-164.
Tried various settings but nothing remove those lines.

@hrydgard
Copy link
Owner

Don't fast-forward on the loading screens and it should be OK. Use Rendering Mode = Buffered.

@jullebarge
Copy link

I don't use fast forward and I'm already in buffered mode, still I have those red lines.

@hrydgard hrydgard modified the milestones: v1.10.0, v1.11.0 Mar 30, 2020
@2bndy5
Copy link

2bndy5 commented May 1, 2020

Posted this in the closed (seemingly identical) issue by mistake. #3064 (comment)

@ghost
Copy link

ghost commented Jun 4, 2020

@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

@2bndy5
Copy link

2bndy5 commented Jun 4, 2020

@ghost
Copy link

ghost commented Jun 4, 2020

@2bndy5 thanks for the dump
Here's the results (OpenGL)

Hardware Rendering

Screenshot_20200604-141914HW

Software Rendering

Screenshot_20200604-142028SW

@Kzitold
Copy link

Kzitold commented Nov 24, 2020

I had to switch the backend to Direct3D 9.

@hrydgard hrydgard removed D3D11 Direct3D 11 D3D9 Direct3D 9 labels Dec 26, 2020
@Panderner
Copy link
Contributor

@Gamemulatorer Red Overlay Fix cheat can cause graphical glitches and FMV videos does not display

Here's a Title Screen:
Screenshot_2021-05-31-20-03-31-691_org ppsspp ppsspp

@ghost
Copy link

ghost commented May 31, 2021

Adding this game to PixelDepthRounding compat.ini sometimes fix this red overlay screen issue on my phone.

OpenGL

Screenshot_2021-05-31-22-39-07-508_org ppsspp ppsspp

Vulkan

Screenshot_2021-05-31-22-38-24-814_org ppsspp ppsspp
Redmi Note 9 Mediatek Helio G85 Mali G52 MC2 GPU

@hrydgard
Copy link
Owner

Only sometimes?

I don't know how that setting could be related though..

@ghost
Copy link

ghost commented May 31, 2021

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.

@ghost
Copy link

ghost commented Sep 27, 2021

This still occuring issue is annoying.

@ghost
Copy link

ghost commented Sep 28, 2021

This issue is very rare to happen using the latest git but yeah still annoying issue.

@ghost
Copy link

ghost commented Oct 5, 2021

This still occuring issue is annoying.

@mojojojodojo Try my work around if your playing this game on pc see ~ #12949 (comment)

@unknownbrackets
Copy link
Collaborator

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]

@ghost
Copy link

ghost commented Oct 19, 2021

Yeah putting I/O at "simulate UMD delays" seem to help.

@ghost
Copy link

ghost commented Oct 20, 2021

Changing I/O method doesn't really fix this the only solution I found is by adding this game to Force04154000Download compatibility.

@CristobalManga
Copy link

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.

@ghost
Copy link

ghost commented Oct 20, 2021

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

@2bndy5
Copy link

2bndy5 commented Oct 20, 2021

@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.

@ghost
Copy link

ghost commented Oct 20, 2021

@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)

@Qr0e
Copy link

Qr0e commented Oct 21, 2021

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).

@ghost
Copy link

ghost commented Jul 16, 2022

This issue can be fixed by adding this game to AllowLargeFBTextureOffset see ~ #15691

@SilentMRG
Copy link

SilentMRG commented Jul 26, 2022

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!

@ghost
Copy link

ghost commented Jul 27, 2022

@SilentMRG use hack setting lower resolution for effects (reduce artifacts) set to aggresive to fix the crt line graphic glitch.

@2bndy5
Copy link

2bndy5 commented Jul 27, 2022

I would consider the pseudo CRT filter as a new issue. Even if it a regression, it should get its own thread/issue.

@SilentMRG
Copy link

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/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
GE emulation Backend-independent GPU issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.