Emulator Issues #12548
closedHeart visible in front of Flipside shop when using Stereoscopic 3D on Vulkan
0%
Description
Game Name?
Super Paper Mario (rev 0)
Game ID?
R8PE01
MD5 Hash?
fe441d77d5cb9a7f01de954e84e6ca49
What's the problem? Describe what went wrong.
A green heart appears in front of Howzit's shop on Flipside 2F when using Stereoscopic 3D on the Vulkan backend. The heart appears regardless of which stereo mode is used (passive is the one that interferes least with normal seeing, though). It goes away after flipping into 3D and then back into 2D, though it will appear again upon reloading the area. The heart actually comes from the Flipside 2nd Floor Outskirts heart pillar (the one that unlocks chapter 4).
The same issue also applies to Notso's shop on Flopside 2F.
What steps will reproduce the problem?
- Play the game until chapter 4 is unlocked (or use a 100% completed save file).
- Switch to the Vulkan backend and enable Stereoscopic 3D.
- Travel to Flipside 2F.
- Walk to the shop (on the left side) and observe that the heart is visible.
Is the issue present in the latest development version?
Yes, tested 5.0-14344 and 5.0-14402.
Is the issue present in the latest stable version?
No. 5.0 does not have the Vulkan backend. I also confirmed that the other backends available in 5.0 (OGL, D3D11, and D3D12) are not affected.
If the issue isn't present in the latest stable version, which is the first broken version?
Confirmed present in 5.0-750, the earliest version that has Vulkan that I can test (5.0-748 added it but doesn't exist for Windows).
What are your PC specifications? (CPU, GPU, Operating System, more)
- CPU: Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz, 2592 Mhz, 6 Core(s), 12 Logical Processor(s)
- GPU: NVIDIA GeForce GTX 1650 Ti
- OS: Windows 10 Home 10.0.19042.746
Is there anything else that can help developers narrow down the issue?
The attached fifologs were both recorded with OpenGL and with Stereoscopic 3D disabled; however, they exhibit the issue when playing them back with Vulkan and Stereoscopic 3D enabled. This tells me that it's not some kind of bounding box issue with Stereoscopic 3D. The first fifolog was recorded right on entering the area, while the second was recorded after flipping into 3D and back into 2D. Judging from the object counts, the flip into 3D resulted in the game culling objects that weren't on screen, and then it left them culled afterwards, but I haven't investigated fully.
Files