Bug 29584 - Falling back from GL ES 3.0 to 2.0 does not work
Summary: Falling back from GL ES 3.0 to 2.0 does not work
Status: RESOLVED NORESPONSE
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 5.1
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Radek Doulik
URL:
Depends on:
Blocks:
 
Reported: 2015-04-30 07:25 UTC by Grigory (Playtika)
Modified: 2017-09-14 18:42 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description Grigory (Playtika) 2015-04-30 07:25:30 UTC
If i first pass 3.0 and it fails (old device),  then if i pass 2.0 it will also fail.
But if i pass 2.0 from start - everything will be okay.

private bool CreateFrameBuffer(GLVersion version, GraphicsMode graphicsMode)
        {
            bool res = false;
            try
            {
                ContextRenderingApi = version;
                GraphicsMode = graphicsMode;
                base.CreateFrameBuffer();
                res = true;
            }
            catch (Exception ex)
            {
                Dev.Log.WriteLine("Failed to create frame buffer {0}", ex.Message);
            }
            return res;
        }
Comment 1 Radek Doulik 2015-05-06 09:43:36 UTC
Could you please attach a test project that demonstrates this?
Comment 2 Jon Douglas [MSFT] 2017-09-14 18:42:51 UTC
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!