Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retrieving texture data is not resulting in correct image data #30

Open
justinstenning opened this issue Aug 15, 2015 · 3 comments
Open
Labels

Comments

@justinstenning
Copy link
Owner

Original image:
image

As Jpeg/Bitmap results in correct image however:

Retrieving raw pixel data:
image

As PNG:
image

@ghost
Copy link

ghost commented Oct 5, 2015

This bug still remains. I though might have been fixed by earlier commits but no. Still PixelData and PNG shots not giving correct image data. Also got a error message from the BasicHLSL11.exe file after these types of screenshots. The error says : The Direct3D device has a non-zero reference count, meaning some objects were not released.

@justinstenning
Copy link
Owner Author

No Farukh, this still remains a problem, which is why the issue is still open.

You can ignore the non-zero reference count message.

@ghost
Copy link

ghost commented Oct 8, 2015

I have tested 5 Games with it and posting their png and pixeldata result here.

1st Game : Call Of Duty 4 Modern Warfare = All the formats works fine. No Problem at all. DirectX9 Game.

2nd Game : Counter Strike Source = png and pixeldata have problem. DirectX9 Game The screenshots of the two different types are below:

PNG Format:
pngdata

PixelData:
pixel-data

3rd Game : FIFA 11 = png problem. Is not providing correct image data. Pixeldata is not getting any image data. Whole screenshot is blank. DirectX9 Game.

4th Game : Need For Speed Most Wanted = DirectX9 Game. Both png and Pixeldata problem here.

5th Game : Watch Dogs = DirectX11 Game. PNG problem not providing correct image data. Pixeldata format is not proving any image at all. Blank.

Hope this information will help you to solve this bug. Please feel free to ask me if any test you need to run regarding this bug.

Hope you will solve it soon.
Thanks in advance...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant