(08-02-2017, 01:06 PM)JonnyH Wrote: [ -> ]Yes, but dolphin requires GLES3 (which isn't supported on sgx), and the current head uses features that hit bugs that weren't fixed until (relatively) recently.
All rogue cores should support GLES3.1 with the AEP (the only thing missing from 3.2 is ASTC, which was added in the Rogue-XT refresh)
Rogue first gen (6X30 and 6X00) do not include the AEP silicon. If the implementation is possible it was never used. The GX6X50's do actually support ASTC, as it's a mandatory part of AEP and then 3.2. They are the only core to include it optionally, but only Apple to my knowledge excluded the extended silicon. The most common implementation is the GX6250 in the MT8173/8176 which is used in devices like the Mi Pad 3, which offer full ES3.2 compliance. The 7 XE series optionally can include it but adoption of those units is basically unknown on android. The 7XT includes it mandatorily for android bound implementations, however the OGL 4.4 compliance (the new addition to the 7 series) was optional for desktop implementations. 8XE includes it mandatorily. So ATM basically every major android device that implements compatible rogue hardware also supports a nougat update with ES3.2 on board.
(08-02-2017, 10:42 PM)Nintonito Wrote: [ -> ]Rogue first gen (6X30 and 6X00) do not include the AEP silicon. If the implementation is possible it was never used. The GX6X50's do actually support ASTC, as it's a mandatory part of AEP and then 3.2. They are the only core to include it optionally, but only Apple to my knowledge excluded the extended silicon. The most common implementation is the GX6250 in the MT8173/8176 which is used in devices like the Mi Pad 3, which offer full ES3.2 compliance. The 7 XE series optionally can include it but adoption of those units is basically unknown on android. The 7XT includes it mandatorily for android bound implementations, however the OGL 4.4 compliance (the new addition to the 7 series) was optional for desktop implementations. 8XE includes it mandatorily. So ATM basically every major android device that implements compatible rogue hardware also supports a nougat update with ES3.2 on board.
Sorry, I kinda flubbed that: Yes, for the 6 series (6x00/6x30) astc was the only hw feature that killed gles3.2/AEP support. 6xt/6xe (6x50/6x10) supported that (being the large/small 'refresh' cores).
After series 6 the names changed slightly, rather than xe/xt being the 'refresh' names, they became the small/large designs from the start.
Not sure where you got the idea series 7 supports desktop GL, that's unlikely to ever happen even if the hw could support it.
And 7xe was replaced quickly enough by 8xe that I'm not sure there's any expectation of release silicon for that.
8xe is a continuation of the rogue design, just tuned/optimised - 8xt is a rather different design (and not really ready for product release quite yet).
All PowerVR products allow specific features to be disabled on a per-customer basis, but we *strongly* recommend people don't (and I don't think anyone does for "user-level" features at least)
(08-03-2017, 03:55 AM)JonnyH Wrote: [ -> ]Sorry, I kinda flubbed that: Yes, for the 6 series (6x00/6x30) astc was the only hw feature that killed gles3.2/AEP support. 6xt/6xe (6x50/6x10) supported that (being the large/small 'refresh' cores).
After series 6 the names changed slightly, rather than xe/xt being the 'refresh' names, they became the small/large designs from the start.
Not sure where you got the idea series 7 supports desktop GL, that's unlikely to ever happen even if the hw could support it.
And 7xe was replaced quickly enough by 8xe that I'm not sure there's any expectation of release silicon for that.
8xe is a continuation of the rogue design, just tuned/optimised - 8xt is a rather different design (and not really ready for product release quite yet).
All PowerVR products allow specific features to be disabled on a per-customer basis, but we *strongly* recommend people don't (and I don't think anyone does for "user-level" features at least)
Desktop GL is specced out by Imagination, for Intel and Spreadtrum's x86 processor that elect to use poweVR graphics on a desktop computer (as was done before with Series 5). Its never been done due to a total lack of adoption but Imagine still specs the chips in case. As for disabling specific features, I think Apple is the only one that does it, and that's mostly because they're still baby steps with Metal, and OGL for them is dead.
(08-03-2017, 07:39 AM)Nintonito Wrote: [ -> ]Desktop GL is specced out by Imagination, for Intel and Spreadtrum's x86 processor that elect to use poweVR graphics on a desktop computer (as was done before with Series 5). Its never been done due to a total lack of adoption but Imagine still specs the chips in case. As for disabling specific features, I think Apple is the only one that does it, and that's mostly because they're still baby steps with Metal, and OGL for them is dead.
The design for PowerVR chips hasn't really been driven by 'desktop' features for some time. Naturally, there's a lot of crossover, as often widely used desktop features are the 'next' thing pulled into the mobile versions, and some things are cheap enough that you "may as well" - but there hasn't been any true in-depth feature work for desktop support since the sgx 5x5 versions. Not that there's really much "big" stuff left in desktop that's not already possible using the mobile APIs, if you cut out the compatibility stuff, outside of perhaps some 'easy' features.
For the most part, the software development of new desktop API versions has stopped. That is likely the real the reason why you'll never see GL4.x on PowerVR (unless something changes).
Hi. I have an other question and I wound open a new thread.
This time my question is for resident evil code veronica I can play it buy with an red color but when you chance of room by the doors the color is the auténtica. Is there some special configuration.
Tanks.
Ps. I played really 4of wii and have the same problem that re4 of GameCube the smog efect