open [11982] My GF is a mermaid intro not loading properly #11982

Open
opened 2026-01-02 20:36:58 -03:00 by Accord · 0 comments
Owner

Branch: __refs_pull_11982_head

CartickKazama opened issue at 2023-11-08 08:22:

Is there an existing issue for this?

  • I have searched the existing issues

Affected Build(s)

yuzu1613

Description of Issue

Graphics not loading properly in opening other than that every thing is fine

Expected Behavior

Screenshot 2023-11-08 134531

Reproduction Steps

..

Log File

yuzu_log.txt

System Configuration

CPU:Ryzen 5 5600H
GPU/Driver: GTX 1650 mobile
RAM:16gb
OS:windows11

Squall-Leonhart commented at 2023-11-08 09:19:

Duplicate of https://github.com/yuzu-emu/yuzu/issues/6985 i think

G-Spawn commented at 2023-11-08 11:08:

At least generally can you please stick to docked mode and try earlier nvidia drivers to rule out if it is due to nvidia breaking drivers again? https://www.nvidia.com/download/driverResults.aspx/211638/en-us/

G-Spawn commented at 2023-11-08 11:09:

also you're using your amd integrated for vulkan not your nvidia gpu. Interesting.

Squall-Leonhart commented at 2023-11-08 11:55:

User tested both vendors
First run

[4900.616886] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:163: Driver: NVIDIA 546.1.0.0
[4900.616892] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:164: Device: NVIDIA GeForce GTX 1650
[4900.616892] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:165: Vulkan: 1.3.260
[4900.616902] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:166: Available VRAM: 3.05 GiB

second run

[5415.838174] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:163: Driver: AMD proprietary driver 2.0.279
[5415.838180] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:164: Device: AMD Radeon(TM) Graphics
[5415.838180] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:165: Vulkan: 1.3.260
[5415.838185] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:166: Available VRAM: 2.00 GiB

Also the "Expected Behavior" screenshot is not the expected behavior, artifacts should not be present in the stream

image

Squall-Leonhart commented at 2023-11-08 12:29:

This is absolutely the same bug as https://github.com/yuzu-emu/yuzu/issues/6985

image

CartickKazama commented at 2023-11-08 12:31:

For those asking why not using Nvidia gpu I tried it switching to each one and the problem is still the same

CartickKazama commented at 2023-11-08 12:36:

At least generally can you please stick to docked mode and try earlier nvidia drivers to rule out if it is due to nvidia breaking drivers again? https://www.nvidia.com/download/driverResults.aspx/211638/en-us/
I tried changing my graphics and the problem is still the same gameplay fine but only opening is facing this issue

CartickKazama commented at 2023-11-08 12:40:

User tested both vendors

First run

[4900.616886] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:163: Driver: NVIDIA 546.1.0.0
[4900.616892] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:164: Device: NVIDIA GeForce GTX 1650
[4900.616892] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:165: Vulkan: 1.3.260
[4900.616902] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:166: Available VRAM: 3.05 GiB

second run

[5415.838174] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:163: Driver: AMD proprietary driver 2.0.279
[5415.838180] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:164: Device: AMD Radeon(TM) Graphics
[5415.838180] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:165: Vulkan: 1.3.260
[5415.838185] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:166: Available VRAM: 2.00 GiB

Also the "Expected Behavior" screenshot is not the expected behavior, artifacts should not be present in the stream

image
I took the screenshot too late I thing sorry about and I think you pretty much made it simple for me

Kelebek1 commented at 2023-11-17 05:21:

This is absolutely the same bug as #6985

I don't know if it's the same bug because I don't have the other game, but this one does not try to parse 2 videos at the same time, it only has 1 instance of nvdec, and multiple videos are already supported by virtue of having 4 differen cdma pushers which contain the nvdec processor and its state.
I messed with this game a bit today but can't figure out why it's wrong.

Squall-Leonhart commented at 2023-11-17 05:46:

@kelebek1 both games share the same a bug in that the DTS order isn't respected, but the other one also has a seperate channel being set up for the decoder stream, please see https://github.com/Ryujinx/Ryujinx/pull/2671

Kelebek1 commented at 2023-11-17 06:49:

@Kelebek1 both games share the same a bug in that the DTS order isn't respected, but the other one also has a seperate channel being set up for the decoder stream, please see Ryujinx/Ryujinx#2671
I've seen that and tried the ffmpeg workaround to force return the frame, as well as implementing the Vic registers and storing the frames by offset to return them out-of-order, but neither helped.

Squall-Leonhart commented at 2023-11-18 00:09:

This may be an ffmpeg issue, a patch that may be relevant to this was landed between 5.1.3 and 5.1.4 / 6.0.0 and 6.0.1

Squall-Leonhart commented at 2023-11-18 00:45:

