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

Severe graphic errors in Unreal Tournament on Mali400 and Adreno 205 #164

Closed
Elwood89 opened this Issue Jan 27, 2014 · 48 comments

Comments

Projects
None yet
9 participants
@Elwood89
Contributor

Elwood89 commented Jan 27, 2014

I have a S3 international (Exynos/ Mali400) and a Sony Xperia Play (Qualcomm Snapdragon, Adreno 205). Both on Android 4.1.2.

Both display flickering black triangles in this game. I was going to make a video, but someone beat me to it ;)
http://www.youtube.com/watch?feature=player_detailpage&v=yAo2l91Dl0s#t=123

Here we can se someone playing it on a S4(probably a PowerVR SGX 544MP GPU) with only minor flickering:
http://www.youtube.com/watch?feature=player_detailpage&v=j_AOT3_D3dY#t=101

it is also listed as playable on the Pandora Compatibility list, with only a "Sometimes single textures are flickering a bit" issue, so probably the big problem is not there as well.

I'm using a Reicast test build from 25.01.2014. (obbf33c from the Lounge Katt buildbot).


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@AbandonedCart

This comment has been minimized.

Contributor

AbandonedCart commented Jan 27, 2014

#103
#108
Merging these issues together, since they seem to be the same situation

@sergioroprado

This comment has been minimized.

sergioroprado commented Jan 27, 2014

On my note 3 (adreno 330) sonic adventure 2 is running almost perfect, with only very very minor graphical glitches.

@AbandonedCart

This comment has been minimized.

Contributor

AbandonedCart commented Jan 27, 2014

That one shouldn't have been an issue. This seems to be more the 2XX series now.

@hooby3dfx

This comment has been minimized.

Contributor

hooby3dfx commented Jan 27, 2014

There are other games with the same (or similar looking) gfx issue with flickering black triangles:
Dynamite Cop (heavy flickering)
Sega Bass Fishing (heavy flickering)

@AbandonedCart

This comment has been minimized.

Contributor

AbandonedCart commented Jan 27, 2014

I'm not sure, but what about a build against GLES3, since it seems to be all 4.X.X devices with rendering issues?

@hooby3dfx

This comment has been minimized.

Contributor

hooby3dfx commented Jan 27, 2014

adreno drivers have major issues with es3 (see
https://forums.dolphin-emu.org/Thread-opengl-es-3-guide).
worth a shot though.

On Mon, Jan 27, 2014 at 2:41 PM, TwistedUmbrella
notifications@github.comwrote:

I'm not sure, but what about a build against GLES3, since it seems to be
all 4.X.X devices with rendering issues?


Reply to this email directly or view it on GitHubhttps://github.com//issues/164#issuecomment-33412481
.

@AbandonedCart

This comment has been minimized.

Contributor

AbandonedCart commented Jan 27, 2014

Well I started a compost heap https://github.com/LoungeKatt/reicast-emulator/tree/gl3kk that may eventually turn into GLES3

@Elwood89

This comment has been minimized.

Contributor

Elwood89 commented Jan 27, 2014

Gentlemen... you are not planning to make this a GLES3-only emu, are you? Are these issues too much to handle for GLES2? Not that I know anything about it, apart from the fact that I have no GLES3 devices, therefore I forbid such action! ;)

@AbandonedCart

This comment has been minimized.

Contributor

AbandonedCart commented Jan 27, 2014

Relax. GLES3 is API 18+. That's application suicide as a sole release. It's like Antutu or any of the Tegra apps where you design it as a separate version. I can't really see skmp switching to a version I don't think his hardware would run either way. It's just research.

@skmp

This comment has been minimized.

Member

skmp commented Jan 27, 2014

Software rendering is much more likely to be a viable solution that ES3 for
quite some time ...

On Mon, Jan 27, 2014 at 11:11 PM, TwistedUmbrella
notifications@github.comwrote:

Relax. GLES3 is API 18+. That's application suicide as a sole release.
It's like Antutu or any of the Tegra apps where you design it as a separate
version. I can't really see skmp switching to a version I don't think his
hardware would run either way. It's just research.


