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
Romance of the Three Kingdoms VII [SLPM-62010] font bug #1628
Comments
Please follow the issue template( https://github.com/PCSX2/pcsx2/blob/master/ISSUE_TEMPLATE.md ) and describe your issue in detail, not just the serial number and a vague two word description of the issue. |
PCSX2 version: development builds v1.5.1488 PCSX2 options: default Plugins used: default Last known version to work: lastest version use old plugin GSdx32-r5612 PC specifications: CPU: Intel 4710mq GPU: GTX 970m OS: Windows 10 64 Bit) |
Can you upload a multiple frames (hold CTRL + SHIFT + F8 for 2-3 seconds while the font bug is visible) GS Dump of the issue? http://forums.pcsx2.net/Thread-How-to-create-a-proper-GS-dump |
I'm presuming it's the same bug as this http://forums.pcsx2.net/Thread-Bug-Report-Romance-of-the-Three-Kingdoms-8-NTSC-U-C |
In all likelihood yes, the bug seems to affect several of RotTK games. |
@h188cm could you provide the gs dump asked by flatout ? It would really increase the probability that I fix the bug. |
gs dump download |
@h188cm Thanks for the dump 👍 @gregory38 It's definitely still there with the latest builds, so the recent improvements have not affected it. |
SLPM62010,font bug
Added by refractionpcsx2:
Text on the menu has always displayed incorrectly however it was mostly right back in the 1.0.0 days. After sudonim's changes back in 2fbcafc the text became black and has stayed as such ever since.
Related forum thread with screenshots and info: http://forums.pcsx2.net/Thread-ROTK8
Followup thread re-highlighting the issue: http://forums.pcsx2.net/Thread-Bug-Report-Romance-of-the-Three-Kingdoms-8-NTSC-U-C
Note has been made in GSClut.cpp line 162 under WriteCLUT32_I8_CSM1
The text was updated successfully, but these errors were encountered: