Whirly Fizzle
-
Posts
4,719 -
Joined
-
Last visited
Content Type
Forums
Blogs
Knowledge Base
Posts posted by Whirly Fizzle
-
-
Which viewer are you using?
I just tried to repoduce that on the latest release of Viewer 3 and Firestorm 4.5.1 beta and it did not reproduce.
-
-
What you are seeing are all known problems with the new version of Vivox (voice) found in Firestorm and Viewer 3. As far as I know, Singularity is still using the older voice version so I doubt anything changed at their end.
Running 2 or more viewers where at least one is using the new voice version will cause the voice connection popups even if voice is disabled in the viewers or blocked from connecting in your Firewall. The multuple popups that never stop spawning is also a known problem some people have.
The only workaround I can give you, which will stop the problem on Firestorms end is to tick the "Do not show me this again" box on Firestorms error message. This will probably not stop the popups from constantly spawning on Singularity though.
-
As far as the memory bloat is concerned, Firestorm does suffer just the same as Viewer 3.
The performance issue is Viewer 3 when using expanded view for chat is unrelated to the memory problem.
Seeing as you have a 64bit Windows system, give the 64bit alpha build of Firestorm a try. For details see http://wiki.phoenixviewer.com/fs_firestorm-64-bit
-
Firestorm 4.4.2 release and 4.5.1 beta are not affected by this bug no.
The internal builds of Firestorm were affected by it but unless you are self compiling, you wont have seen it. It is now fixed internally.
Firestorm does have the compact and expanded view options but they have different names.
Preferences -> Chat -> General -> Use V1 style chat headers
When this option is enabled, thats "compact view".
When this option is disabled, thats "Expanded view".
-
-
There is a fix for this in the pipeline.
See http://wiki.secondlife.com/wiki/Beta_Server_Office_Hours/Minutes/2013-11-07
Maestro Linden: another change in the upcoming maintenance RC is a feature request that came from this group a few weeks agoMaestro Linden: that objects rezzed by sat-upon objects should have a fresh autoreturn and temp-on-rez timerMaestro Linden: so that they'll last the full ~60 seconds (for temporary) or parcel autoreturn timeMaestro Linden: we've also got the odd edge case where a temp-on-rez attachment rezzes stuff
-
The poor performance issue when the conversation window is open on that viewer build is a known bug.
It appears to happen when you have chat mode set to "Expanded view". If you change chat mode to "Compact view" you should find you no longer get the performance drop when focussed on a chat tab with many lines of chat history.
Regarding your login memory useage of 1.1GB, this is quite high unless you have a large inventory. The larger your inventory, the higher your memory useage will be right from login (unless inventory cache is empty).
For example, my alt has about 7k of inventory and the viewer will be using about 450Mb just after login. If I login my main, which has over 100k of inventory, the same viewer with same settings in same locatyion will be using around 1 gig at login
-
What viewer are you using?
There are no known crashes reported for this as far as I know. I am able to wear rigged mesh with normal and spec maps added on Viewer 3 and internal builds of Firestorm with materials support added.
Does this happen with all rigged mesh or just certain ones?
If you can reproduce this crash on Viewer 3 you should file a JIRA issue.
Make sure to give all your system information from Help -> About Secondlife.
Reproduce your crash and then immediately, before relaunching the viewer, zip up your entire logs folder and attach it to your JIRA issue using More Actions -> Attach files.
Instructions on where to find your logs folder on Viewer 3 can be found HERE.
If you happen to be using a TPV with materials support and mesh deformer support then there is a known crash when wearing deformable rigged mesh with normal & spec maps but if thats the case then you would need to contact the TPV developers.
-
I wonder if you are seeing BUG-4196 - Temp prims rezzed by temp vehicles/NPV's/apps cannot rez temp prims after being sat on for more than a minute.
This issue reports:
After the recent change that makes rezzed prims inherit the rezzer's autoreturn time, temp prims rezzed by sat on temp rezzers, die instantly once the sitter has sat on the rezzer for more than 60 seconds.
This is having a impact on temp combat vehicles or NPV's or other temp sat on rezzing apps.
Please either make sat on temp prims not count down their autoreturn timers or make temp prims not inherit the rezzer's auotreturn time.
-
-
See FIRE-11852 - [bUG-3472] [MAINT-2957] Texture thrashing since SSA - TEXTURES REBAKING AFTER BEING FULLY REZZED
-
Elyse, if you have another session where you see yourself or other avatars stuck grey and you are using the Firestorm test build containing Monty's fix, please can you stay logged in at least 20 mins around other avatars if possible, and then logout and immediately, before relaunching the viewer, zip up your entire logs folder and attach it to FIRE-11448 using More Actions -> Attach files.
Instructions where to find your logs folder on Firestorm can be found HERE
Thanks!
-
Qie Niangao wrote:What's got me puzzled, though, is why others aren't seeing this. For me it happens once I cam around anywhere with enough Mesh.
Oh, others are seeing it.
Since the Viewers updated to the SSA code a lot of people are suffering out of memory crashes, particularly when around a lot of other avatars and camming around a lot.
The log snippet you posted shows the standard lines from an out of memory crash.
This is affecting all OS.
-
If anyone having this problem would like to test a build of Firestorm containing Monty's proposed fix, please drop me an IM inworld and tell me what operating system you are using.
Bunderwahl, I already left you an IM.
Those of you testing, please leave feedback for Monty on this thread for how the fix works for you.
-
The entire screen getting texture glitches when window size is changed is a known bug since the Cocoa changes on Mac 10.6.8.
Its listed as a known issue in the release notes: MAINT-3135[c] Cocoa Viewer: Mac: Maximizing the viewer leaves garbage on the screen (10.6 only).
As far as I know, a fix is pending.
-
-
2
-
-
Both those images look like shaders are disabled.
Can you paste in all your system information from Help -> About Secondlife? (From the top menu bar).
-
You can't now use the Firestorm gpu_table from the 4.4.2 Firestorm release in a build of Viewer 3 that contains the fix for STORM-1552.
The STORM-1552 fix will cause Viewer 3 to see the Firestorm gpu_table as invalid (correctly so).Workarounds:
- Edit the gpu_table from Firestorm 4.4.2 and add this line as the very top line:
//GPU_TABLE - that token on line 1 tags this as a gpu table file or - Use this version of the gpu_table: https://dl.dropboxusercontent.com/u/43361170/gpu_table.zip
- Edit the gpu_table from Firestorm 4.4.2 and add this line as the very top line:
-
Go to Avatar -> Preferences -> Move & View -> Firestorm -> Allow camera to move without constraints through prims -> Tick it -> Relog.
-
Viewer 3 (the official default viewer) crashes at login with anything newer then the 13.4 catalyst drivers. A fix for this is in the pipeline, but not released yet.
You can either rollback to the 13.4 catalyst or try Firestorm Viewer which has this crash fixed.
-
Can you paste in all your system information from Help (in the top menu bar) -> About Exodus.
Can you attach a photo showing an example of the "black plague"
Can you reproduce the same problem on the latest release of Viewer 3?
-
Sloan, you were given a special test build of Firestorm by myself (on Aug 25th) and a special build of Viewer 3 by a Linden to test and asked to provide feedback.
You never replied to either with logs and the other results you were asked for over a month ago.
If you would still like help in resolving this issue then please update BUG-1872 with the information requested.
Complaining (again) without providing feedback when asked won't get you fixed. :smileymad:
-
Tonky, can you attach logs to your JIRA issue at BUG-4042 immediately after logging out of the next session you where you experience grey avatars.
If you happen to be on Viewer 3 when this happens, then this page tells you where to find your Viewer 3 logs folder: http://community.secondlife.com/t5/English-Knowledge-Base/How-to-report-a-bug/ta-p/733545#Section_.3
If you are on Firestorm (I hope you meant Firestorm and not Phoenix, Phoenix is not serverside appearance compatible and grey avatars is expected behaviour
) then this page tells you where to find the Firestorm logs folder: http://wiki.phoenixviewer.com/file_a_jira#how_to_give_us_your_logsLogs from Viewer 3 would be prefered by the Lindens if you can do that but either viewer's logs should show the problem.
) then this page tells you where to find the Firestorm logs folder: 
Facebook
Instagram
Twitter
YouTube
Flickr
Where do these 鋰㰀暜藐 come from?
in Second Life Viewer
Posted
Its a Mac specific bug.
See STORM-1976 - When pasting from a web browser or some other applications into the viewer, some garbage characters are appended