Ratchet & Clank 2 [NTSC]
#1
PCSX2 1.7.0-20220206122623 https://github.com/PCSX2/pcsx2/pull/5488
Windows 10 21H2
Geforce 1070Ti - 472.12

At the start of the 2nd level one of the following will be observed after opening and closing the games Pause menu:

* Everything is correct.
* All textures experience a significant resolution decrease or Dithering completely disables (unsure which is happening). Some surfaces may also become invisible.
* All terrain/solid surfaces are invisible, foliage and stuff still appears.

To reproduce the first scenario: Configure PCSX2 to use the Software Renderer while the game is not loaded and then boot the ISO, you can switch to/from any of the Hardware Renderers while the game is running without introducing any issues so long as Internal Resolution is set to Native.

To reproduce the 2nd scenario: Repeat the above but when changing to a Hardware Renderer, set the Internal Resolution higher than Native. The issue will persist when switching back to the Software Renderer.

To reproduce the 3rd scenario: Configure PCSX2 to use any Hardware Renderer while the game is not loaded and then boot the ISO.


Attached Files
.zip   Mcd001.zip (Size: 268,48 KB / Downloads: 154)
.zip   Mcd002.zip (Size: 10,07 KB / Downloads: 140)
.zip   inis.zip (Size: 7,71 KB / Downloads: 148)
Computer specifications:
Windows 10 | Ryzen 3700X | ASUS Crosshair VIII Hero (WiFi) | MSI 1070Ti | 16GB 3600MHz RAM
Reply

Sponsored links

#2
(02-16-2022, 01:55 PM)Franpa Wrote: PCSX2 1.7.0-20220206122623 https://github.com/PCSX2/pcsx2/pull/5488
Windows 10 21H2
Geforce 1070Ti - 472.12

* Everything is correct.
* All textures experience a significant resolution decrease or Dithering completely disables (unsure which is happening). Some surfaces may also become invisible.
* All terrain/solid surfaces are invisible, foliage and stuff still appears.

Most of what you are describing sounds like mipmapping, which R&C requires to function properly. Textures far away from the camera will render at a lower resolution to save bandwidth on the console.

Can you post pictures of what you are seeing after this "bug" occurs?
Reply
#3
Scenario 1 & 2 can be demonstrated in the same game session, Scenario 3 needs the game to be Shutdown (or starting with PCSX2 closed).

Reminder that:

Scenario 1 involves starting the game with the Software Renderer. Once the game is running you can change to any Hardware Renderer so long as Internal Resolution remains set to Native. The only incorrect thing you'll encounter after the change to Hardware Rendering (that I've noticed so far) is the Pause Menu background being broken.

Scenario 2 is starting the game with the Software renderer. Once the game is running change to a Hardware Renderer and increase the Internal Resolution. exiting the games Pause Menu will result in poor rendering quality of all surfaces (very speckly, low resolution texturing and some surfaces disappearing at certain camera angles)

Scenario 3 is simply starting the game with either Direct3D 11, OpenGL or Vulkan Hardware Renderer chosen. Internal Resolution is irrelevant. The video speaks for it self.

*Scenario 1 & 2 (1:05 for 2): https://www.youtube.com/watch?v=ErA3dXCdSNg
*Scenario 3: https://www.youtube.com/watch?v=yiFU2RFUr_M
Computer specifications:
Windows 10 | Ryzen 3700X | ASUS Crosshair VIII Hero (WiFi) | MSI 1070Ti | 16GB 3600MHz RAM
Reply




Users browsing this thread: 1 Guest(s)