Tegra 4 Testing

[Steel01]

I saw some commits recently about work on Tegra 4 devices, but I didn't see a thread or posts about it, so I'm starting a testing thread. If I missed one somewhere, please merge this in with it.

I have a Nvidia Shield, so I pulled a buildbot compiled apk of version 4.0-194, the latest android apk to build. Current revisions are failing on the arm JitIL (buildbot output). Anyways, like Sonic said, I get no video output with GLES. However, I don't get video output for software either. When I use the software renderer on my Galaxy S3, I get the intro screens in Windwaker before it hangs. I'd like to help do some debugging myself, but I don't know where to start. Afaik, I can't pipe gdb into my Shield. Is there a way to get it to write a log out somewhere?

Thanks for working on this,
Steel01

P.S. Out of curiosity, which Tegra 4 device is being used to develop this?

Edit: Wow, so I set the CPU Core to interpreted and fired off Star Fox Assault, then went to do something else and almost forgot about it. Maybe half an hour later, I started hearing sounds. So, I guess the JIT has problems on the Shield. Last time I ran it with JIT, I came back to see it had failed back to the game list.

[Sonicadvance1]

Comex broke the jit in recent changes, working on fixing them.
Project shield is used for testing.
I have no idea why the software rasterizer is failing, is truly a mystery for me there.
I should have some changes in the coming days for OGL output on it.

[Steel01]

Does the software renderer not work for you on the Shield either? And okay, I'll keep an eye on the commit log and report back with testing after you get those GL changes in.

Thanks again,
Steel01

Edit: Update with the recent build (4.0-203). First, yay for being able to see the settings more easily, thanks Lioncash. Second, trying to launch a game with either JIT immediately falls back to the game list without any error. Third, with the interpreter, I get a couple green triangles within a few seconds on Starfox Assault. So, seems like the commit works as advertised. Except maybe for JIT, but I expect that's known.

[Steel01]

New testing with build 229 with Windwaker. I finally saw something! With JitIL, I can get into the menus. And all things considered, it's running really fast, somewhere around 20-30 fps by guestimation. The fps counter doesn't show up. The graphics have a bad case of spiky polygon syndrome, but that was a given by one of the commit messages. One other bug I should have mentioned before is that axises don't map correctly. D-pad, sticks, triggers, they all map to axis-16+. I don't even know what that is, I might go pull up CWM's keypad tester and see if it picks up the joystick presses to find out. But the normal button presses work fine.

Steel01

Edit: Scratch the input bug. Stuff mapped correctly this last try. Slightly confused as to what changed there, but hey it worked. However, it's not capturing the input correctly as the settings tab changed on main stick and d-pad left right.

Edit 2: Getting in game a little bit. More like 4-6 fps there. Which still isn't bad for the second or third commit for tegra. And it hung right before getting the telescope, meh.

[pete3k]

Thanks Shield01 for updating us with the testing of the current version of Dolphin on Shield.
How do you compile the latest version?
Where do you get the source from?
Are there instructions I can use to compile everything???

Thanks

[Steel01]

https://dl.dolphin-emu.org/builds/

I don't know why it's not easier to find the android builds, but that's the output directory of the buildbot. You want one like dolphin-master-4.0-229.apk. 229 was the last one I got, you most likely want the highest number. Do note that you'll have to uninstall the dolphin version from the play store or the apk install will error out.

With those, you don't have to compile it yourself. If you really want to compile it yourself, you'll have to wait for a dev or figure it out yourself. I haven't tried to set up a dev tree and build the apk.

Steel01

[ricardo85x]

Hi

Since Tegra does not support any official Open-GL ES, So do you guys think Dolphin will run fast on tegra 4 devices someday? Or should I stop visiting this forum daily with hopes about the Shield?

thanks.

[Link_to_the_past]

(11-03-2013, 12:11 PM)ricardo85x Wrote: Hi

Since Tegra does not support any official Open-GL ES, So do you guys think Dolphin will run fast on tegra 4 devices someday? Or should I stop visiting this forum daily with hopes about the Shield?

thanks.

Let me quote the part below from google play:

Quote:If you're expecting reasonable speeds out of this, you are sorely
mistaken. This will run slow on every single Android device, no matter
if it is the most powerful one in the world.

And Tegra 4 is not even the fastest arm cpu currently.... But streaming works from a desktop pc with shield if you want to try.

[Guilherme]

Will the Dolphin Emu for Android supports OpenGL ES 2.0 emulation? I use it on my PC with the G33/G31 video card that supports OpenGL ES 1.X, and that runs not so bad. I think the OpenGL ES 2.0 support would be better than Software Redering. I think I would get between 5-10 FPS on my games. With Software Rendering I get 1 FPS, sometime (almost never) 3.

[ricardo85x]

(11-03-2013, 12:35 PM)Link_to_the_past Wrote:

(11-03-2013, 12:11 PM)ricardo85x Wrote: Hi

Since Tegra does not support any official Open-GL ES, So do you guys think Dolphin will run fast on tegra 4 devices someday? Or should I stop visiting this forum daily with hopes about the Shield?

thanks.

Let me quote the part below from google play:

Quote:If you're expecting reasonable speeds out of this, you are sorely
mistaken. This will run slow on every single Android device, no matter
if it is the most powerful one in the world.

And Tegra 4 is not even the fastest arm cpu currently.... But streaming works from a desktop pc with shield if you want to try.

Hi

I know the actual state(slow for every device) My question is about if I should have hope for improviments for tegra 4. Or if the improviments will only come for devices with Open-GL ES 3.