Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebGL is not working #103

Closed
HADB opened this issue Jan 25, 2019 · 9 comments
Closed

WebGL is not working #103

HADB opened this issue Jan 25, 2019 · 9 comments
Assignees

Comments

@HADB
Copy link

HADB commented Jan 25, 2019

WebGL is not working in v1.5.0

@David-Desmaisons
Copy link
Member

Could you create a project with a minimal set-up with this problem, so I can investigate?
Thanks.

@HADB
Copy link
Author

HADB commented Jan 26, 2019

OK, I will give you next week.
PS: I'm trying to show a web page in iframe which using WebGL and tells me WebGL not working.

@David-Desmaisons
Copy link
Member

Meanwhile try to check the log and verify if you need to set a CEFswitch

@HADB
Copy link
Author

HADB commented Feb 1, 2019

Hi, I have set up a minimal project https://github.com/HADB/Neutronium.Vue.SPA.WebGL

What I have done:

  1. Create a project with Neutronium.Vue.SPA template
  2. Edit View/src/main.vue, add an iframe element which contains a WebGL sample source
<template>
    <main>
      <v-content>
        <v-container fluid class="main-container">
          <iframe src="https://webglsamples.org/aquarium/aquarium.html" />
        </v-container>
      </v-content>
    </main>
</template>

<style>
...
iframe{
  width: 100%;
  height: 100%;
}
...
</style>
  1. Build and run

Screenshots:

  1. The WebGL sample in chrome
    chrome
  2. Result in Neutronium app
    demo

I have got these logs in bin/Debug/debug.log

[0201/123700.292:ERROR:gpu_process_transport_factory.cc(1026)] Lost UI shared context.
[0201/123702.108:ERROR:viz_main_impl.cc(201)] Exiting GPU process due to errors during initialization
[0201/124014.290:ERROR:gpu_process_transport_factory.cc(1026)] Lost UI shared context.
[0201/124015.670:ERROR:viz_main_impl.cc(201)] Exiting GPU process due to errors during initialization
[0201/124714.916:ERROR:gpu_process_transport_factory.cc(1026)] Lost UI shared context.
[0201/124716.235:ERROR:viz_main_impl.cc(201)] Exiting GPU process due to errors during initialization
[0201/125059.216:ERROR:gpu_process_transport_factory.cc(1026)] Lost UI shared context.
[0201/125101.345:ERROR:viz_main_impl.cc(201)] Exiting GPU process due to errors during initialization
[0201/125700.305:ERROR:gpu_process_transport_factory.cc(1026)] Lost UI shared context.
[0201/125701.889:ERROR:viz_main_impl.cc(201)] Exiting GPU process due to errors during initialization
[0201/125832.476:ERROR:gpu_process_transport_factory.cc(1026)] Lost UI shared context.
[0201/125834.127:ERROR:viz_main_impl.cc(201)] Exiting GPU process due to errors during initialization

@HADB
Copy link
Author

HADB commented Feb 1, 2019

Maybe this is related to the following line but I didn't test because I couldn't find a way to remove this CEFswitch.

@David-Desmaisons
Copy link
Member

It seems that this is linked to this switch indeed, I can add a way to not call this switch although this might cause other problem in the display.

@David-Desmaisons
Copy link
Member

@HADB I will provide in version 1.5.1 a way to not disable Gpu. On ChromiumFxWebBrowserApp:

        /// <summary>
        /// Set to true to allow Gpu
        /// </summary>
        protected virtual bool AllowGpu => false;

I remember that the past using GPU could introduce some bugs in display so by default Gpu will continue to be disabled.

@David-Desmaisons
Copy link
Member

Available in version 1.5.2

@HADB
Copy link
Author

HADB commented Feb 21, 2019

Problem solved. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants