Metroid: Other M's cutscenes are completely blacked out.

[DaThWiiDSGuy]

I'm playing through the beginning of the game right now and for some reason, the very beginning cutscenes render fine, but once I get onto the main area of the game, the cutscenes start having this giant black box covering up the whole thing, and I know it's a black box because for some reason, I can see a pixel of the game around the right side and the bottom.

I've gone and looked around for this issue, and all I could find was this: https://bugs.dolphin-emu.org/issues/3477

It says the issue is resolved, but I'm on one of the latest dolphin 5.0 builds, specifically 5.0-5791 x64, and this issue persists, how do I fix this?

[DaThWiiDSGuy]

As a side note, I'm also _completely_ new here, so I'm not quite sure if this is the correct section to put this in, or if I'm supposed to put this in the "Development Discussion" section

If this is posted in the wrong place, I'll happily move it over there.

[Fog]

Hardware specs would be nice to know, as well as what video backend you're using and graphics settings.

[DaThWiiDSGuy]

(11-09-2017, 03:34 AM)Fog Wrote: Hardware specs would be nice to know, as well as what video backend you're using.

GTX 1070 8gb, I7 4790k, 16gbs ddr3 ram

I'm using the Direct3D 11 backend as well.

Here's my graphics settings: https://gyazo.com/c3d720ebf77293569042908cd982829e
The resolution was set to native because I wanted to see if the issue persisted on a lower res, however, I know this happens when I set it up to the setting they recommend for 1440p

Edit: issue still persists on lower resolution

[Fog]

(11-09-2017, 03:35 AM)DaThWiiDSGuy Wrote: GTX 1070 8gb, I7 4790k, 16gbs ddr3 ram

I'm using the Direct3D 11 backend as well.

Here's my graphics settings: https://gyazo.com/c3d720ebf77293569042908cd982829e
The resolution was set to native because I wanted to see if the issue persisted on a lower res, however, I know this happens when I set it up to the setting they recommend for 1440p

Does this issue also occur with OpenGL or Vulkan?

[DaThWiiDSGuy]

(11-09-2017, 03:39 AM)Fog Wrote: Does this issue also occur with OpenGL or Vulkan?

I'll try those as well, one moment.

[DaThWiiDSGuy]

(11-09-2017, 03:39 AM)Fog Wrote: Does this issue also occur with OpenGL or Vulkan?

Alright, I went and tried OpenGL and the issue seems to be fixed.

Thanks , I really appreciate it!

Edit: So... how do I mark this thread and solved? If that's even a thing o.O

[Fog]

(11-09-2017, 03:44 AM)DaThWiiDSGuy Wrote: Alright, I went and tried OpenGL and the issue seems to be fixed.

Thanks , I really appreciate it!

Edit: So... how do I mark this thread and solved? If that's even a thing o.O

Don't need to worry about that.

However, we'll be looking into the issue for D3D.

[KHg8m3r]

You're on Windows 7 yes? Does this issue happen in D3D in builds before 5.0-5404? Cause this sounds like the LogicOps issue with D3D in Windows 7