* Clear uniforms before first program use on all platforms: (), () *Applied Workarounds: exit_on_context_lost* * Some drivers are unable to reset the D3D device in the GPU process sandbox * disabled_extension_GL_KHR_blend_equation_advanced_coherent * disabled_extension_GL_KHR_blend_equation_advanced * enable_bgra8_overlays_with_yuv_overlay_support * clear_uniforms_before_first_program_use * Hardware Protected Video Decode: Hardware accelerated * Out-of-process Rasterization: Hardware accelerated Compared to Chrome, the only difference is that “Skia Renderer” is disabled in Brave. PS: Github doesn't allow registration of accounts, so I'm unable to "file an issue" at NW.js' repo there.Info on brave://gpu/ shows that the WebGL is HW accelerated. Interestingly, the "glove view" feature is available when I just looked at Google Maps in Vivaldi (on the same computer), which is a browser that is also using Chromium. Online, there are about six trillion search results about this, but all of them are years old and completely unrelated to NW.js. ![]() How is it possible that the "globe view" is disabled in spite of using their latest browser engine? It just doesn't make sense. But now, the "globe view" feature (which is crucial) is simply "greyed out"/disabled, as if I were running a browser from 1994 or something.īut I'm literally using Google's own engine, and I made sure to re-build it yesterday with the latest version of NW.js (meaning latest version of Chromium). Until a couple of weeks or so ago, there were no problems. I have given it a feature which on request opens a new window of itself (Chromium) with Google Maps at the specified coordinates. I use NW.js (Chromium) to make a desktop map application for my own use.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |