pcsx2
pcsx2 copied to clipboard
[BUG]: (Persona 3 FES) Hashes with "xxxx-xxxx" instead of "xxxx-xxxx-xxxx" have trouble loading the texture
Describe the Bug
Example: "f331606d5d604a5b-00006640.dds" won't load, but "531bb5f705944073-3b07777cc9cb6b9-00006654.dds" will.
This is because "f331606d5d604a5b-00006640" only has 2 sets of numbers, instead of 3 like in "531bb5f705944073-3b07777cc9cb6b9-00006654"
I already have tried enabling "GPU Palette Conversion" and setting "Texture Preloading" to None
Reproduction Steps
d41fb8bd4eb48742-00005a00.dds and f331606d5d604a5b-00006640.dds have the same issue.
Expected Behavior
Both textures to load successfully.
PCSX2 Revision
1.7.3131.0
Operating System
Windows 10 (64bit)
If Linux - Specify Distro
No response
CPU
Ryzen 7 2700x
GPU
RTX 3060
GS Settings
Emulation Settings
GS Window Screenshots
No response
Logs & Dumps
Solved the issue with textures generating bad hashes and not loading. If a .tmx file (original texture from p3fes) has "UsesPalette" set to "False" and "PaletteCount" set to "0," PCSX2 will generate a hash with "xxxx-xxxx," instead of "xxxx-xxxx-xxxx." So, I just modified the .tmx file and now it generated a proper new hash with "xxxx-xxxx-xxxx."
This only fixed Persona 3 FES issue with getting bad hashes, which involves modding the actual game. This could be affecting other games that can't be easily modded.
I think a better description would be textures without a CLUT hash are not being replaced in Persona 3 FES. I am unaware if this issue affects other games but as @ACViper said it is a possibility. The texture f331606d5d604a5b-00006640 @ACViper spoke about can be found in the Velvet Room's fuse menu. I have attached a memcard with a save file and the replacement so anyone wishing to help can reproduce the issue.
To reach the fuse menu select the Journey. Then load the 2nd save file it should say 1/31 (Su) Tartarus. From there you should be able to spot a blue door on the left of the screen, interact with it. Now navigate though the menu with these options Fuse Personas->Normal Spread->Select any 2 personas. Now you should should see the L and R prompts at the top of the screen. To view the status text go back to the Normal Spread menu and press triangle on any of the personas you should see the Status text at the top of the screen.
Solved the issue with textures generating bad hashes and not loading. If a .tmx file (original texture from p3fes) has "UsesPalette" set to "False" and "PaletteCount" set to "0," PCSX2 will generate a hash with "xxxx-xxxx," instead of "xxxx-xxxx-xxxx." So, I just modified the .tmx file and now it generated a proper new hash with "xxxx-xxxx-xxxx."
How did you modify it?
Hi, I might have the same issue in Dragon Quest 8.
I marked all textures in this room, so you can see that some textures do not load.
At first sight, it's related to textures which have a shorter file name:
Here is a save state of this room: SLES-53974 (945FBF31).01.p2s.zip
(rev 4118)
PS: Maybe it's worth mentioning that this room was flickering in purple in previous builds. So this room was already kind of special beforehand
If it's using region textures, the filename/hash will have changed, and you'll need to re-dump.
Pretty sure the original issue here doesn't occur anymore, but if it does we can reopen.
What are region textures? The texture dumps are from last night though and I used the latest build
I'm having this same issue again with Jonny Moseley Mad Trix. The textures used for the loading screen are "3df1013021285ba6-80005e42" and "5c16b729152736ff-80005e42", only two hashes, and refuse to load. These specific textures actually loading properly has been quite spotty. Some updates they won't load, then I'll install an update and they'll load sometimes, I'll reboot and they'll load all the time, the next day an update is released and they no longer loads. I'm currently on v1.7.4274 and they does not load, but did work before an update this morning.
All other texture dumps from this game have three hashes, like "74a1d520d52e95dd-bdd6134a24757e16-00005dd3", and have never ever had any issues. It's just these two that have seen massive on-and-off difficulties loading.