Tabitha Oxide

Im having the same issue as of 5-16-14 with the newest release of firestorm 64bit. __________________________ Windows 8.1 / 64bit Firestorm 64bit Nvidia GTX 870m (3gb) 12 gb ram __________________________ -Tabitha

the past 48 hours have been SL misery. Its not you or your connection. The Servers are having all sorts of problems including inventory, rezzing, and connection stability. Its 8pm 5-1 eastern time and Its getting worse as today continues. I just logged out to clear my cashe and now cannot connect to the servers.. Just be patient.. after over 7 yrs I can tell you that this is amazingly normal and will come frequently..

Firestorm-Release 4.6.1.40478 - Clean Install Date: 3-24 (BROKEN WITH MEMORY LEAKS) As of this posting the latency issues continue. This is being felt by many users with a variety of different system setups, processors, Ram, Gfx Adapters... Regardless of your particular system configuration (fast computer/slow computer) - (draw distance and or Graphics Settings) many users are experienceing the same problems with latency or lag connected to the grid with the newest release of Firestorm. A LOT of internal changes were made when the upgraded from the BETA version to get it working and I suspect that some memory leaks were not caught and corrected. After several complete clean installs (meaning that you uninstall the old viewer and all the hidden files that are left behind - including a purge of all firestorm registry entries before the fresh install) It has been my experience that at first, the grid runs pretty well but as time goes on (about 20 minutes) poor performance creeps back in and movement regardless of the land and its occupancy is very laggy. I can take my draw distance from 200m to 30M and have very little effect. Clearing the cashe at this point has zero effect and is not the root problem. I believe that this version of the viewer is simply broken and has memory leaks that will no doubt be addressed in hopefully a new release comming soon. I too love using Firestorm but also agree that somewhere within the spaghetti layered code there is a problem with this viewer version and suggest users stick with Beta if it works for you, or just trying one of the various other viewers out there untill resolved. -Tabi