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

Tales of Destiny 2 Black Screen On Android #6232

Closed
mckimiaklopa opened this issue Jun 5, 2014 · 6 comments
Closed

Tales of Destiny 2 Black Screen On Android #6232

mckimiaklopa opened this issue Jun 5, 2014 · 6 comments

Comments

@mckimiaklopa
Copy link

Except on Battles,on the title screen and on FMVs,this game just displays a black screen sometimes overlayed with some objects(on dialogues,it is just a black screen with text)
screenshot_2014-06-05-14-28-51
screenshot_2014-06-05-14-29-17

I tried builds 0.9.8-48 and 0.9.8-1028 with all the possible settings I can think of and it does not change anything about the issue

My specs
http://www.gsmarena.com/samsung_galaxy_s_duos_2_s7582-5876.php

@mckimiaklopa
Copy link
Author

This only happens to broadcom videocore gpus

@unknownbrackets
Copy link
Collaborator

Those controls are huge.

Well, it does a block transfer to show the background behind the menu. Also, when drawing parts of the menu it uses color doubling. Maybe somehow the shader color doubling is turning it into black?

I wonder if we need to clamp or something.

-[Unknown]

@hrydgard
Copy link
Owner

I can't imagine color doubling would anything into black (unless there's a color test for non-equality with white active, but that would just be crazy). Shader math doesn't wrap unless you explicitly use integers.

If this only happens on Broadcom it's not unlikely to be some driver bug.

@unknownbrackets
Copy link
Collaborator

Has this changed at all? I wonder if it was related at all to the PowerVR issue that had to do with using GL_CONSTANT_COLOR when not necessary.

-[Unknown]

@unknownbrackets
Copy link
Collaborator

Does this still happen in the latest version? There was a problem related to viewport and render resolution that might've caused this on certain devices (and maybe on Broadcom even at 1x.)

-[Unknown]

@unknownbrackets
Copy link
Collaborator

Let's hope it has improved. If it hasn't, we'll have to wait for more information to do anything about it.

Closing for now due to lack of updates / information.

-[Unknown]

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

No branches or pull requests

3 participants