You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if this can be a duplicate of #15472 issue, but i will try to add more information. I hope this helps (a little at least) since I didn't see any other issues that provide any of this data for this problem in this game.
I think it is a particle bug. As I see, happens mostly with projectiles, which seams to be particles. Not all proyectiles are affected, so it can be related with the shaders of the projectiles.
This bug makes the projectile texture scale and distortion all across the screen, making some parts barely playable.
This doesn't happen in alpha v0.0.31-16319 and earlier.
Note: All my suppositions are based on my game development experience (which is relative poor)
Sorry for any spelling, writing and/or conjugation errors, spanish is my native language.
Details
Before the regression (v0.0.31-16319-0231902a), this enemy fired green glowing energetic projectiles, which are animated. And they look right.
But after the regression (v0.0.31-16323-d6f6752a), the projectile texture is stretched across all the screen, like the projectile mesh is scaled absurdly filling almost, if not, all the screen.
I try to get almost the same image on both RPCS3 versions. The place is the starting are on planet Torren IV (after completing the planet, and getting out and in again)
This happens with Zurkon projectiles too, but I chose this because the bug is absurd and is easiest to take a screenshot.
I don't know how to exactly explain the bug, but i think this enemy projectiles are a clearly example of what is happening.
Quick summary
I don't know if this can be a duplicate of #15472 issue, but i will try to add more information. I hope this helps (a little at least) since I didn't see any other issues that provide any of this data for this problem in this game.
I think it is a particle bug. As I see, happens mostly with projectiles, which seams to be particles. Not all proyectiles are affected, so it can be related with the shaders of the projectiles.
This bug makes the projectile texture scale and distortion all across the screen, making some parts barely playable.
This doesn't happen in alpha v0.0.31-16319 and earlier.
Note: All my suppositions are based on my game development experience (which is relative poor)
Sorry for any spelling, writing and/or conjugation errors, spanish is my native language.
Details
Before the regression (v0.0.31-16319-0231902a), this enemy fired green glowing energetic projectiles, which are animated. And they look right.
But after the regression (v0.0.31-16323-d6f6752a), the projectile texture is stretched across all the screen, like the projectile mesh is scaled absurdly filling almost, if not, all the screen.
I try to get almost the same image on both RPCS3 versions. The place is the starting are on planet Torren IV (after completing the planet, and getting out and in again)
This happens with Zurkon projectiles too, but I chose this because the bug is absurd and is easiest to take a screenshot.
I don't know how to exactly explain the bug, but i think this enemy projectiles are a clearly example of what is happening.
Build with regression
v0.0.31-16323-d6f6752a
Attach two log files
Log files:
v0.0.31-16319-0231902a
RPCS3.log
Ratchet Clank Future A Crack In Time [NPUA80966] - exit and save log.log.gz
v0.0.31-16323-d6f6752a (regression)
bugged RPCS3.log
bugged Ratchet Clank Future A Crack In Time [NPUA80966] - exit and save log.log.gz
Attach capture files for visual issues
RSX Capture:
v0.0.31-16319-0231902a
NPUA80966_20240508004839_capture.rrc.gz (on google drive)
v0.0.31-16323-d6f6752a (regression)
bugged NPUA80966_20240508004839_capture.rrc.gz (on google drive)
System configuration
OS: Windows 11
CPU: AMD Ryzen 5 5600
GPU: AMD Radeon RX 6600
AMD Driver version: 23.40.31.05-240417a-402338C-AMD-Software-Adrenalin-Edition
Other details
No response
The text was updated successfully, but these errors were encountered: