Texture with two 8-bit channels (like L8A8) - what fits this case better is treating texture as a 32-bit 8888 texture with half the width. Since to properly decode a pixel we need information from its neighbour (later called “left” and “right” pixels), it’s unfeasible to treat this data as a 16-bit Data is laid out as presented:Įvery pixel has its own Y (luminance) value, with U and V values shared between two neighbouring pixels. With YUY2, each 32-bit value defines a pair of pixels. YUY2 is a 16-bit 4:2:2 format, which is a variation of YUV color format typically used to encode videos. let’s see at what data really is provided by in-game VP6 decoder. at a later point - to understand what’s going on with 1. Weird darker stripe - linear filtering failure… very non-obvious at first.

Duplicated image - caused by interpreting 16-bit wide pixel data as 32-bit.Greenish appearance - that’s what typically happens when you display YUV data as RGB - so we can see that in-game decoder indeed provides us with non-RGB data.Let’s identify and isolate issues we can see here: The very first time movies are displayed on Windows 10 in game (note this is 640x240, for the time being displayed in the corner and not stretched at all). However, it is possible to write a shader which outputs RGB data when given a non-RGB texture -Īnd this is exactly what we are going to do here.įirst, replacing static blue fill with data provided by VP6 decoder (without specifying a shader or anything fancy) gives us a first view on the movies. Since we are now using D3D9, it is not possible to directly display a non-RGB image. Polished further to display movie data instead of a static image! In other words, this simple example basically proves the idea works out and can be It’s drawn using newly written wrapper, which means we can use it to draw anything we want to. While it doesn’t seem like it, this blue rectangle is in fact a breakthrough. This is a screenshot from the very first attempt of testing a RwD3D9 wrapper which gave visible results. Now, with most of the code in place, we can check if anything shows up… As it was listed, there were a few possible approaches to fixing the issue,īut finally only one of them ended up being viable. In Part 1, we have researched the crash and figured out the exact cause of it.

If you haven’t read Part 1 yet, I strongly encourage to go back and read it first before proceeding with this post. Fixing game-breaking issues in The Godfather: The Game - Part 2

Godfather pc game windows 10