Seems like some patches are not working
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- computer-graphics, game-dev
Research direction
Start by reproducing Echo Night Beyond (SLUS-20928, CRC 2DE16D21) with ParaLLEl and compare it with Vulkan. Inspect how the supplied pnach patch and the No Interlacing patch line are handled, then determine whether the rendering path applies them. Done means the game renders without the reported interlacing and duplicated image under ParaLLEl.
Written by the indexing model from the issue text.
Description
Hey Im trying to play Echo Night Beyond (Serial: SLUS-20928)(CRC: 2DE16D21).
The problem is this game have very much noticeable offset in rendering that makes the image a lot blurry (and like "duplicated"), it comes from interlacing, that even in PCSX2 dont get turned off no matter the GS setting.
I managed to get the best patch in PCSX2 that corrects this,
//No Interlacing + 60FPS
patch=1,EE,0013FFDC,word,10000014 //10200014
However it wont work on LRPS2 when using ParaLLEl (it works in vulkan, most of the time).
The pnach file has the correct CRC number with the patch lines, but it wont work, so interlacing and duplicate image persists.
Also in the patches git, there is this,
Does it have something too do with that?
Edit: sorry for excessive brightness i have hdr enabled, but still, first image the letters cant be read, in the 2nd they can (does not happen only with text, its all the in game rendering)
This is how it currently looks
An this how it should kinda look (does not with ParaLLEl)
Id like a workaround, i prefer playing with the looks that ParaLLEl gives.
- Dominant language
- C
- Stars
- 90
- Forks
- 34
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 9
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from libretro/parallel-ps2
-
Difficulty 4/5 3-5 days Newbie friendliness 12/100
libretro/parallel-ps2#195 · 8 comments ·
Maintainers usually reply within 1 day
-
Apple silicon: loading a save state crashes with SIGBUS in state_read (write to a read-only page)Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
libretro/parallel-ps2#194 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
libretro/parallel-ps2#192 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
libretro/parallel-ps2#185 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
libretro/parallel-ps2#184 ·
Maintainers usually reply within 1 day
All issues in libretro/parallel-ps2
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
JulianKemmerer/PipelineC#395 ·
-
upstream-blocked
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
libretro/parallel-n64#858 ·