and multiple videos are already supported by virtue of having 4 different cdma pushers which contain the nvdec processor and its state.
it really doesn't look like the surface index is robust enough for cases involving the recombination of luma and chroma offsets, (among other things) - also i might not have worded things well, processing of video components can be done in multiple contexts as well, and the h264 decoder itself isn't doing this, which could lead to visual garbage.


[Export of Github issue for yuzu-emu/yuzu. Generated on 2024.02.28 at 10:04:32.]

**Branch:** [__refs_pull_11982_head](https://accord.dravee.dev/Accord/yuzu-mirror/src/branch/__refs_pull_11982_head) #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/147279591?u=1d6efa1c422e9d99df56c7a1ca8b84b4f57c771a&v=4" width="50"></div>[CartickKazama](https://github.com/CartickKazama) opened issue at [2023-11-08 08:22](https://github.com/yuzu-emu/yuzu/issues/11982): > ### Is there an existing issue for this? > - [X] I have searched the existing issues > ### Affected Build(s) > yuzu1613 > ### Description of Issue > Graphics not loading properly in opening other than that every thing is fine > ### Expected Behavior ![Screenshot 2023-11-08 134531](https://github.com/yuzu-emu/yuzu/assets/147279591/54414a2d-084b-4e32-8169-8eab243ea4d8) > ### Reproduction Steps > .. > ### Log File > [yuzu_log.txt](https://github.com/yuzu-emu/yuzu/files/13294136/yuzu_log.txt) > ### System Configuration > CPU:Ryzen 5 5600H > GPU/Driver: GTX 1650 mobile > RAM:16gb > OS:windows11 #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/1098176?v=4" width="50"></div>[Squall-Leonhart](https://github.com/Squall-Leonhart) commented at [2023-11-08 09:19](https://github.com/yuzu-emu/yuzu/issues/11982#issuecomment-1801391020): > Duplicate of https://github.com/yuzu-emu/yuzu/issues/6985 i think #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/23653025?u=7c6e73d3e257f4d10b2b8f9416c3db35faef85c1&v=4" width="50"></div>[G-Spawn](https://github.com/G-Spawn) commented at [2023-11-08 11:08](https://github.com/yuzu-emu/yuzu/issues/11982#issuecomment-1801668875): > At least generally can you please stick to docked mode and try earlier nvidia drivers to rule out if it is due to nvidia breaking drivers again? https://www.nvidia.com/download/driverResults.aspx/211638/en-us/ #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/23653025?u=7c6e73d3e257f4d10b2b8f9416c3db35faef85c1&v=4" width="50"></div>[G-Spawn](https://github.com/G-Spawn) commented at [2023-11-08 11:09](https://github.com/yuzu-emu/yuzu/issues/11982#issuecomment-1801670801): > also you're using your amd integrated for vulkan not your nvidia gpu. Interesting. #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/1098176?v=4" width="50"></div>[Squall-Leonhart](https://github.com/Squall-Leonhart) commented at [2023-11-08 11:55](https://github.com/yuzu-emu/yuzu/issues/11982#issuecomment-1801739964): > User tested both vendors > First run > ``` > [4900.616886] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:163: Driver: NVIDIA 546.1.0.0 > [4900.616892] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:164: Device: NVIDIA GeForce GTX 1650 > [4900.616892] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:165: Vulkan: 1.3.260 > [4900.616902] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:166: Available VRAM: 3.05 GiB > ``` > second run > ``` > [5415.838174] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:163: Driver: AMD proprietary driver 2.0.279 > [5415.838180] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:164: Device: AMD Radeon(TM) Graphics > [5415.838180] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:165: Vulkan: 1.3.260 > [5415.838185] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:166: Available VRAM: 2.00 GiB > ``` > Also the "Expected Behavior" screenshot is *not* the expected behavior, artifacts should not be present in the stream ![image](https://github.com/yuzu-emu/yuzu/assets/1098176/6b337b9f-a598-4a1f-8f1b-0352c728528d) #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/1098176?v=4" width="50"></div>[Squall-Leonhart](https://github.com/Squall-Leonhart) commented at [2023-11-08 12:29](https://github.com/yuzu-emu/yuzu/issues/11982#issuecomment-1801794811): > This is absolutely the same bug as https://github.com/yuzu-emu/yuzu/issues/6985 ![image](https://github.com/yuzu-emu/yuzu/assets/1098176/83b701f7-44bc-43d0-ac5e-285f4b317807) #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/147279591?u=1d6efa1c422e9d99df56c7a1ca8b84b4f57c771a&v=4" width="50"></div>[CartickKazama](https://github.com/CartickKazama) commented at [2023-11-08 12:31](https://github.com/yuzu-emu/yuzu/issues/11982#issuecomment-1801798938): > For those asking why not using Nvidia gpu I tried it switching to each one and the problem is still the same #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/147279591?u=1d6efa1c422e9d99df56c7a1ca8b84b4f57c771a&v=4" width="50"></div>[CartickKazama](https://github.com/CartickKazama) commented at [2023-11-08 12:36](https://github.com/yuzu-emu/yuzu/issues/11982#issuecomment-1801806052): > > At least generally can you please stick to docked mode and try earlier nvidia drivers to rule out if it is due to nvidia breaking drivers again? https://www.nvidia.com/download/driverResults.aspx/211638/en-us/ > I tried changing my graphics and the problem is still the same gameplay fine but only opening is facing this issue #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/147279591?u=1d6efa1c422e9d99df56c7a1ca8b84b4f57c771a&v=4" width="50"></div>[CartickKazama](https://github.com/CartickKazama) commented at [2023-11-08 12:40](https://github.com/yuzu-emu/yuzu/issues/11982#issuecomment-1801812083): > > User tested both vendors > > > > First run > > > > ``` > > [4900.616886] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:163: Driver: NVIDIA 546.1.0.0 > > [4900.616892] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:164: Device: NVIDIA GeForce GTX 1650 > > [4900.616892] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:165: Vulkan: 1.3.260 > > [4900.616902] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:166: Available VRAM: 3.05 GiB > > ``` > > > > second run > > > > ``` > > [5415.838174] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:163: Driver: AMD proprietary driver 2.0.279 > > [5415.838180] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:164: Device: AMD Radeon(TM) Graphics > > [5415.838180] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:165: Vulkan: 1.3.260 > > [5415.838185] Render.Vulkan <Info> video_core\renderer_vulkan\renderer_vulkan.cpp:Report:166: Available VRAM: 2.00 GiB > > ``` > > > > Also the "Expected Behavior" screenshot is _not_ the expected behavior, artifacts should not be present in the stream > > > > ![image](https://user-images.githubusercontent.com/1098176/281392577-6b337b9f-a598-4a1f-8f1b-0352c728528d.png) > I took the screenshot too late I thing sorry about and I think you pretty much made it simple for me #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/34639600?v=4" width="50"></div>[Kelebek1](https://github.com/Kelebek1) commented at [2023-11-17 05:21](https://github.com/yuzu-emu/yuzu/issues/11982#issuecomment-1815764834): > > This is absolutely the same bug as #6985 > > > I don't know if it's the same bug because I don't have the other game, but this one does not try to parse 2 videos at the same time, it only has 1 instance of nvdec, and multiple videos are already supported by virtue of having 4 differen cdma pushers which contain the nvdec processor and its state. > I messed with this game a bit today but can't figure out why it's wrong. #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/1098176?v=4" width="50"></div>[Squall-Leonhart](https://github.com/Squall-Leonhart) commented at [2023-11-17 05:46](https://github.com/yuzu-emu/yuzu/issues/11982#issuecomment-1815782958): > @kelebek1 both games share the same a bug in that the DTS order isn't respected, but the other one also has a seperate channel being set up for the decoder stream, please see https://github.com/Ryujinx/Ryujinx/pull/2671 #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/34639600?v=4" width="50"></div>[Kelebek1](https://github.com/Kelebek1) commented at [2023-11-17 06:49](https://github.com/yuzu-emu/yuzu/issues/11982#issuecomment-1815829677): > > @Kelebek1 both games share the same a bug in that the DTS order isn't respected, but the other one also has a seperate channel being set up for the decoder stream, please see [Ryujinx/Ryujinx#2671](https://github.com/Ryujinx/Ryujinx/pull/2671) > I've seen that and tried the ffmpeg workaround to force return the frame, as well as implementing the Vic registers and storing the frames by offset to return them out-of-order, but neither helped. #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/1098176?v=4" width="50"></div>[Squall-Leonhart](https://github.com/Squall-Leonhart) commented at [2023-11-18 00:09](https://github.com/yuzu-emu/yuzu/issues/11982#issuecomment-1817274225): > This may be an ffmpeg issue, a patch that may be relevant to this was landed between 5.1.3 and 5.1.4 / 6.0.0 and 6.0.1 #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/1098176?v=4" width="50"></div>[Squall-Leonhart](https://github.com/Squall-Leonhart) commented at [2023-11-18 00:45](https://github.com/yuzu-emu/yuzu/issues/11982#issuecomment-1817292617): > > and multiple videos are already supported by virtue of having 4 different cdma pushers which contain the nvdec processor and its state. > it really doesn't look like the surface index is robust enough for cases involving the recombination of luma and chroma offsets, (among other things) - also i might not have worded things well, processing of video components can be done in multiple contexts as well, and the h264 decoder itself isn't doing this, which could lead to visual garbage. > ------------------------------------------------------------------------------- > [Export of Github issue for [yuzu-emu/yuzu](https://github.com/yuzu-emu/yuzu). Generated on 2024.02.28 at 10:04:32.]
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Accord/yuzu-mirror#11982
No description provided.