Closed mcliston closed 1 year ago
What I'm trying to understand is if I'm uploading these visuals up to a report server, is the visual actually looking for the GPU on that machine (the server)?
@mcliston hardware acceleration (or a software rendering fallback, like Chrome provides) is required on the device that accesses the Power BI report to view from PBI Server or Online. No GPU is required on the PBI report server itself, only the client consuming it requires WebGL.
My issue has been following the pattern of some past posts about this subject; Chrome works well (because the software is driving the web GL rendering) and IE and Edge show either a blank screen or returns a message about the browser not supporting web GL.
To make sure I understand your issue - you are unable to render a Mapbox map visual in a PBIX workbook that you've published to Power BI Report Server using IE or Edge, but it does work using Chrome? To double check, are you using the Mapbox Visual hosted on the Microsoft Store marketplace?
cc/ @samgehret
@ryanbaumann thank you for the timely response. Yes, you are correct. I generated the visuals in Power BI desktop, uploaded to the report server, and then am trying to access them via Chrome/Edge/IE (Edge = no WebGL support message, IE = blank screen, Chrome = OK).
In regard to the marketplace, I access the mapbox option within Power BI desktop (adding the mapbox icon via the marketplace options).
To add, I've done all the browser checks for WebGL compliance (I forgot the weblink off the top of my head but it's been posted in like posts) and all have WebGL 1 support.
To add, I've done all the browser checks for WebGL compliance (I forgot the weblink off the top of my head but it's been posted in like posts) and all have WebGL 1 support.
Interesting. I'm re-checking our IE and Edge support on the latest release. I'm able to see Edge for sure - the no WebGL message could be a browser specific thing on the machine you're testing on. Do you use an external monitor?
@mcliston
The IE blank screen is a great catch - digging into that now. I'm seeing it too on https://app.powerbi.com/view?r=eyJrIjoiZmFiNjhhY2EtMGQwMi00YzZlLWJjMTQtZWRiMDEwYjcyM2ZkIiwidCI6IjYyOWE3MGIyLTMyYjktNDEyNi05NTFlLTE3NjA0Y2Y0NTZlYyIsImMiOjF9
The machine that I am testing on is a desktop with external monitors (I recall seeing other posts talking about this, probably with you moderating). But I'm not positive if that setup requires extra drivers for those external monitors, if that is the issue. I'll be checking come Monday.
In the meant time I'll get a hold of a machine with IE and Edge to check out the link you sent.
@ryanbaumann Just wondering if you foresee a solution to this on the horizon? Just wanted to give a client an update on options.
Hello, the choropleth layer doesn't work in Edge by me either. Firefox and Chrome are fine. I get the same error about Web GL and GPU.. I am using the newest 1.3 Mapbox version for PowerBI. What is interesting, that in the end of October (surely on the 19th of October), the same dashboard was correctly shown in Edge, with the same version of Power-Bi visual. So maybe it is the newest version of Edge?
Hi @iCatCat, what hardware and OS and Edge version are you running Edge on where the visual does not function with the Mapbox Visual for Power BI? I'm unable to replicate this on my local machine.
Hi @ryanbaumann I have Windows 10 64 bit Edge version: Microsoft Edge 41.16299.248.0 , Microsoft EdgeHTML 16.16299 Edge Screenshot: Firefox:
Thanks @iCatCat - What does your hardware setup look like? Can you type in Chrome chrome://gpu/
and paste the results here? Are you using a specific laptop or desktop model, or a VM?
@ryanbaumann to create my dashbaords I am using Power BI Desktop August 2018 Version. To publish them we use Power BI Server Version 1.3.6801.38816 (August 2018), a local version, not cloud. It is installed on the remote server, not local on my pc.
Here is the GPU report from chrome:
Graphics Feature Status
Canvas: Hardware accelerated
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
Out-of-process Rasterization: Unavailable
Hardware Protected Video Decode: Unavailable
Rasterization: Unavailable
Skia Deferred Display List: Disabled
Skia Renderer: Disabled
Surface Synchronization: Enabled
Video Decode: Hardware accelerated
Viz Service Display Compositor: Disabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated
Driver Bug Workarounds
clear_uniforms_before_first_program_use
decode_encode_srgb_for_generatemipmap
disable_discard_framebuffer
disable_dxgi_zero_copy_video
disable_framebuffer_cmaa
disable_nv12_dxgi_video
exit_on_context_lost
force_cube_complete
scalarize_vec_and_mat_constructor_args
disabled_extension_GL_KHR_blend_equation_advanced
disabled_extension_GL_KHR_blend_equation_advanced_coherent
Problems Detected
Some AMD drivers have rendering glitches with GPU Rasterization: 653538
Disabled Features: gpu_rasterization
Protected video decoding with swap chain is for Windows and Intel only
Disabled Features: protected_video_decode
Some drivers are unable to reset the D3D device in the GPU process sandbox
Applied Workarounds: exit_on_context_lost
Clear uniforms before first program use on all platforms: 124764, 349137
Applied Workarounds: clear_uniforms_before_first_program_use
Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
ANGLE crash on glReadPixels from incomplete cube map texture: 518889
Applied Workarounds: force_cube_complete
Framebuffer discarding can hurt performance on non-tilers: 570897
Applied Workarounds: disable_discard_framebuffer
Use GL_INTEL_framebuffer_CMAA on ChromeOS: 535198
Applied Workarounds: disable_framebuffer_cmaa
Disable KHR_blend_equation_advanced until cc shaders are updated: 661715
Applied Workarounds: disable(GL_KHR_blend_equation_advanced), disable(GL_KHR_blend_equation_advanced_coherent)
Decode and Encode before generateMipmap for srgb format textures on Windows: 634519
Applied Workarounds: decode_encode_srgb_for_generatemipmap
Zero-copy DXGI video hangs or displays incorrect colors on AMD drivers: 623029
Applied Workarounds: disable_dxgi_zero_copy_video
NV12 DXGI video displays incorrect colors on older AMD drivers: 644293
Applied Workarounds: disable_nv12_dxgi_video
Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
Disabled Features: native_gpu_memory_buffers
Viz service display compositor is not enabled by default.
Disabled Features: viz_display_compositor
Skia renderer is not used by default.
Disabled Features: skia_renderer
Skia deferred display list is not used by default.
Disabled Features: skia_deferred_display_list
Version Information
Data exported 2018-11-08T07:30:19.592Z
Chrome version Chrome/70.0.3538.77
Operating system Windows NT 10.0.16299
Software rendering list URL https://chromium.googlesource.com/chromium/src/+/0f6ce0b0cd63a12cb4eccea3637b1bc9a29148d9/gpu/config/software_rendering_list.json
Driver bug list URL https://chromium.googlesource.com/chromium/src/+/0f6ce0b0cd63a12cb4eccea3637b1bc9a29148d9/gpu/config/gpu_driver_bug_list.json
ANGLE commit id 05c729f336ef
2D graphics backend Skia/70 193565807f7fd2a2c14e21b44c545cc03ebe134f-
Command Line "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --flag-switches-begin --flag-switches-end
Driver Information
Initialization time 171
In-process GPU false
Passthrough Command Decoder false
Sandboxed true
GPU0 VENDOR = 0x1002, DEVICE= 0x6611 ACTIVE
GPU1 VENDOR = 0x0000, DEVICE= 0x0000
GPU2 VENDOR = 0x0000, DEVICE= 0x0000
GPU3 VENDOR = 0x0000, DEVICE= 0x0000
GPU4 VENDOR = 0x0000, DEVICE= 0x0000
GPU5 VENDOR = 0x0000, DEVICE= 0x0000
GPU6 VENDOR = 0x8086, DEVICE= 0x5912
Optimus false
AMD switchable false
Desktop compositing Aero Glass
Direct Composition true
Supports overlays false
Overlay capabilities
Diagonal Monitor Size of \.\DISPLAY3 21.9"
Diagonal Monitor Size of \.\DISPLAY2 21.9"
Driver D3D12 feature level Not supported
Driver Vulkan API version Not supported
Driver vendor Advanced Micro Devices, Inc.
Driver version 21.19.128.4
Driver date 9-3-2016
GPU CUDA compute capability major version 0
Pixel shader version 5.0
Vertex shader version 5.0
Max. MSAA samples 8
Machine model name
Machine model version
GL_VENDOR Google Inc.
GL_RENDERER ANGLE (AMD RadeonT R5 430 Direct3D11 vs_5_0 ps_5_0)
GL_VERSION OpenGL ES 2.0 (ANGLE 2.1.0.05c729f336ef)
GL_EXTENSIONS GL_ANGLE_client_arrays GL_ANGLE_depth_texture GL_ANGLE_explicit_context GL_ANGLE_explicit_context_gles1 GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_lossy_etc_decode GL_ANGLE_pack_reverse_row_order GL_ANGLE_program_cache_control GL_ANGLE_request_extension GL_ANGLE_robust_client_memory GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_CHROMIUM_bind_generates_resource GL_CHROMIUM_bind_uniform_location GL_CHROMIUM_color_buffer_float_rgb GL_CHROMIUM_color_buffer_float_rgba GL_CHROMIUM_copy_compressed_texture GL_CHROMIUM_copy_texture GL_CHROMIUM_sync_query GL_EXT_blend_minmax GL_EXT_color_buffer_half_float GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_disjoint_timer_query GL_EXT_draw_buffers GL_EXT_frag_depth GL_EXT_map_buffer_range GL_EXT_occlusion_query_boolean GL_EXT_read_format_bgra GL_EXT_robustness GL_EXT_sRGB GL_EXT_shader_texture_lod GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc_srgb GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_rg GL_EXT_texture_storage GL_EXT_unpack_subimage GL_KHR_debug GL_KHR_parallel_shader_compile GL_NV_EGL_stream_consumer_external GL_NV_fence GL_NV_pack_subimage GL_NV_pixel_buffer_object GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth32 GL_OES_element_index_uint GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_surfaceless_context GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_array_object OES_compressed_EAC_R11_signed_texture OES_compressed_EAC_R11_unsigned_texture OES_compressed_EAC_RG11_signed_texture OES_compressed_EAC_RG11_unsigned_texture OES_compressed_ETC2_RGB8_texture OES_compressed_ETC2_RGBA8_texture OES_compressed_ETC2_punchthroughA_RGBA8_texture OES_compressed_ETC2_punchthroughA_sRGB8_alpha_texture OES_compressed_ETC2_sRGB8_alpha8_texture OES_compressed_ETC2_sRGB8_texture
Disabled Extensions GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent
Disabled WebGL Extensions
Window system binding vendor Google Inc. (adapter LUID: 0000000000008be8)
Window system binding version 1.4 (ANGLE 2.1.0.05c729f336ef)
Window system binding extensions EGL_EXT_create_context_robustness EGL_ANGLE_d3d_share_handle_client_buffer EGL_ANGLE_d3d_texture_client_buffer EGL_ANGLE_surface_d3d_texture_2d_share_handle EGL_ANGLE_query_surface_pointer EGL_ANGLE_window_fixed_size EGL_ANGLE_keyed_mutex EGL_ANGLE_surface_orientation EGL_ANGLE_direct_composition EGL_NV_post_sub_buffer EGL_KHR_create_context EGL_EXT_device_query EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_get_all_proc_addresses EGL_KHR_stream EGL_KHR_stream_consumer_gltexture EGL_NV_stream_consumer_gltexture_yuv EGL_ANGLE_flexible_surface_compatibility EGL_ANGLE_stream_producer_d3d_texture EGL_ANGLE_create_context_webgl_compatibility EGL_CHROMIUM_create_context_bind_generates_resource EGL_CHROMIUM_sync_control EGL_EXT_pixel_format_float EGL_KHR_surfaceless_context EGL_ANGLE_display_texture_share_group EGL_ANGLE_create_context_client_arrays EGL_ANGLE_program_cache_control EGL_ANGLE_robust_resource_initialization EGL_ANGLE_create_context_extensions_enabled
Direct rendering Yes
Reset notification strategy 0x8252
GPU process crash count 0
Compositor Information
Tile Update Mode One-copy
Partial Raster Enabled
GpuMemoryBuffers Status
ATC Software only
ATCIA Software only
DXT1 Software only
DXT5 Software only
ETC1 Software only
R_8 Software only
R_16 Software only
RG_88 Software only
BGR_565 Software only
RGBA_4444 Software only
RGBX_8888 GPU_READ, SCANOUT
RGBA_8888 GPU_READ, SCANOUT
BGRX_8888 Software only
BGRX_1010102 Software only
RGBX_1010102 Software only
BGRA_8888 Software only
RGBA_F16 Software only
YVU_420 Software only
YUV_420_BIPLANAR Software only
UYVY_422 Software only
Display(s) Information
Info Display[2779098405] bounds=[1680,0 1680x1050], workarea=[1680,0 1680x1010], scale=1, external.
Color space information {primaries:BT709, transfer:IEC61966_2_1, matrix:RGB, range:FULL}
Bits per color component 8
Bits per pixel 24
Info Display[2841568472] bounds=[0,0 1680x1050], workarea=[0,0 1680x1010], scale=1, external.
Color space information {primaries:BT709, transfer:IEC61966_2_1, matrix:RGB, range:FULL}
Bits per color component 8
Bits per pixel 24
Video Acceleration Information
Decode h264 baseline up to 1920x1088 pixels
Decode h264 baseline up to 1088x1920 pixels
Decode h264 main up to 1920x1088 pixels
Decode h264 main up to 1088x1920 pixels
Decode h264 high up to 1920x1088 pixels
Decode h264 high up to 1088x1920 pixels
Encode h264 baseline up to 3840x2176 pixels and/or 30.000 fps
Encode h264 main up to 3840x2176 pixels and/or 30.000 fps
Encode h264 high up to 3840x2176 pixels and/or 30.000 fps
Diagnostics
... loading ...
Log Messages
GpuProcessHostUIShim:
GpuProcessHostUIShim:
Thanks for opening this issue, @mcliston, and for responding @ryanbaumann. I am also experiencing the problem of no MapBox visual loading on Internet Explorer. I am able to view the visual on Google Chrome and Microsoft Edge, and on Power BI Desktop.
Has the been any progress toward solving this problem? Thank you
@banwarp yes, @samgehret and his team are working on a fix for this in the next release.
Edit - specifically will address compatibility of the Mapbox Visual with IE11 in the latest release on the Office Store. It will not address WebGL errors related to hardware acceleration.
Any update with Mapbox and IE11? I see that the Mapbox visual loads in Edge, but not working in IE11 still.
@PowerBIwjkolesar we're continuing to see this issue on IE11. Is it possible to use Edge or another browser?
Thanks for the response @ryanbaumann - unfortunately, at this time that is not an option for us. Are there plans to resolve the issue with IE11? I know this bug has been open since Nov 2018 - and like you said it works in other browsers. But wondering where this bug falls in line of priority. It has pretty high level visibility due to the Mapbox custom visual not loading on Power BI report we have for many users.
Same situation here - about 20% of our customers run IE, generally because of restrictive government IT departments. We're close to launching a new feature with the Mapbox custom visual in Power BI Embedded, but it looks like we'll either need to hack a workaround for IE users or use a different visual (none of which are as great as Mapbox).
Hi, Same issue here, the Mapbox visual in Power BI works fine in Chrome and Edge, but in IE it doesn't load at all. This is a major issue if you want to embed the report, because you can't ask all customers to not use IE. I see this issue has been mentioned here a long time ago but has not been solved yet.
At least please update with an expectation so that we know what to expect from Mapbox..
Thanks
The latest version of the Mapbox Visual for Power BI in the Office Store does not support IE11. This question is reflected in our FAQ here for future reference:
But, will this be solved at all? If it doesn’t support IE11, then you cannot use Mapbox visual for Power BI embedded.
Please advice,
Thanks, Emile
Met vriendelijke groet / Kind regards, CRM Partners BV Emile van Lier Consultant
Emile.van.Lier@crmpartners.com +31 (6) 22180919
From: Ryan Baumann notifications@github.com Sent: woensdag 15 januari 2020 10:19 PM To: mapbox/mapboxgl-powerbi mapboxgl-powerbi@noreply.github.com Cc: Emile van Lier Emile.van.Lier@crmpartners.com; Comment comment@noreply.github.com Subject: Re: [mapbox/mapboxgl-powerbi] Mapbox / Power BI choropleth in IE and Edge (#253)
The latest version of the Mapbox Visual for Power BI does not support IE11.
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/mapbox/mapboxgl-powerbi/issues/253?email_source=notifications&email_token=AMAQXPZKSXYHWATYHPFAF73Q554U7A5CNFSM4GBOX5ZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJB24BQ#issuecomment-574860806, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMAQXP4QGULTNUGONKIII4LQ554U7ANCNFSM4GBOX5ZA.
Hi, I'm trying to implement some choropleths in multiple types of browsers which I understand has been an issue because of the need for direct gpu support. My issue has been following the pattern of some past posts about this subject; Chrome works well (because software is driving the web GL rendering) and IE and Edge show either a blank screen or returns a message about the browser not supporting web GL.
In my situation we are running Power BI on premises and upload to a report server within the intranet.
What I'm trying to understand is if I'm uploading these visuals up to a report server, is the visual actually looking for the GPU on that machine (the server)? Is there a definitive fix for this?