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
Graphics appear glitched in the Disney Infinity games
Details
In the Disney Infinity games (Disney Infinity, Disney Infinity 2.0 and Disney Infinity 3.0) the graphics will appear with blocky artifacts all over both during gameplay and during cutscenes (but not in menus/loading screens). The games seem to require WCB+RCB+WDB+RDB to avoid appearing overly bright, but even with these settings on, the block effect still appears.
As well as enabling WCB+RCB+WDB+RDB, the game also seemed to run more stable with FIFO Accuracy set to Atomic, so this was enabled in the above example. Tested with Strict Rendering Mode enabled also which made no difference, and the same issue was present using OpenGL instead of Vulkan.
The text was updated successfully, but these errors were encountered:
Quick summary
Graphics appear glitched in the Disney Infinity games
Details
In the Disney Infinity games (Disney Infinity, Disney Infinity 2.0 and Disney Infinity 3.0) the graphics will appear with blocky artifacts all over both during gameplay and during cutscenes (but not in menus/loading screens). The games seem to require WCB+RCB+WDB+RDB to avoid appearing overly bright, but even with these settings on, the block effect still appears.
RPCS3 Example from Infinity 2.0:

Console Example:

Attach a log file
Log File: DisneyInfinity2.log.gz
Attach capture files for visual issues
RSX Capture: https://mega.nz/file/bNcwjSya#0Rl0T1JjGNzwJYkIZLAwrSxTcXp8LpUqo_zMVuYUMOw
Renderdoc Capture: https://mega.nz/file/GF9HhJwB#y0mcZz49aUfMVS_44p9Svo720OUlLgkZoNEu3gWEVqA
System configuration
Intel Xeon CPU E3-1240 v5 @ 3.50GHz | 16 GiB RAM | Operating system: Windows, Major: 10, Minor: 0, Build: 19045 | NVIDIA GeForce GTX 1060 6GB running on driver 537.13.0.0
Other details
As well as enabling WCB+RCB+WDB+RDB, the game also seemed to run more stable with FIFO Accuracy set to Atomic, so this was enabled in the above example. Tested with Strict Rendering Mode enabled also which made no difference, and the same issue was present using OpenGL instead of Vulkan.
The text was updated successfully, but these errors were encountered: