search

secondlife / jira-archive

3 stars 0 forks source link

[BUG-225269] Graphics glitches in viewer 5.1.7.517973 (macOS) #4113

Closed sl-service-account closed 9 months ago

sl-service-account commented 6 years ago

What just happened?

Just letting the viewer idle, every few seconds (one to maybe about 30) large graphic glitches quickly appear and disappear across the entire viewer window. They do not appear to glich out viewer windows like inventory, chat, scripts, search, etc.

Unlike BUG-225225, the impact is not limited to Advanced Lighting Model or Nvidia graphics: I'm seeing it with Radeon graphics with or without Advanced Lighting enabled, although it seems more common with Advanced Lighting.

What were you doing when it happened?

Just standing.

What were you expecting to happen instead?

I don't expect the viewer to glitch in general, let alone glitch when nothing in a scene has changed

Other information

Seems new to viewer 5.1.7.517973 as I hadn't seen it before upgrading.

Attachments

Original Jira Fields | Field | Value | | ------------- | ------------- | | Issue | BUG-225269 | | Summary | Graphics glitches in viewer 5.1.7.517973 (macOS) | | Type | Bug | | Priority | Unset | | Status | Closed | | Resolution | Expected Behavior | | Reporter | Lou Netizen (lou.netizen) | | Created at | 2018-08-12T21:21:51Z | | Updated at | 2018-10-11T15:59:08Z | ``` { 'Build Id': 'unset', 'Business Unit': ['Platform'], 'Date of First Response': '2018-08-13T07:31:06.251-0500', "Is there anything you'd like to add?": "Seems new to viewer 5.1.7.517973 as I hadn't seen it before upgrading.", 'ReOpened Count': 0.0, 'Severity': 'Unset', 'System': 'SL Viewer', 'Target Viewer Version': 'viewer-development', 'What just happened?': "Just letting the viewer idle, every few seconds (one to maybe about 30) large graphic glitches quickly appear and disappear across the entire viewer window. They do not appear to glich out viewer windows like inventory, chat, scripts, search, etc.\r\n\r\nUnlike BUG-225225, the impact is not limited to Advanced Lighting Model or Nvidia graphics: I'm seeing it with Radeon graphics with or without Advanced Lighting enabled, although it seems more common with Advanced Lighting.", 'What were you doing when it happened?': 'Just standing.', 'What were you expecting to happen instead?': "I don't expect the viewer to glitch in general, let alone glitch when nothing in a scene has changed", } ```
sl-service-account commented 6 years ago

Lou Netizen commented at 2018-08-12T23:34:40Z

Example of one such glitch caught in a single frame of a screen capture. Not all look like this.

sl-service-account commented 6 years ago

Lou Netizen commented at 2018-08-13T00:03:00Z

Here's another: note the blue line in my avatar's hair and the glitch extending from it to the right.

sl-service-account commented 6 years ago

Whirly Fizzle commented at 2018-08-13T12:31:06Z

The earliest image looks like what happens when a vertex has zero weights - BUG-10747

sl-service-account commented 6 years ago

Whirly Fizzle commented at 2018-08-13T12:35:28Z, updated at 2018-08-13T12:36:06Z

Do you only see these glitches happen when worn rigged mesh is in the scene?

Does disabling either or these settings fix the problem?

sl-service-account commented 6 years ago

Lou Netizen commented at 2018-08-13T18:12:28Z, updated at 2018-08-13T18:19:26Z

Turning off either Open GL vertex buffer objects or Avatar Hardware Skinning (or both) seems to fix it, or at least reduce its frequency to the point where I can't distinguish it from other graphical refreshes and issues.

The only consistent rigged mesh item in scene when this has happened has been this hair. I doubt it has always been in the viewer window: https://marketplace.secondlife.com/p/TRUTH-HAIR-Stephania-Mesh-Hair-browns/5371730

If it is caused by rigged mesh, I have no idea what other people might have been wearing.

sl-service-account commented 6 years ago

Lou Netizen commented at 2018-08-14T00:32:29Z, updated at 2018-08-14T19:01:03Z

Another example: notice the pixelation and streaking. This is all-different clothing, but some of it is fitmesh. When I see it happen I always think it includes objecta in the background, but when I actually can isolate a frame of it, I can't rule out that this is only a (edit: RIGGED) mesh issue.

sl-service-account commented 6 years ago

Lou Netizen commented at 2018-08-14T21:38:18Z

Finally caught one where the background tweaks out. See the yellow rectangular areas on the map in the background? Those aren't in the map texture. And neither is the blue and green in the hair.

sl-service-account commented 6 years ago

Lou Netizen commented at 2018-08-14T21:40:12Z, updated at 2018-08-14T21:41:32Z

And I can now re-confirm the glitch occurs WITHOUT Advanced Lighting model enabled.

sl-service-account commented 6 years ago

Lou Netizen commented at 2018-08-14T21:54:21Z, updated at 2018-08-14T22:46:47Z

And I can now confirm the glitch happens without either OpenGL vertex buffer objects OR Advanced Lighting Model enabled. For me it is far less frequent, but it does happen.

sl-service-account commented 6 years ago

Lou Netizen commented at 2018-08-14T22:46:37Z

And I can now confirm that the glitch happens without Avatar Hardware Skinning enabled, although its frequency seems much reduced.

sl-service-account commented 6 years ago

Whirly Fizzle commented at 2018-08-15T03:15:29Z

Do you see the same problems on this viewer? http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/5.1.3.514233 This viewer was a build before the "Love Me Render" changes were merged in - Love Me Render was a bunch of rendering fixes. Just curious if something in that bunch of fixes caused the problem.

sl-service-account commented 6 years ago

Lou Netizen commented at 2018-08-15T19:18:18Z, updated at 2018-08-15T22:30:01Z

Am testing: so far it hasn't happened after several hours in 5.1.3.514233.

sl-service-account commented 6 years ago

Kyle Linden commented at 2018-08-16T15:10:31Z

Hi Lou,

Thanks for the update. Please let us know if any of the graphics issues occur on the 5.1.3 build.

Thanks!

sl-service-account commented 6 years ago

Lou Netizen commented at 2018-09-03T23:15:31Z, updated at 2018-09-03T23:15:53Z

I'm thinking this may not be a Second Life issue: I hadn't seen the bug for almost a week when it reappeared today pretty aggressively. I lived with it for a bit, but then thought to compare my application stack today compared to my app stack yesterday and the app stack when I filed this bug, and guess what? Only one thing is different when the bug appears!

Microsoft Remote Desktop 10.2.1

If I quit Remote Desktop, the glitches in SL stop.

I don't know what the proper thing to do here is in LL JIRA; projects I work on this would be classified as an "active" third-party incompatibility but I don't know how LL handles things.

sl-service-account commented 6 years ago

Whirly Fizzle commented at 2018-09-04T18:29:36Z

That's interesting. Those remote desktop type programs (like JoinMe or https://www.logmein.com/) often install a dummy graphics driver thingy (not sure what the correct technical term is for it - mirror driver I think?). I wonder if Help -> About Second Life will show a different graphics card &/or driver version when the bug is reproducing & when it isn't.

I also notice you have an incredibly low amount of texture memory in your system information: Texture memory: 96MB So I also wonder when Microsoft Remote Desktop is disabled, whether you have more texture memory available to the viewer.

I also don't know how to troubleshoot that on Mac, only on Windows. On Windows, you would use WMI Explorer available at https://wmie.codeplex.com/ to browse the WMI registry and check what video controllers & video memory is reported there. This will also show all the details for those remote dummy mirror driver things.

sl-service-account commented 6 years ago

Kyle Linden commented at 2018-09-05T16:02:15Z

Hi Lou,

Thank you for the detailed description of the issue. Whirly has asked all the questions I want to know about too. Please update with this information so we can sort out whether these class of applications (remote access clients) consume memory that negatively impacts SL performance.

If this is indeed the case we need to document it for all.

Thanks!

sl-service-account commented 6 years ago

Lou Netizen commented at 2018-09-05T20:28:44Z

Here's "About Second Life" from a cold boot just now: the only apps running are the SL viewer and a browser to connect to JIRA. I captured "About Second Life" before launching the browser. Upshot: same graphics reported, same graphics memory reported. (FWIW, the Radeon Pro 580 has 8GB of graphics memory.)

Second Life Release 5.1.8.518593 (64bit) Release Notes

CPU: Intel(R) Core(TM) i5-7600K CPU @ 3.80GHz (3800 MHz) Memory: 24576 MB OS Version: Mac OS X 10.13.6 Darwin 17.7.0 Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64 x86_64 Graphics Card Vendor: ATI Technologies Inc. Graphics Card: AMD Radeon Pro 580 OpenGL Engine

OpenGL Version: 2.1 ATI-1.68.20

Window size: 2229x1258 Font Size Adjustment: 108pt UI Scaling: 1 Draw distance: 128m Bandwidth: 1500kbit/s LOD factor: 1.375 Render quality: 3 / 7 Advanced Lighting Model: Enabled Texture memory: 96MB VFS (cache) creation time: August 11 2018 11:41:52

J2C Decoder Version: KDU v7.10.4 Audio Driver Version: FMOD Ex 4.44.64 Dullahan: 1.1.1080 / CEF: 3.3325.1750.gaabe4c4 / Chromium: 65.0.3325.146 LibVLC Version: 2.2.8 Voice Server Version: Not Connected September 05 2018 12:22:07

sl-service-account commented 6 years ago

Whirly Fizzle commented at 2018-09-05T20:46:16Z

If you uninstall Microsoft Remote Desktop & reboot, do you still only have 96MB texture memory showing in system information?

sl-service-account commented 6 years ago

Lou Netizen commented at 2018-09-05T21:07:34Z

Yep. May be an issue with the viewers' system profiler?

sl-service-account commented 6 years ago

Whirly Fizzle commented at 2018-09-05T23:41:54Z

Can you attach your viewer logs to this JIRA issue. Run a short sesssion where you see the texture memory as 96MB in Help -> About. Log out then zip up the viewer logs folder & attach it to this issue using More Actions -> Attach files. This page tells you how to find the logs folder: https://community.secondlife.com/knowledgebase/english/how-to-report-a-bug-r224/Section_.3#Section__3

Do you happen to also use Firestorm viewer? If so, does texture memory also show as 96MB in Help -> About Firestorm?

sl-service-account commented 6 years ago

Lou Netizen commented at 2018-09-06T17:27:08Z

Attached. I do not use Firestorm or other TPVs, I don't have time to vet them.

sl-service-account commented 6 years ago

Whirly Fizzle commented at 2018-09-06T18:23:50Z, updated at 2018-09-06T19:52:06Z

From log:

Version: Second Life Release 5.1.8.518593

INFO: #RenderInit;parseFeatureTable: Attempting to parse feature table from /Applications/Second Life Viewer.app/Contents/Resources/Second Life Viewer.app/Contents/Resources/featuretable_mac.txt INFO: #RenderInit;parseFeatureTable: Found feature table version 37 WARNING: #RenderInit;loadGPUClass: Unable to get an accurate benchmark; defaulting to class 3 INFO: #RenderInit;applyBaseMasks: Setting GPU Class to Class3 INFO: #RenderInit;maskFeatures: Applying GPU Feature list: Class3 INFO: #RenderInit;maskFeatures: Applying GPU Feature list: ATI INFO: #RenderInit;maskFeatures: Applying GPU Feature list: VRAMGT512 INFO: LLViewerTextureList::updateMaxResidentTexMem: Total Video Memory set to: 96MB MB INFO: LLViewerTextureList::updateMaxResidentTexMem: Available Texture Memory set to: 72MB MB

