Double checking something with my gpu settings in Vivaldi
-
So I am on my old computer for a few weeks and one thing that is getting me is making sure that everything is as speedy as possible. One thing I noticed is that my vivaldi://gpu is showing some interesting parts and I am not sure if this is supposed to be this way. [spoiler] 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: Disabled Native GpuMemoryBuffers: Software only. Hardware acceleration disabled Rasterization: Software only. Hardware acceleration disabled Video Decode: Hardware accelerated Video Encode: Hardware accelerated WebGL: Hardware accelerated Driver Bug Workarounds clear_uniforms_before_first_program_use disable_discard_framebuffer exit_on_context_lost force_cube_complete scalarize_vec_and_mat_constructor_args texsubimage_faster_than_teximage Problems Detected Some drivers are unable to reset the D3D device in the GPU process sandbox Applied Workarounds: exit_on_context_lost TexSubImage is faster for full uploads on ANGLE Applied Workarounds: texsubimage_faster_than_teximage 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 Accelerated rasterization has been disabled, either via about:flags or command line. Disabled Features: rasterization Raster is using a single thread. Disabled Features: multiple_raster_threads Native GpuMemoryBuffers have been disabled, either via about:flags or command line. Disabled Features: native_gpu_memory_buffers [/spoiler] From my understanding, if Hardware Acceleration is enabled and working under chrome, then all of them should be on and green. So what is wrong with this? I have tried decode switch flag I saw on another post, enabling the overwrite for the GPU blacklist and nothing seems to have changed. About the only thing I haven't done is install 32-bit and see what happens. If ya need info: Windows 10 core 64-bit AMD Radeon HD 7770 AMD Athlon II x2 250 (3GHZ) Vivaldi 64-bit
-
"…all of them should be on and green."
Not necessarily. The browser engine is supposed to be able to detect which things will or will not work with your hardware, only turn on the ones that will work, and use workarounds for others, while ignoring still others and leaving them un-accelerated. -
Mine works perfectly normally, and looks like this:
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
Rasterization: Software only. Hardware acceleration disabled
Video Decode: Hardware accelerated
Video Encode: Hardware accelerated
WebGL: Hardware accelerated
Driver Bug Workarounds
clear_uniforms_before_first_program_use
disable_discard_framebuffer
exit_on_context_lost
force_cube_complete
scalarize_vec_and_mat_constructor_args
texsubimage_faster_than_teximage
use_current_program_after_successful_link
Problems Detected
Always call glUseProgram after a successful link to avoid a driver bug: 349137
Applied Workarounds: use_current_program_after_successful_link
Some drivers are unable to reset the D3D device in the GPU process sandbox
Applied Workarounds: exit_on_context_lost
TexSubImage is faster for full uploads on ANGLE
Applied Workarounds: texsubimage_faster_than_teximage
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
Accelerated rasterization has been disabled, either via about:flags or command line.
Disabled Features: rasterization
Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
Disabled Features: native_gpu_memory_buffers
Version Information
Data exported 5/10/2016, 3:28:11 PM
Chrome version Chrome/50.0.2661.89
Operating system Windows NT 10.0
Software rendering list version 10.18
Driver bug list version 8.59
ANGLE commit id unknown hash
2D graphics backend Skia
Command Line Args Snapshots\Application\vivaldi.exe" –always-authorize-plugins --disable-translate --ppapi-flash-path="C:\WINDOWS\SysWOW64\Macromed\Flash\pepflashplayer32_22_0_0_144.dll" --flag-switches-begin --flag-switches-end
Driver Information
Initialization time 518
In-process GPU false
Sandboxed false
GPU0 VENDOR = 0x10de, DEVICE= 0x104a
Optimus false
AMD switchable false
Desktop compositing Aero Glass
Diagonal Monitor Size of \.\DISPLAY1 23.9"
Driver vendor NVIDIA
Driver version 10.18.13.6510
Driver date 4-27-2016
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 (NVIDIA GeForce GT 610 Direct3D11 vs_5_0 ps_5_0)
GL_VERSION OpenGL ES 2.0 (ANGLE 2.1.0.unknown hash)
GL_EXTENSIONS GL_OES_element_index_uint GL_OES_packed_depth_stencil GL_OES_get_program_binary GL_OES_rgb8_rgba8 GL_EXT_texture_format_BGRA8888 GL_EXT_read_format_bgra GL_NV_pixel_buffer_object GL_OES_mapbuffer GL_EXT_map_buffer_range GL_EXT_color_buffer_half_float GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_float GL_OES_texture_float_linear GL_EXT_texture_rg GL_EXT_texture_compression_dxt1 GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_OES_compressed_ETC1_RGB8_texture GL_EXT_sRGB GL_ANGLE_depth_texture GL_OES_depth32 GL_EXT_texture_storage GL_OES_texture_npot GL_EXT_draw_buffers GL_EXT_texture_filter_anisotropic GL_EXT_occlusion_query_boolean GL_NV_fence GL_EXT_disjoint_timer_query GL_EXT_robustness GL_EXT_blend_minmax GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_pack_reverse_row_order GL_OES_standard_derivatives GL_EXT_shader_texture_lod GL_EXT_frag_depth GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_EXT_discard_framebuffer GL_EXT_debug_marker GL_OES_EGL_image GL_EXT_unpack_subimage GL_NV_pack_subimage GL_OES_vertex_array_object GL_KHR_debug GL_ANGLE_lossy_etc_decode
Disabled Extensions
Window system binding vendor Google Inc. (adapter LUID: 0000000000008ec7)
Window system binding version 1.4 (ANGLE 2.1.0.unknown hash)
Window system binding extensions EGL_EXT_create_context_robustness EGL_ANGLE_d3d_share_handle_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_ANGLE_flexible_surface_compatibility
Direct rendering Yes
Reset notification strategy 0x8252
GPU process crash count 0
Compositor Information
Tile Update Mode One-copy
Partial Raster Disabled
GpuMemoryBuffers Status
ATC Software only
ATCIA Software only
DXT1 Software only
DXT5 Software only
ETC1 Software only
R_8 Software only
RGBA_4444 Software only
RGBX_8888 Software only
RGBA_8888 Software only
BGRX_8888 Software only
BGRA_8888 Software only
YUV_420 Software only
YUV_420_BIPLANAR Software only
UYVY_422 Software only
Diagnostics
0
b3DAccelerationEnabled true
b3DAccelerationExists true
bAGPEnabled true
bAGPExistenceValid true
bAGPExists true
bCanRenderWindow true
bDDAccelerationEnabled true
bDriverBeta false
bDriverDebug false
bDriverSigned false
bDriverSignedValid false
bNoHardware false
dwBpp 32
dwDDIVersion 11
dwHeight 1080
dwRefreshRate 60
dwWHQLLevel 0
dwWidth 1920
iAdapter 0
lDriverSize 17369768
lMiniVddSize 0
szAGPStatusEnglish Enabled
szAGPStatusLocalized Enabled
szChipType GeForce GT 610
szD3DStatusEnglish Enabled
szD3DStatusLocalized Enabled
szDACType Integrated RAMDAC
szDDIVersionEnglish 11.3
szDDIVersionLocalized 11.3
szDDStatusEnglish Enabled
szDDStatusLocalized Enabled
szDXVAHDEnglish Supported
szDXVAModes ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
szDescription NVIDIA GeForce GT 610
szDeviceId 0x104A
szDeviceIdentifier {D7B71E3E-530A-11CF-B063-47301CC2C735}
szDeviceName \.\DISPLAY1
szDisplayMemoryEnglish 4095 MB
szDisplayMemoryLocalized 4095 MB
szDisplayModeEnglish 1920 x 1080 (32 bit) (60Hz)
szDisplayModeLocalized 1920 x 1080 (32 bit) (60Hz)
szDriverAssemblyVersion 10.18.13.6510
szDriverAttributes Final Retail
szDriverDateEnglish 4/27/2016 12:00:00 AM
szDriverDateLocalized 4/27/2016 00:00:00
szDriverLanguageEnglish English
szDriverLanguageLocalized English
szDriverModelEnglish WDDM 2.0
szDriverModelLocalized WDDM 2.0
szDriverName nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um,nvwgf2um
szDriverNodeStrongName oem114.inf:0f066de31a238341:Section001:10.18.13.6510:pci\ven_10de&dev_104a
szDriverSignDate
szDriverVersion 10.18.0013.6510
szKeyDeviceID Enum\PCI\VEN_10DE&DEV_104A&SUBSYS_104A196E&REV_A1
szKeyDeviceKey \Registry\Machine\System\CurrentControlSet\Control\Video{397CFF1B-12ED-49D4-AFB0-CFEDA5A47B81}\0000
szManufacturer NVIDIA
szMiniVdd n/a
szMiniVddDateEnglish n/a
szMiniVddDateLocalized n/a
szMonitorMaxRes
szMonitorName Dell E2414H (Digital - DVI)
szNotesEnglish No problems found.
szNotesLocalized No problems found.
szOverlayEnglish Supported
szRankOfInstalledDriver 00D12001
szRegHelpText
szRevision
szRevisionId 0x00A1
szSubSysId 0x104A196E
szTestResultD3D7English Not run
szTestResultD3D7Localized Not run
szTestResultD3D8English Not run
szTestResultD3D8Localized Not run
szTestResultD3D9English Not run
szTestResultD3D9Localized Not run
szTestResultDDEnglish Not run
szTestResultDDLocalized Not run
szVdd n/a
szVendorId 0x10DE
Log Messages
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay. -
Interesting. But shouldn't multiple raster threads at least in my end be enabled? I am pretty sure I have both the VRAM (2GB) and the card capabilities to utilize raster threads better, shouldn't I?
-
Only if the firmware of the card and the software of the browser are compatible. Cards and browsers don't all speak the same language. Some graphics cards, no matter how advanced, have to have hardware acceleration disabled, pretty much for this or that browser to work at all.
-
Hi man, this is a really old thread but I have some pointers, if you are still using that old computer:
For modern HW acceleration of VIDEO please buy at least a bit more-modern cheap GPU, for example some Geforce with Pascal GPU or latter. Basically anything from GT 1030 and higher. Be carefult to have a card with GDDR5, not DDR3.
Then you have to tinker with settings as you tried. It will be possible to set all of the settings to HW acclerate Vivaldi with the GPU except one thing: multiple raster threads. This is because you have only 2-core cpu and Vivaldi/Chromium will not turn on multiple raster threads if you don't have at least 3 cores/threads working in the machine. You CAN force it but the performance will be nearly the same as without the feature. So upgrade the CPU to 4X as well and you will see the feature auto-activated.
Finally, you didn't write about it in detail, but please upgrade your memory. For your system the DDR3 is dirt-cheap on second-hand market and it's really worth it if you can supply your Win 10 system with an abundance of RAM. I saw this with my own eyes, there was a clear-as-a-day difference between 64-bit system with 4GB of RAM and 64-bit system with 16GB of RAM, preferably with some modern Kaveri (Athlon II x4 860) / Godavari (Athlon II x4 870) CPU, perhaps even Athlon II x4 845 Carrizo, if you can get your hands onto it. These CPUs will allow you to use your RAM if it supports XMP profiles with speeds even higher than 2133 Mhz!!
So upgrade, upgrade, upgrade your system to the maximum.
God Speed!
-
Oh, I just realized you went AM3 Phenom/FX route, so get those, they have enough performance and many more cores. Dirt cheap as well. Make sure to know what RAM speeds their northbridge will support, so you can upgrade to the highest possible speed RAM.
-
@Beholder4096 well that is a heck of a thread necro in my e-mail, mainly because of the moderator post that I think realized a bit late :face_with_stuck-out_tongue_winking_eye:
This was during the time of my older pc being used for a few weeks while I was repairing my newer PC cause of a weird issue that happened. In fact, seeing the tags, this post was designed from the old forums and Vivaldi had MANY MANY MANY changes.
@zapoqx said in Double checking something with my gpu settings in Vivaldi:
So I am on my old computer for a few weeks and one thing that is getting me is making sure that everything is as speedy as possible.
Basically Ayespy was possibly right and I had the newer PC back soon, but I wasn't gonna rip out my R7 260X to test if it was board communication or GPU for the old PC. I was just genuinely curious given at the time I tested and could pull it off with Firefox. I'm on a newer and better graphics card since then and even on a newer PC than the new PC (at the time) that I had (i5-4690 -> R5-3600X) with even more memory since. Don't think its an issue so you can relax
-
Ppafflick moved this topic from Vivaldi for Windows on
