Note 3 - android 4.4 ( snapdrago 800 ) - Shenume - Notebook broken

[skmp]

From @mirek190 on March 4, 2014 20:54

edit by @skmp Depth precision issues are causing this problem. It might be possible to work around them, but there's no easy for fix now

---

Look at it

http://i62.tinypic.com/f550uf.png

Notebook is broken I can not read it instructions, numbers, etc. The game is unplayable now.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/60867800-note-3-android-4-4-snapdrago-800-shenume-notebook-broken?utm_campaign=plugin&utm_content=tracker%2F91046168&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F91046168&utm_medium=issues&utm_source=github).

[skmp]

From @stodag on March 4, 2014 21:40

yeah, a must have needed for this game otherwise your walkin round in circles.. unfortunately graphic bugs can be hard to fix.. if they do so, chances are it'll break other games.

[skmp]

From @LoungeKatt on March 4, 2014 21:45

Note 3 + Shenmue == Broked. It's like 4 issues.

[skmp]

From @mirek190 on March 4, 2014 22:52

No . On mod kernel or debug mode for the first seconds of game and everything is fine ;-)

[skmp]

From @MrPsyMan on March 4, 2014 22:57

We could calibrate our depth handler again in order to fix the notebook. But as said, other stuff will certainly break.

[skmp]

From @mirek190 on March 4, 2014 23:42

As we know weren't many games on DC ( good games even less 15 - 20 ? ) and will be any problem add options in the emulator like - path for game 1, path for game 2 etc ?

Then would sole problems if any modifications will break other games. I think it even would work automatically but I can choose manually...

[skmp]

From @LoungeKatt on March 4, 2014 23:52

That's a pretty big mess for one device, though...

[skmp]

From @MrPsyMan on March 5, 2014 4:29

For starters, I can count at least 30 good games on the system.

Additionally, "fixing" some of the depth issues will result in other issues on the same game. We can't "fix" all the depth issues on a single game at the same time. That's a hardware limitation on the GPU.

The only applicable "fix" is either a software renderer (that will be too slow unless you have something like a quad-core at 2ghz) or a GPU with better depth handling capabilities.

For the record, the Dreamcast GPU has a depth range of around 4 billions. Most mobile GPUs have that reduced to about 16 millions, with some going even as low as 65 thousands (tegra 3). In order to fit all the objects in such a smaller range we do all sorts of special handling. The end result however is rarely pretty.

Now, we could do even more special handling but unfortunately mobile GPUs are slow and it would kill speed.

...and that's pretty much it.

[skmp]

From @neko68k on March 5, 2014 5:41

the note 3 with snapdragon is a quad core 2.3ghz, so yeah ;D

[skmp]

From @Elwood89 on March 5, 2014 9:57

Is the Dreamcast GPU depth accuracy (4 billions? wow) an exception when it comes to console GPU's of that generation? Just curious...

[skmp]

Yeah, CLX had 32 bit floating point Z range. And games love to abuse it.

[skmp]

From @mirek190 on March 5, 2014 14:58

In that case should be at least an option in settings like

• default depth
• better accurate depth
• best accurate depth

I think it would be helpful for everyone.

It is possible to make it ?

[skmp]

From @LoungeKatt on March 5, 2014 15:21

Unless you're on something earlier than the r6 market version, it's already under render depth in settings.

[skmp]

From @mirek190 on March 5, 2014 15:41

I didn't know about it. I thought it is connected with color depth - you know 16 bit, 24 or 32 bit color depth ....

Anyway I was changing to 16 , 24 and 32 I don't see any difference. Notebook is still broken in the same way.

[skmp]

From @LoungeKatt on March 5, 2014 17:10

Probably isn't related. I added most of that before I even knew what it was honestly.

[skmp]

From @MrPsyMan on March 5, 2014 23:31

It doesn't make a difference because the hardware can't do the 32bit one. It's a hardware limitation.

[skmp]

From @nex86 on July 14, 2014 18:31

I'm on r6 on Tegra 4 (Nvidia Shield) and like to play this game but it's unplayable right now because of the unreadable notebook. Isn't there a way to fix this? Also, I tried force software rendering but it doesn't change anything.

[skmp]

From @LoungeKatt on July 14, 2014 19:50

On a shield, you won't see a real difference between software and hardware rendering. That is for low end devices where the hardware will slow down the emulator.

[skmp]

From @nex86 on July 14, 2014 20:27

okay, but won't software rendering fix the depth glitches? for me it doesn't so I assume it runs with hardware OpenGL ES regardless if force software rendering is on or not. With software rendering you won't have the GPU limitations so most graphical glitched caused by them can be fixed.

[skmp]

From @LoungeKatt on July 14, 2014 21:54

Not how it works. Software rendering applies to the Android EGL view but not the native emulator output. The issue you have is with the native emulator.

[skmp]

From @nex86 on July 14, 2014 22:10

So there is no way to fix it? I know NullDC has a few depth glitches as well but they're not as bad as in Reicast.

[skmp]

From @LoungeKatt on July 15, 2014 2:52

It needs to be fixed in the emulator or an update from Google that fixes graphics drivers in newer Android builds.

[kaim146]

I'm on a Galaxy J7Perx with R8 Reicast. I've attempted the 16, 24, and 32 "view rendering depth" options and they've failed to work for the broken notebook. I've attempted to use both "debug profiler" 1&2 but both result in the emulator freezing and not responding. I've also used 2 different files for Disc 1, but both have the same issue with the notebook (and Ryo's eyes glitching through his face during the opening cutscene)