On Thu May 15 04:56:25 2025 +0000, Elizabeth Figura wrote:
Yes, unless there's evidence that native mfplat decoders are returning larger samples than the size they return in GetOutputSizeInfo(), this seems like the wrong way to solve things.
The code was changed a while ago to call `MFCalculateImageSize()` instead of `GetOutputSizeInfo()` to fix several games, but I found no info on the exact issue. If `GetOutputSizeInfo()` never returns an exceedingly large size, we could just take the max of the two.