Reply to this email directly or view it on GitHubhttps://github.com//issues/164#issuecomment-33423257
.

~skmp

@AbandonedCart

This comment has been minimized.

Contributor

AbandonedCart commented Jan 27, 2014

Yeah. It's amazing that 2 years after the big mess getting the Adreno 205 to even run with ICS, it hasn't improved at all. Now it just breaks quietly.

@AbandonedCart

This comment has been minimized.

Contributor

AbandonedCart commented Jan 29, 2014

hrydgard/ppsspp#5135

Seems related to the problems we are having. Not directly, but it seems the n5 is one of the ones with graphical "hiccups" so I was thinking it could be a result of refresh rate.

@AbandonedCart

This comment has been minimized.

Contributor

AbandonedCart commented Feb 2, 2014

Try the newest build. For Jet Set Radio, it seems to be completely resolved.
Current:
screenshot_2014-02-02-15-10-46
screenshot_2014-02-02-15-10-57
Before:
screenshot_2014-01-21-01-29-05

@AbandonedCart

This comment has been minimized.

Contributor

AbandonedCart commented Feb 2, 2014

Closing this unless there are new reports. It's flawless on every device tested that previously had the issue.

@hooby3dfx

This comment has been minimized.

Contributor

hooby3dfx commented Feb 3, 2014

unreal still has massive black flickering areas.
sega bass fishing still has extreme triangle flickering, though it does
look a little better now i think.
dynamite cop also has nasty flickering (also might have gotten a little
better).
i think virtua tennis also got better (now has very minor flickering in
players).

all on shield^

On Sun, Feb 2, 2014 at 4:22 PM, TwistedUmbrella notifications@github.comwrote:

Closing this unless there are new reports. It's flawless on every device
tested that previously had the issue.

Reply to this email directly or view it on GitHubhttps://github.com//issues/164#issuecomment-33913172
.

@skmp

This comment has been minimized.

Member

skmp commented Feb 3, 2014

try the zhack branch

On Mon, Feb 3, 2014 at 7:21 AM, hooby3dfx notifications@github.com wrote:

unreal still has massive black flickering areas.
sega bass fishing still has extreme triangle flickering, though it does
look a little better now i think.
dynamite cop also has nasty flickering (also might have gotten a little
better).
i think virtua tennis also got better (now has very minor flickering in
players).

all on shield^

On Sun, Feb 2, 2014 at 4:22 PM, TwistedUmbrella <notifications@github.com

wrote:

Closing this unless there are new reports. It's flawless on every device
tested that previously had the issue.

Reply to this email directly or view it on GitHub<
#164 (comment)

.


Reply to this email directly or view it on GitHubhttps://github.com//issues/164#issuecomment-33925511
.

~skmp

@hooby3dfx

This comment has been minimized.

Contributor

hooby3dfx commented Feb 4, 2014

ok, zhack branch has the greatest improvement of everything.
unreal - way better (still a little glitchy but playable)
dynamite cop - way better (still a little glitchy on first stage but
playable, got better in next levels). screenshot attached.
sega bass - still wicked glitchy, maybe this is a different issue.
screenshot attached.
virtua tennis - actually worse in this branch. screenshot attached. other
player was invisible.

what do you think the plan will be for integrating a fix? i take it that
you want to avoid game specific hacks.

screenshot_2014-02-03-22-39-26
screenshot_2014-02-03-22-38-15
screenshot_2014-02-03-22-33-44

edit: not sure why images arent showing up. oh well, links are there.

@hooby3dfx hooby3dfx reopened this Feb 4, 2014

@AbandonedCart

This comment has been minimized.

Contributor

AbandonedCart commented Feb 4, 2014

Your gitfu is weak.

They got no legs! It's like pacman tennis...

@AbandonedCart

This comment has been minimized.

Contributor

AbandonedCart commented Feb 4, 2014

I am terrible with C, but this is what I'm thinking is a good way to handle it:
https://github.com/LoungeKatt/reicast-emulator/commit/c58b18bd3355156edfe8e5bcdb543aa7c19ad573

@skmp

This comment has been minimized.

Member

skmp commented Feb 4, 2014

