Jump to content
  • 0

Mesh stopped loading in every viewer. Suspected Windows 10 Update?


Kira Zobel
 Share

You are about to reply to a thread that has been inactive for 2438 days.

Please take a moment to consider if this thread is worth bumping.

Question

  • 0

Hmmm... you don't both happen to be using Webroot antivirus software do you?

There have been a spate of reports over the last few days of corrupted mesh and texture loading and the one thing so far everyone has had in common is they are using Webroot antivirus software and the problem started after a recent Webroot definitions update.

The viewer logs we have seen from those suffering from this problem on Firestorm show the usual nasty symptoms when firewall/antivirus software is not compatible with Pipelining in the viewer.  Disabling Pipelining or disabling Webroot will fix this problem.

It would be great if you could file a JIRA issue and attach your viewer logs after running a session where you reproduce this problem. The viewer logs will easily show if it is the usual problem of Antivirus/Firewall + Pipelining incompatibility.

Once that's established, it can be investigated what's causing the problem on your system.

Instructions on how to file a Firestorm JIRA issue and where to find the viewer logs: http://wiki.phoenixviewer.com/file_a_jira

On the LL viewer, go to Help -> Report a bug, to file a JIRA issue.

Where to find logs on the LL viewer: http://community.secondlife.com/t5/English-Knowledge-Base/How-to-report-a-bug/ta-p/733545#Section_.3

Link to comment
Share on other sites

1 answer to this question

Recommended Posts

  • 0

Hmmm... you don't both happen to be using Webroot antivirus software do you?

There have been a spate of reports over the last few days of corrupted mesh and texture loading and the one thing so far everyone has had in common is they are using Webroot antivirus software and the problem started after a recent Webroot definitions update.

The viewer logs we have seen from those suffering from this problem on Firestorm show the usual nasty symptoms when firewall/antivirus software is not compatible with Pipelining in the viewer.  Disabling Pipelining or disabling Webroot will fix this problem.

It would be great if you could file a JIRA issue and attach your viewer logs after running a session where you reproduce this problem. The viewer logs will easily show if it is the usual problem of Antivirus/Firewall + Pipelining incompatibility.

Once that's established, it can be investigated what's causing the problem on your system.

Instructions on how to file a Firestorm JIRA issue and where to find the viewer logs: http://wiki.phoenixviewer.com/file_a_jira

On the LL viewer, go to Help -> Report a bug, to file a JIRA issue.

Where to find logs on the LL viewer: http://community.secondlife.com/t5/English-Knowledge-Base/How-to-report-a-bug/ta-p/733545#Section_.3

Link to comment
Share on other sites

You are about to reply to a thread that has been inactive for 2438 days.

Please take a moment to consider if this thread is worth bumping.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...