Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Black color back ground issue
kaku_yamamoto
Member Posts: 8 ✭
in General
I'm sorry if my question is not suitable for this category.
My Onshape display a black colored back ground screen.
This started a few days ago...
How can I fix this issue?
My Onshape display a black colored back ground screen.
This started a few days ago...
How can I fix this issue?
0
Comments
The issue you are seeing is likely related to this question : https://forum.onshape.com/discussion/14644/problem-with-onshape-and-google-chrome#latest
Please try the steps in Pete Yodis' reply and see if it resolves the issue.
To help us determine the cause of this issue, please type chrome://gpu in Chrome and then past the results back here in this thread. Thank you
I changed the rendering to "Enable".
Now I can see the genuine back ground display.
Unforunately, today the black display is back...
Now my chrome settings are 1) Override software rendering list ..."Enable" 2) Hardware acceleration ..."Checked".
But my Onshape doesn't display genuine white back ground... X(
chrome://gpu results are below.
Graphics Feature Status
Driver Bug Workarounds
Problems Detected
Applied Workarounds: exit_on_context_lost
Applied Workarounds: clear_uniforms_before_first_program_use
Applied Workarounds: scalarize_vec_and_mat_constructor_args
Applied Workarounds: force_cube_complete
Applied Workarounds: disable_discard_framebuffer
Applied Workarounds: disable_direct_composition
Applied Workarounds: disable_dxgi_zero_copy_video
Applied Workarounds: disable(GL_KHR_blend_equation_advanced), disable(GL_KHR_blend_equation_advanced_coherent)
Applied Workarounds: decode_encode_srgb_for_generatemipmap
Applied Workarounds: disable_dxgi_zero_copy_video
Applied Workarounds: disable_nv12_dxgi_video
Applied Workarounds: disable_accelerated_vp9_decode, disable_accelerated_vp8_decode
Applied Workarounds: disable_delayed_copy_nv12
Applied Workarounds: disable_vp_scaling
Applied Workarounds: disable_direct_composition_video_overlays
Applied Workarounds: disable_nv12_dynamic_textures
Applied Workarounds: limit_d3d11_video_decoder_to_11_0
Applied Workarounds: use_empty_video_hdr_metadata
Applied Workarounds: disable_accelerated_vp8_decode
ANGLE Features
On some GPUs, program binaries don't contain transform feedback varyings
Some users rely on a lost context notification if a GL_OUT_OF_MEMORY error occurs
Always rewrite vec/mat constructors to be consistent
On some drivers TexImage sometimes seems to interact with the Framebuffer
On some drivers when rendering with no render target, two bugs lead to incorrect behavior
Some drivers corrupt texture data when clearing for robust resource initialization.
Using clear() may not take effect
Bug in some drivers triggers a TDR when using CopySubresourceRegion from a staging texture to a depth/stencil
Textures with the format DXGI_FORMAT_B5G6R5_UNORM have incorrect data
Fails to allocate ShaderResourceView for StructuredBuffer on some drivers
Using isnan() on highp float will get wrong answer
1x1 and 2x2 mips of depth/stencil textures aren't sampled correctly
The HLSL optimizer has a bug with optimizing 'pow' in certain integer-valued expressions
Some drivers sometimes write out-of-order results to StreamOut buffers when transform feedback is used to repeatedly write to the same buffer positions
On some drivers the return value from RWByteAddressBuffer.InterlockedAdd does not resolve when used in the .yzw components of a RWByteAddressBuffer.Store operation
Some drivers do not take into account the base level of the texture in the results of the HLSL GetDimensions builtin
Some drivers have a bug where they ignore null render targets
HLSL's function texture.Load returns 0 when the parameter Location is negative, even if the sum of Offset and Location is in range
Evaluating unary minus operator on integer may get wrong answer in vertex shaders
The viewport or render target slice will be selected in the geometry shader stage for the ANGLE_multiview extension
Set data faster than image upload
In specific cases the driver doesn't handle constant register zero correctly
Some D3D11 renderers do not support geometry shaders for pointsprite emulation
Copying from staging storage to constant buffer storage does not work
Missing an option to disable mipmaps on a mipmapped texture
Version Information
Driver Information
Compositor Information
GpuMemoryBuffers Status
Display(s) Information
Video Acceleration Information
Vulkan Information
Device Performance Information
Diagnostics
Log Messages
This is likely due to the recent Chrome update. Please use an alternate browser such as Firefox.
Paul