Z computation is a quite hot path, this will chop off perfomance. Ill merge
to master the modvols edits that arent much of a hack, since we dont render
modvols anyway. The rest needs to go.

@AbandonedCart

This comment has been minimized.

Contributor

AbandonedCart commented Feb 4, 2014

All i know is the original zhack commit made all my games 8 bit nightmares lol

@skmp

This comment has been minimized.

Member

skmp commented Mar 24, 2014

Is this still an issue? It should be fixed in r6

@hooby3dfx

This comment has been minimized.

Contributor

hooby3dfx commented Mar 24, 2014

the zhack branch has improvements in some games (UT, Dynamite Cop) but master still has heavy artifacts. havent testing in awhile though, ill check out latest.

@skmp

This comment has been minimized.

Member

skmp commented Apr 25, 2014

This is a quite delicate matter, so moved for r8

@skmp skmp added this to the r8 milestone Apr 25, 2014

@skmp

This comment has been minimized.

Member

skmp commented Jun 27, 2015

As far as I recall, zhack was (partially) merged to master a long time ago.

@AbandonedCart

This comment has been minimized.

Contributor

AbandonedCart commented Jun 28, 2015

a portion of zhack was merged a while back to resolve issues with Sonic Adventure or Shenmue, but there was some trade-off that prevented a complete merge. It was something like it fixed some games but caused black blobs in other games. The parts that had the most benefit with the least regression were merged. Building the branch could more or less completely fix some games, though, if the games it broke were not an issue for the specific user.

@MrPowerGamerBR

This comment has been minimized.

MrPowerGamerBR commented Sep 24, 2015

This issue stills persists on the lastest Play Store release and in the lastest Dev Build.

Also, I can't find the zhack branch anywhere, I tried searching on the Dev Builds page, nothing; tried searching on the GitHub branches, also nothing.

@petervirtual

This comment has been minimized.

petervirtual commented Jun 11, 2017

How can I get my hands on a compiled version of the zhack branch for my device? I'd really like to try this fix.

@AbandonedCart

This comment has been minimized.

Contributor

AbandonedCart commented Jun 11, 2017

The branch no longer exists. Parts have been merged, but it would have been outdated (and likely crash) as a separate branch now.

@petervirtual

This comment has been minimized.

petervirtual commented Jun 11, 2017

do you think there is a repository somewhere that would have the apk from 2014 when it was current?

@AbandonedCart

This comment has been minimized.

Contributor

AbandonedCart commented Jun 11, 2017

Doubtful, but again it will likely crash because it had no support for current Android.

@petervirtual

This comment has been minimized.

petervirtual commented Jun 11, 2017

my device is android 4.x (cheap gaming handheld) so I'd really like to hunt out a build from that vintage. I've been trying the older builds on the reicast (ci builds) website, which are stable but al have the severe graphics glitches

@petervirtual

This comment has been minimized.

petervirtual commented Jun 11, 2017

BTW ... thanks for being so repsonsive

@skmp

This comment has been minimized.

Member

skmp commented Jun 12, 2017

@petervirtual

This comment has been minimized.

petervirtual commented Jun 12, 2017

I might being doing something wrong so I'll explain what I have done so far. I have been attempting to use reicast on a raspberry pi (which I have set aside for now), an android gaming handheld (android 4.4) and a moto g (3rd gen Android 6.0). The two android devices have identical symptoms however, they are dissimilar hardware and OS

I have attempted to use the play store current verion of reicast and many of the builds from http://builds.reicast.com. When I use the public app or build older than approximately 3/2015 then I get the flashing textures. When I use the newer builds from reicast.com then I get green polygons flashing in place of textures. (See the two behaviors below). Interestingly, when using the raspberry pi and installing using the native installer included, I get the green behavior also.

screenshot_20170612-151232
screenshot_20170612-151245
screenshot_20170612-160858

Your advice is greatly appreciated.

@petervirtual

This comment has been minimized.

petervirtual commented Jun 13, 2017

@petervirtual

This comment has been minimized.

petervirtual commented Jun 17, 2017

Anyone have any ideas on this one?

@conkerbad4day

This comment has been minimized.

conkerbad4day commented Jun 20, 2018

