LittleBigPlanet 3 [NPUA81116] - Constant freezing

[ActualMandM]

Windows 10 64-bit
GeForce GTX 1060 6GB
i5-7600k
16GB RAM

In the log, the following is constantly spammed almost every frame, possibly causing the game to momentarily freeze for a second:

·E 0:11:05.841757 {rsx::thread} RSX: Sampling of RTT region as non-2D texture! addr=0xc2f3e000, Type=3, dims=160x90
·E 0:11:05.841759 {rsx::thread} RSX: Texture resides in render target memory, but requested type is not 2D (3)

Enabling CPU Blit fixes the freezing issue.
RPCS3.log.gz

[ActualMandM]

Calmed down after Unl shenagigans, reopening.

Issue still persists in latest master. (RPCS3 v0.0.5-6693-f27f7d50c Alpha | HEAD)

RPCS3.log.gz

[ActualMandM]

Seems to have been fixed, closing.

[Zangetsu38]

no close, problem continue like lot other game

[dio-gh]

This ticket should be closed. I asked @RainbowCookie32 to retest, just to make super extra sure, but considering that even the OP said that the issue is fixed, I'm 99% sure it's long gone. Will see hopefully tomorrow.

@Zangetsu38 Just what the fuck were you thinking? This ticket has been rotting here for over a year now because of you without any kind of updates. I come here, and all I see is your shitty vague "uhhh many more games are affected too" comment without any kind of specifics. If it's a more general issue, you should have opened a separate ticket and collected the games there, as this one is currently specific to LBP3 and you couldn't have edited it. How do you think a tester can verify your claims? How do you think this "class of issue" can be found if it's stashed away in some random ticket with an unrelated name? Do I / we read your mind?

[RainbowCookie32]

As OP already said, the issue with freezing was fixed. I've been playing for a while now without any freezing. While there is RSX related log spam (RSX: Could not gather all required slices for cubemap/3d generation), it doesn't seem to affect performance or the game's visuals in any noticeable way. It's also a different error than the one on the original post.

This issue can now be closed, since the problems are fixed