Skip to content
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.

[BUG-10819] [Intel HD Graphics 500 series] Screen flashes with certain graphics settings when any worn rigged mesh is in view textured with a diffuse texture set to alpha blending mode. #1110

Open
3 tasks
sl-service-account opened this issue Nov 30, 2015 · 2 comments

Comments

@sl-service-account
Copy link

sl-service-account commented Nov 30, 2015

  • This problem is being reported to Firestorm support with increasing frequency now that the new Intel Skylake processors with Intel HD 500 series graphics are in wider use.

  • Several of the affected users have verified that the problem happens on the current LL viewer - it reproduces on any viewer actually.

  • I do not have a system which reproduces this problem myself but getting someone on an affected system to file a LL JIRA issue for this has proved fruitless so far, so I'm filing it as I believe I have enough information now for a valid report.

  • I have no idea if this is even fixable in the viewer or whether it is a driver bug or a fault in the Intel 500 cards, but hopefully someone at LL has a system with Intel HD 500 series graphics and can reproduce this.

  • This bug appears to be specific to only the new Intel HD Graphics 500 series cards.

  • There are many different problems which can cause the viewer screen to flash but this one has very specific (& unfortuantely common) conditions that must be met to reproduce on the Intel HD 500 cards.

    Examples Of Affected Systems

    |Processor|Graphics Card|Driver Version|Open GL Version|Operating System|Notes|
    |
    |-|-|-|-|-|-|-|
    |Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz (2712 MHz)|Intel(R) HD Graphics 530|10.18.0015.4271|4.2.0 - Build 10.18.15.4271|Microsoft Windows 10 64-bit (Build 10240)|Landru McCallen, verified repro on LL viewer|
    |
    |Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (4007.99 MHz)|Intel(R) HD Graphics 530|10.18.0015.4279|4.2.0 - Build 10.18.15.4279|Microsoft Windows 10 64-bit (Build 10240)|Hazel Romano, verified repro on LL viewer|
    |
    |Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz (2496 MHz)|Intel(R) HD Graphics 520|10.18.0015.4293|4.2.0 - Build 10.18.15.4293|Microsoft Windows 10 64-bit (Build 10586)|Nyu Warblood, Surface 4 Pro|
    |
    |Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz (2591.98 MHz)|Intel(R) HD Graphics 520|10.18.0015.4248|4.2.0 - Build 10.18.15.4248|Microsoft Windows 10 64-bit (Build 10240)| Abbie Flagon. Optimus system luckily so fixed by switching to Nvidia card|
    |
    |Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz (2400 MHz)|Intel(R) HD Graphics 520|10.18.0015.4279|4.2.0 - Build 10.18.15.4279|Microsoft Windows 10 64-bit (Build 10240)|Fullmetalone Resident|
    |
    |Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (2591.99 MHz)|Intel(R) HD Graphics 530|20.19.0015.4352|4.2.0 - Build 20.19.15.4352|Microsoft Windows 10 64-bit (Build 10586)|Whirly Fizzle, THIS SYSTEM DOES NOT REPRODUCE THE BUG!|



    # Steps To Reproduce


    |

  • Login on an affected system with an Intel(R) HD Graphics 500 series card.

  • Either wear or stand near someone wearing any rigged mesh which has at least one face textured with a diffuse texture containing alpha which is set to alpha blending mode.

  • I attached a simple rigged cube & diffuse texture to this issue which will reproduce the problem.
    There is nothing special about this mesh or texture though - the problem will reproduce with any worn rigged mesh with a diffuse texture set to alpha blending.

    • Upload the attached Test png texture to SL.

    • Upload the attached Rigged_Cube.dae to SL. "Include skin weight" must be enabled in the Upload tab of the mesh upload window.

    • Texture the rigged cube with Test png texture set as the diffuse texture. Set alpha mode to alpha blending.

      The following conditions must be met to reproduce the flashing:

  • Worn rigged mesh in the scene which has at least one face textured with a diffuse texture containing alpha and set to alpha blending mode.
    Alpha masking and emissive mask mode do not reproduce the problem.
    Worn unrigged mesh does not reproduce the problem.

  • If ALM is disabled the flashing will always reproduce unless Hardware skinning is disabled.

  • If ALM is enabled the flashing will only reproduce when the avatar wearing the alpha blended rigged mesh is standing in or close to Linden water (Weird huh?)

  • If Hardware Skinning is disabled, the flashing stops in this case too.

    Observed Behaviour

  • Severe screen flashing where the repro meshes appear to explode constantly if the following conditions are met:
    When a repro mesh is worn by an avatar close to the person on an affected system with the following graphics settings, the bug will reproduce:

  • ALM disabled + Hardware skinning enabled.

  • ALM enabled + Hardware skinning enabled + Avatar wearing the mesh standing in Linden water.

  • See the attached gifs showing examples of the screen flashing.

  • Landru McCallen.gif shows a scene where only myself & Landru are present. I'm wearing a full body alpha with the rigged cube attachment textured with a single alpha blended diffuse texture - the orange box in the middle of the screen.
    As soon as I changed the texture to alpha masking+mask cutoff or emissive mask, the flashing ceased.

    Expected Behaviour

    No crazy flashing.