Would love to see a fix for this been using samsung s8 snapdragon i can do some test for you guy i would really love to revive this to be fixen thanks you!

@petervirtual

This comment has been minimized.

petervirtual commented Jun 22, 2018

Me too. I would happily test it also. All the the master builds have the symptoms I have described previously and I would really appreciate a fix for this too. Not sure I have the skills to contribute in any other meaningful way, but I would be willing to help out in any way I can.

@conkerbad4day

This comment has been minimized.

conkerbad4day commented Jun 23, 2018

Well testing is another thing first it would be nice to see support from the team and try to fix unreal tournament.... that the only game i want and that the only one that broken please dev we need a fix thank!

@AbandonedCart

This comment has been minimized.

Contributor

AbandonedCart commented Jun 23, 2018

(Off topic conversation removed. Those involved may refer to their email notifications)

@reicast reicast deleted a comment from conkerbad4day Jun 23, 2018

@reicast reicast deleted a comment from conkerbad4day Jun 23, 2018

@reicast reicast deleted a comment from conkerbad4day Jun 23, 2018

@conkerbad4day

This comment has been minimized.

conkerbad4day commented Jun 23, 2018

Did i ever said they where similar?!? No... what im saying is that it seems rather long for a team of 12 guy to fix a little problem that was not here at first ofc it can happen but 4 years in my book is rather long all problem dolphin try to fix them in 1 years or less that seem like a reasonable wait but 4 years that so long iv seen the ticket and iv seen that unreal tournament is not the only problem rrciast have .... Ofc doing little update to show that the thing is alive help but when the works doesnt change anything exeptional it make me wonder if the team is really that interested in finishing this project. Dont be mad after me all i am doing is poi ting out the slowness of the team that will lead to its death( i hope not tbh i love it) but iv seen so many emu showing love at first then slowly dying off.

@AbandonedCart

This comment has been minimized.

Contributor

AbandonedCart commented Jun 23, 2018

You keep referencing Dolphin, so you are implying that it is somehow similar.
Unreal Tournament is FAR from the only problem.
You keep referencing 4 years based on this issue alone.
That is 12 people total. That does not account for how recently some have joined or those that only work on a specific frontend exclusively. That number was only relevant in saying that compared to other projects, the team is significantly smaller overall.

The team is interested in "finishing" the project, which is why so much effort has been placed into rallying contribution. You are more than welcome to dwell on your feelings about the past 4 years, but that will do absolutely nothing about resolving the issue today. This is a non-profit open-source project, meaning there are no deadlines for support other than those we set for ourselves because we are contributing our free time, not just code. While leaving an issue sitting for a long time is not ideal, sometimes we do not have a choice in that. Quitting a full-time job because you want to play Unreal Tournament and it needs work would not be realistic.

I appreciate your feedback, but today is a new day. It is time to move on. If you think the project will die because of events that have long since passed, then you have already been proven wrong. Sorry.

@conkerbad4day

This comment has been minimized.

conkerbad4day commented Jun 23, 2018

Im just assuming too fast maybe hahaha dont worry im not that interested in playing the game my son is well no worrys dude ur team can take wathever time you want i was just pointing out 4 years yes is long so pleaae dont worry about my statment comparing dolphin it was a stupid thing for me to do ....

Now what could it take to be a tester i got no pc at my hand and i wish to test evergame( i got a collection ) so far almost 50% of what i shoot at it will run well so that a good thing no? For the rest many many game not working and i think reicast will take long before reaching a viable option for an android emulators so we need more guy like you that talk back to people like me otherwise it would be really dead.

@petervirtual

This comment has been minimized.

petervirtual commented Jun 23, 2018

I’m certainly impressed by all the hard work that goes into a project like this. Honestly, I wish I had the skills it takes to troubleshoot a bug like this one.

I would be greatful if the issue I have experienced and described previously in this thread could be fixed.

Any suggestions on how I could encourage the skillful and smart developers on this project to take a closer look would be greatly appreciated.

Thank you in advance.

@skmp

This comment has been minimized.

Member

skmp commented Jul 13, 2018

@skmp skmp closed this Jul 13, 2018

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