

- Firestorm viewer 64 bit win 10 how to#
- Firestorm viewer 64 bit win 10 update#
- Firestorm viewer 64 bit win 10 windows#

Firestorm viewer 64 bit win 10 how to#
The firestorm link above shows you how to do that for many anti-virus programs. You also need to exclude the cache folders from anti-virus and security scans. firestorm-release64.exe (or firestorm-release.exe).You should have the following files excluded in your firewall: You won't be needing the Firestorm.bin or Firstorm.exe in there if you are using a more modern release of the viewer. For example, if your current version of Firestorm is installed in the folder "firestorm_圆4" make sure the exclusion is not set to "FirestormOS_圆4" or some other name. Many things have changed over the many versions of both Firestorm and your Operating System and you need to be sure that everything is still valid. HOWEVER, even if you have already done this in the past, go back and check to make sure the exclusions are still there and are still correct. Those are general directions and some bits are outdated. You need to make sure you add the correct filenames and folders and not just add exactly what they have listed there. Some of it does need to be updated to the current release, filenames, folders, and also made just a little clearer. One of the primary adjustments you will probably need to do is to exclude your viewer programs and folders from your firewall and anti-virus programs.į provides good instruction for accomplishing this ( Firestorm Whitelisting) for many anti-virus programs and your firewall. Operating systems and anti-virus programs can hinder, stymie, and block, communications and installations of the Firestorm Viewer. In this modern age of worry over hackers, trojans, worms, viruses, phishers, scammers, and probably aliens, everything is getting complicated. Outside of Firestorm (and any SL viewer) you probably will have to do some tweaking too for optimum efficiency and stability.
Firestorm viewer 64 bit win 10 windows#
I already reported this via the Feedback tool, but apparently it restricts visibility of issues to the language version of the local Windows installation, so I'm reporting this here as well so our users can add additional comments.ĮDIT 07-09-2016: Microsoft has been informed by Linden Lab and is investigating the issue.Firestorm is a wonderful feature filled viewer, complex at times, but with a little time and effort you can get the most out of your Second Life experience by learning the basics of the settings. There are also reports of other games suddenly showing the same kind of issue, all using OpenGL apparently: Personally, I experienced this issue twice already in a single day after I installed KB317698 but only after a random time and number of task switches. When this happens appears to be rather undeterministic - for some people it already happens right at the first task switch, for others after a random amount of time and task switches.įurther details (including system specs of users affected) can be obtained from our issue tracker at What happens exactly is, that for many users simply switching from our program to some other (program loses focus) and then switching back results in a drastic drop in frames per second, whereas scenes previously rendering perfectly fine are suddenly rendered

Firestorm viewer 64 bit win 10 update#
It turns out that all of these users are running Windows 10 and the issue started to arise after installing the latest Windows update KB3176938 (Windows Version 1607 Build 14393.105). They temporarily task-switched to a different program. Since a few days, we received several reports of users suddenly having severe performance issues using our program after I'm one of the developers for the Firestorm viewer () for accessing Linden Lab's Second Life using OpenGL.