Attachments

Links

Related

Original Jira Fields
Field Value
Issue BUG-10819
Summary [Intel HD Graphics 500 series] Screen flashes with certain graphics settings when any worn rigged mesh is in view textured with a diffuse texture set to alpha blending mode.
Type Bug
Priority Unset
Status Accepted
Resolution Accepted
Reporter Whirly Fizzle (whirly.fizzle)
Created at 2015-11-30T02:10:35Z
Updated at 2018-08-03T13:05:11Z
{
  'Business Unit': ['Platform'],
  'ReOpened Count': 0.0,
  'Severity': 'Unset',
  'System': 'SL Viewer',
  'Target Viewer Version': 'viewer-development',
  'What just happened?': 'Filling in...',
  'What were you doing when it happened?': '...',
  'What were you expecting to happen instead?': '...',
}
@sl-service-account
Copy link
Author

Whirly Fizzle commented at 2016-01-31T03:07:47Z, updated at 2016-01-31T03:09:39Z

So. I have a new laptop with one of the affected cards, Intel(R) HD Graphics 530.
I cannot reproduce this bug on either the LL viewer or Firestorm viewer.

However, I'm using the new Intel driver released on Dec 22nd, https://downloadcenter.intel.com/download/25620/Intel-Graphics-Driver-for-Windows-7-8-1-10-15-40-6th-Gen-
So I'm hoping maybe the bug is fixed on this new driver.
Still waiting to hear back from other affected users if this driver update fixes them too.

Here is my system information:

Second Life 4.0.1 (310054) Jan 14 2016 18:17:17 (Second Life Release)
Release Notes

You are at 89.9, 115.1, 21.2 in Testylvania Sandbox located at sim8922.agni.lindenlab.com (216.82.41.98:12035)
SLURL: http://maps.secondlife.com/secondlife/Testylvania%20Sandbox/90/115/21
(global coordinates 332,634.0, 306,291.0, 21.2)
Second Life Server 16.01.19.310114
Retrieving...

CPU: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (2591.99 MHz)
Memory: 8113 MB
OS Version: Microsoft Windows 8 64-bit  (Build 9200) compatibility mode. real ver: 10.0 (Build 10011)
Graphics Card Vendor: Intel
Graphics Card: Intel(R) HD Graphics 530

Windows Graphics Driver Version: 20.19.0015.4352
OpenGL Version: 4.2.0 - Build 20.19.15.4352

libcurl Version: libcurl/7.38.0 OpenSSL/1.0.1h zlib/1.2.8
J2C Decoder Version: KDU v7.2
Audio Driver Version: FMOD Ex 4.44.31
LLCEFLib/CEF Version: 1.5.1-(CEF-WIN-3.2526.1347-32)
Voice Server Version: Vivox 4.6.0017.21209

Built with MSVC version 1800
Packets Lost: 1,016/34,444 (2.9%)

LL viewer still doesnt report the Windows 10 build number...
I'm on OS Version: Microsoft Windows 10 64-bit (Build 10586)

@sl-service-account
Copy link
Author

Whirly Fizzle commented at 2016-02-18T04:05:13Z, updated at 2016-02-18T04:05:29Z

I'm really quite sure now that this was a bug with the older Intel driver for the 500 series cards.
Updating to the latest 20.19.0015.4352 Intel driver has fixed multiple users having this bug who came to Firestorm support.

The release notes for this driver version (https://downloadcenter.intel.com/download/25620/Intel-Graphics-Driver-for-Windows-7-8-1-10-15-40-6th-Gen-) do actually list "Display may flicker on 6th Generation Intel Core and related processors" as a resolved issue.

Pretty sure it's safe to close the internal issue for this one.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant