Open
Bug 1184800
Opened 9 years ago
Updated 2 years ago
YouTube 360° videos are displayed as flat panorama images when Firefox is running in a Windows VM
Categories
(Core :: Graphics, defect, P3)
Core
Graphics
Tracking
()
People
(Reporter: cpeterson, Unassigned)
References
()
Details
(Whiteboard: [gfx-noted] [platform-rel-Youtube])
YouTube 360° videos work well for me on OS X and for Anthony on Linux and real Windows hardware, but in my Windows 8.1 VM, Firefox displays the 360 video as a flat panorama image. Anthony wondered whether this is an issue with WebGL in a VM.
Reporter | ||
Comment 1•9 years ago
|
||
Chrome 43 plays the 360 videos correctly in the same Windows VM. In IE, YouTube displays a message saying 360 video is not supported in IE yet. https://www.youtube.com/watch?list=PLbsGxdAPhjv_tgCNWGaGvSnlIMZNkmnrM&v=7IaYJZ2Usdk
status-firefox39:
--- → affected
status-firefox42:
--- → affected
Reporter | ||
Updated•9 years ago
|
status-firefox40:
--- → affected
status-firefox41:
--- → affected
Matt - this smells more graphicsy than media. What do you think?
Flags: needinfo?(matt.woodrow)
Chris, does WebGL work in your VM?
Flags: needinfo?(cpeterson)
Reporter | ||
Comment 4•9 years ago
|
||
In my Windows VM, WebGL works in Chrome 43 and IE 11, but not Nightly 42.
Component: Video/Audio → Graphics
Flags: needinfo?(cpeterson)
That's the underlying problem then. Youtube's 360 videos require WebGL.
(In reply to Robert O'Callahan (:roc) (Mozilla Corporation) from comment #5) > That's the underlying problem then. Youtube's 360 videos require WebGL. The open question is why doesn't WebGL work inside the VM?
Reporter | ||
Comment 7•9 years ago
|
||
about:support for my Windows 8.1 VM says WebGL is "blocked for your graphics card because of unresolved driver issues." Application Basics ------------------ Name: Firefox Version: 42.0a1 Build ID: 20150720030213 Update Channel: nightly User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0 Multiprocess Windows: 0/1 (default: false) Safe Mode: false Graphics -------- Adapter Description: VMware SVGA 3D Adapter Drivers: vm3dum64 vm3dum Adapter RAM: 384 Asynchronous Pan/Zoom: none Device ID: 0x0405 Direct2D Enabled: Blocked for your graphics card because of unresolved driver issues. DirectWrite Enabled: false (6.3.9600.17795) Driver Date: 7-29-2014 Driver Version: 8.14.1.51 GPU #2 Active: false GPU Accelerated Windows: 1/1 Direct3D 11 WARP (OMTC) Subsys ID: 040515ad Supports Hardware H264 Decoding: false Vendor ID: 0x15ad WebGL Renderer: Blocked for your graphics card because of unresolved driver issues. windowLayerManagerRemote: true AzureCanvasBackend: skia AzureContentBackend: cairo AzureFallbackCanvasBackend: cairo AzureSkiaAccelerated: 0
Chris - still happening?
Whiteboard: [gfx-noted]
Reporter | ||
Comment 10•9 years ago
|
||
I can still reproduce this problem in my Windows 8.1 and 10 VMs with Nightly 42 build 2015-07-26. Graphics -------- Adapter Description: VMware SVGA 3D Adapter Drivers: vm3dum64 vm3dum Adapter RAM: 1024 Asynchronous Pan/Zoom: wheel input enabled Device ID: 0x0405 Direct2D Enabled: Blocked for your graphics card because of unresolved driver issues. DirectWrite Enabled: false (10.0.10166.0) Driver Date: 7-29-2014 Driver Version: 8.14.1.51 GPU #2 Active: false GPU Accelerated Windows: 1/1 Direct3D 11 WARP (OMTC) Subsys ID: 040515ad Supports Hardware H264 Decoding: false Vendor ID: 0x15ad WebGL Renderer: Blocked for your graphics card because of unresolved driver issues. windowLayerManagerRemote: true AzureCanvasBackend: skia AzureContentBackend: cairo AzureFallbackCanvasBackend: cairo AzureSkiaAccelerated: 0
Comment 11•8 years ago
|
||
Firefox 44 also affected.
(In reply to Chella from comment #11) > Firefox 44 also affected. What does it say in the WebGL Renderer line in about:support?
Updated•8 years ago
|
platform-rel: --- → ?
Updated•8 years ago
|
Whiteboard: [gfx-noted] → [gfx-noted] [platform-rel-Youtube]
Updated•8 years ago
|
platform-rel: ? → -
Updated•7 years ago
|
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•