Thread Rating:
Pixel C
|
09-30-2015, 12:40 PM
With Google's last Tegra-based device, they refused to ship it with the full OpenGL driver, majorly hampering its usefulness as an emulation device. If they do that again, it might well render a lot of stuff unplayable.
OS: Windows 10 64 bit Professional
CPU: AMD Ryzen 5900X RAM: 16GB GPU: Radeon Vega 56 09-30-2015, 12:51 PM
Hopefully the change in brand name means a change in philosophy. If this is really a surface competitor it needs the Tegra feature set to complete the package
09-30-2015, 01:20 PM
If they ship with Nvidia's OpenGL ES 3.2 drivers then it won't be a big deal anymore.
Only a few minor things missing at that point.
Well the Nexus 9 volantis kernel is freely available in AOSP. So when Android Marshmallow is released in a few days, we should be able to see what drivers and OpenGL (ES) support there is.
I'd be surprised if the drivers for the Pixel C Android only worked for the Tegra X1. https://source.android.com/source/building-kernels.html 12-09-2015, 06:29 PM
I guess I'll post here.
Google is shipping the Pixel C with Nvidia's OpenGL ES 3.2 driver. They have disabled desktop OpenGL again. Luckily though, since it is Nvidia. They have all the extensions required to not have a visible impact on performance anymore. There are only /very/ minor things missing when running under Nvidia's latest ES 3.2 driver. Here's a list of the things still broken or not working there in Dolphin. - EFB Color peeks - This can be fixed, I just haven't felt like it. We expect BGRA, we give it RGBA under ES. - Video dumping - This can actually be enabled on Tegra since they support an extension that would work around the issue. Wanted to implement it differently so all ES devices could use it (Mainly for FifoCI) - LogicOps - Who cares, these aren't available in ES 2.0 or higher. - Texture LOD bias - This isn't supported by ES or by an extension. We could emulate this ourselves fairly easily. This will most likely never be noticed in any game. - Texture dumping - Another thing that I can't care enough to make work under ES. It's fairly easy to fix, haven't seen a reason to spend time fixing it. And that's it, that's all that is different between running in ES 3.2 + all of Nvidia's extensions versus their GL 4.5 driver. Everything else is properly implemented for performance and correct emulation(In the GPU emulation at least), so no one will notice anything different than running it on another Tegra device that has desktop GL. Unless of course you hit those specific things(EFB color peeks being the big broken item there). I'll also leave with this remark. Just because Nvidia does this well under their ES 3.2 driver, doesn't mean the other mobile vendors will do this well. The other mobile vendors don't support near as many extensions as Nvidia, so they will still hit performance issues and feature losses depending on what they've implemented. I'll be able to find out exactly what they are missing in the future when they release their drivers. 12-09-2015, 07:32 PM
We need to be fair, this list must be seperated in known bugs and missing features. Known bugs which just need a fix (patches are welcome):
(12-09-2015, 06:29 PM)Sonicadvance1 Wrote: - EFB Color peeks - This can be fixed, I just haven't felt like it. We expect BGRA, we give it RGBA under ES. Required features: (12-09-2015, 06:29 PM)Sonicadvance1 Wrote: - LogicOps - Who cares, these aren't available in ES 2.0 or higher.As both features are very uncommon, I doubt you'll notice *any* difference at all ![]() 12-18-2015, 07:41 PM
Hi, already made someone experiences with the pixel C
I have tested the latest Dolphin version, unfortunately without success CU Christian 12-21-2015, 05:49 PM
Hi,
I've just tested the Build 4.0 8400 #1807 The start screen with the Wii controller appears, in the next screen "Could not write to/read from wii System Memory" then the program crashes. CU Christian |
« Next Oldest | Next Newest »
|
Users browsing this thread: 1 Guest(s)