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

Can BIMSurfer offer 2 versions, one is for WEBGL2 and another is for WEBGL1? #63

Open
huangsn10 opened this issue Dec 6, 2019 · 4 comments

Comments

@huangsn10
Copy link

Since most of the current Web Browsers do not support the webGL2 so that it is unable to see 3D scene in mobile phone by BIMSurferV3, so can the BIM SurferV3.0 add one options of selecting between WebGL1 and WebGL2? It means that there will be 2 versions of BIMSurferV3, one is for GL1 and another is for GL2. Is it possible ? how difficult about that?

@rubendel
Copy link
Member

rubendel commented Dec 6, 2019

Most of the current Web Browsers actually DO support WebGL2, Safari is the only one not supporting it.

I would estimate the development effort to be about 120 hours. You would end up with a viewer with probably a few features missing and pretty bad performance (relative to the WebGL2 version).

@akuckartz
Copy link

@huangsn10 Maybe you can ask Apple Inc. to finance such a development - or to allow modern browsers on iOS devices ;-)

@aothms
Copy link
Member

aothms commented Dec 6, 2019

WebGL 2 offers function calls to selectively read and overwrite buffers stored in GPU memory. Without this the kind of interactivity in a viewer like this would be much harder to implement (and may require additional copies of the data to be accessible by JS (webgl1 gpu buffers are not) or fetch data again from the server when modifications in state need to occur. Assuming you have access to the OES_element_index_uint extension (very common on desktop webgl implementations) I don't think performance necessarily needs to be a lot worse.

@huangsn10
Copy link
Author

@rubendel OK thanks alot and I will continue to follow this issue, I am looking forward to see the viewer and I think it will be welcome to most of the user

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

4 participants