INFO: #RenderInit;printGLInfoString: GL_VENDOR: ATI Technologies Inc. INFO: #RenderInit;printGLInfoString: GL_RENDERER: AMD Radeon Pro 580 OpenGL Engine INFO: #RenderInit;printGLInfoString: GL_VERSION: 2.1 ATI-1.68.20

 

featuretable_mac.txt, V37: https://bitbucket.org/lindenlab/viewer-release/src/default/indra/newview/featuretable_mac.txt

RenderTextureMemoryMultiple 1 1.0   (allowed & enabled)

 

 

sl-service-account commented 6 years ago

Lou Netizen commented at 2018-09-06T19:30:40Z

So as I interpret that, this would be a separate issue with identifying the graphics system? Should I open a separate JIRA?

sl-service-account commented 6 years ago

Whirly Fizzle commented at 2018-09-06T19:55:18Z, updated at 2018-09-06T19:55:58Z

I'd wait for a Linden to tell you what to do.

There's something very odd going on here though.  I can find no other Jira issues on the LL Jira or the Firestorm Jira where a Mac (or Windows for that matter) has texture memory set as low as 96MB.

You're only effectively getting 72MB of texture memory too, which is terrible.

Only examples I can find of a 96MB texture memory are from Linux systems running the crappy Mesa graphics drivers - which is to be expected really.

Is your debug setting RenderGLCoreProfile set to TRUE or FALSE?

 

sl-service-account commented 6 years ago

Lou Netizen commented at 2018-09-06T20:05:49Z

RenderGLCoreProfile = FALSE

sl-service-account commented 6 years ago

Kyle Linden commented at 2018-09-13T16:05:23Z

Hi Lou,

I'm happy to hear that removing remote desktop cleared up the graphics issues. I looks like the only remaining oddity is the low texture memory. Will you open Me > Preferences > Graphics > Advanced Settings and see if you can move the Texture Memory slider all the way to the right for 512mb. Click OK as needed to close the open menus. Relaunch the viewer. Now open Help > About Second Life again. Does the Texture Memory report 512mb?

Please let us know and press Info Provided.

Thanks!

sl-service-account commented 6 years ago

Lou Netizen commented at 2018-09-13T21:34:09Z

Yes, in that case setting Graphics>Advanced>Texture Memory to 512MB seems to "stick" (at least through one relaunch) and About Second Life reports 512MB of texture memory available.

I have no insight as to how the graphics system detection works or how the SL viewer determines texture memory availability. Would it be worth trying to see how the default selections behave (if I recall I set it to something right above "Mid" and dialed particles and draw distance back), and opening a separate issue if those behaviors/memory detection aren't as expected?

sl-service-account commented 6 years ago

Kyle Linden commented at 2018-09-14T16:18:44Z

Hi Lou,

Very peculiar. If you were so inclined to experiment...

Would you try reinstalling the Remote Desktop app, launch it so that it consumes its normal amount of memory. Then launch Second Life and see if the SL Texture Memory is impacted.

If you find that it was reduced again, then we have a reproducible scenario that would be worth filing a fresh bug for. I would have expected that once the Remote Desktop software was removed and Second Life was relaunched that it would have detected more available memory and adjusted upward.

If you're not interested in trying this out, that's ok too. The good news is that I think we've solved the issue.

Please let me know and press Info Provided.

Thanks!

sl-service-account commented 6 years ago

Lou Netizen commented at 2018-09-14T17:56:51Z, updated at 2018-09-14T17:57:11Z

Re-installed Remote Desktop: memory does not reset to 96MB, remains at 512MB. Original graphics glitches are, again, very much in evidence while Remote Desktop sessions are open.

sl-service-account commented 6 years ago

Kyle Linden commented at 2018-10-11T15:59:09Z

Hi Lou,

Thank you for the confirmation that Remote Desktop on a Mac causes the issues. I'm sharing this information with our Support team and Documentation team so that others may be informed as well.

I really appreciate you working with me to identify the cause.

Thanks!