Whirly Fizzle

Hmm it should be fixed on Firestorm 4.7.5. Did you install & run any other V3 based viewers or older Firestorm versions on that system? If so, then the you will still have the same problem with the global Nvidia profile. JIRA issues for reference: FIRE-14626 - Firestorm should add itself to the nVidia Program settings list on installation FIRE-16667 - Running Firestorm 4.7.1.45325 causes issues with nvidia drivers BUG-9906 - Second Life messing up NVIDIA drivers

That error will happen if you are rescaling mesh & you don't have enough LI left on the land to hold the mesh at the larger size. A lot of mesh will increase in LI when you make it larger.

CadenzaInVivace wrote: Gotta love how the JIRA's status is "need more info". What more "info" is needed? "Unable to join or leave groups" is too hard for LL to understand? The JIRA is set at "Needs more info" so anyone can comment on it. That JIRA issue is actually a duplicate of an internal JIRA issue but if it was closed as a duplicate or accepted or set to "Info provided" then comments would be locked for everyone apart from the filer & Lindens.

It may be this old bug: https://jira.secondlife.com/browse/VWR-16694 This bug is fixed in fixed in Firestorm - details at http://jira.phoenixviewer.com/browse/FIRE-3657

It's likely nothing wrong with your region as such. There have been widespread problems for days now with joining/leaving groups, changing group tags, teleports timing out, profiles being slow to load etc etc. Restarting the region doesn't help at all - it's grid wide. For details see https://jira.secondlife.com/browse/BUG-10869

I agree with Rolig, it's almost certainly going to be the Firestorm bridge. Are you using an old version of Firestorm? If so you should update to the latest version and the problem will go away. For further details, see this post.

It's a known problem & not fixed yet. For details see https://jira.secondlife.com/browse/BUG-10869

Duplicate chat postings like that are usually caused by some kind of network issue. It's strange in your case you only seem to have the problem on certain regions though. Do you have any alt accounts? If so, do the alts suffer from the same problem & only on the same regions? Do you have any other computers connected to the same home network? If so, does the problem reproduce on those other systems? Have you tried connecting wirelessly instead of wired or replacing the cable? Possibly the cable is faulty?

There are widespread problems currently with a lot of group functions - see https://jira.secondlife.com/browse/BUG-10869

On Firestorm 4.7.5 with Intel HD 2000 graphics on Windows 10, you will only be able to use the 32bit version of the viewer. Once the 32bit version is installed, you will need to apply the "intel fix". For full instructions see http://wiki.phoenixviewer.com/fs_intel_fix_32bit

On older versions of Firestorm, click the "Cancel" button.

I'm all set up :smileyvery-happy:

Does this camera bounce happen in all locations? Have you by any chance just got a new house or a large sculpted or mesh build on your land & this only happens around that area? The LL viewer has a horrible "feature" that you cannot disable which causes the camera view to be bumped by nearby objects. This effect can be really severe around certain sculpted or mesh builds. This camera bumping annoyance isn't new on the LL viewer though, so maybe you are having a different problem. Most (all?) TPVs allow you to disable this effect. For example on Firestorm, go to Avatar -> Preferences -> Move & View -> View -> Allow the camera to move without constraint through prims. This setting needs to be ticked to stop the camera view being pushed by objects.

There have been intermittent problems with joining & leaving groups and long delays with changing group tags over the last few days. Please see https://jira.secondlife.com/browse/BUG-10869

Avi Arrow wrote: As it is now: Instead of "Avi Arrow...(8640)" we now have "(8640 min. remaning) Avi Arr..." List is now sorted by least amount of time remaing and not alphabetically by resident name. Upon first viewing, list now needs to be loaded twice for time to even display at all. 3 is a bug. JIRA issues filed for that here: LL JIRA: https://jira.secondlife.com/browse/BUG-10831 Firestorm JIRA: http://jira.phoenixviewer.com/browse/FIRE-17408

Yes that change is intended. Linden lab actually made the change in their viewer and we picked up that change in Firestorm. The behaviour change was requested here: https://jira.secondlife.com/browse/BUG-8261 If you would to request that this new behaviour is optional on Firestorm, please file an improvement request JIRA issue

There was this problem on an earlier server build which had the upload restrictions, but it seems to be fixed now: https://jira.secondlife.com/browse/BUG-10667

As far as I know the new serveride upload validating only blocks mesh rigged to unknown joints or animations referencing unknown joints. Uploading mesh rigged to attachment points still works just fine. The error message shown the OP's image is a different message to the one you get on the LL viewer when attempting to upload a mesh rigged to an unknown joint though, so I'm not sure. Seems it's getting upset because your joint is called Torso and not mTorso maybe?

Shadows are viewer side, not server. I see shadows on Demondrille region just fine. However in the SW of the region there is a large platform in the sky covering about 1/4 of the region and this is casting that whole quadrant with a huge shadow. Is that maybe the problem?

Daniela Wetherby wrote: Hi guys, hopefully this is correct section for this, this is my first time utilizing Second Life's forums. So, to start off my topic, I just had upgraded to a brand new AMD GPU (mere days ago). A Sapphire Radeon Nitro R9 380, up from an old Nvidia 750 Ti. Now, previously with my NVidia card, I had never encountered this graphical error (imgur link to example) before. I'm not sure whether or not to call it "artefacting" or "pixelation", but it shows up in that one static position at all times. Originally, I had thought it was just un-updated drivers (I only got this card around a week ago), but updating to the latest drivers still didn't fix it. Googling hadn't provided much in the way of a solution, and I had kind of washed my hands with it. However, I decided to fiddle with my graphics settings to try and take prettier snapshots, and lo and behold, I found a solution. Under the "General" tab of Graphics, disable Bump mapping and shiny and that got rid of the artefacting and returned it to normal, thankfully. http://i.imgur.com/VcuS8gu.jpg This being an after snapshot with it disabled. I'm not sure if I wrote this out correctly but, I'm hoping it'll help someone with the same issue. For posterity: My setup Mobo: Gigabyte Tech 990FXA-UD3 CPU: AMD FX-8350 GPU: Sapphire Radeon Nitro R9 380 OS: Windows 10 Viewer: Firestorm 64 4.7.5f os (I also replicated the graphical error using Black Dragon Viewer) There have been quite a few people having this problem and it appears to be specific to the AMD R series cards. It reproduces on all viewers on affected systems, even the V1 based ones like Singularity. The only reason disabling Bump mapping & shiny "fixes" it is because this also disables Advanced Lighting model. Disabling that setting really isn't a fix, it means you are locked down to low graphics quality settings - no materials or shadows. The latest AMD drivers do not fix the problem, rolling back to earlier drivers does not fix the problem. For details see http://jira.phoenixviewer.com/browse/FIRE-16829 This really needs filing as a bug report with AMD by someone on an affected system.

4.7.5.47888 was an old nightly build & still had a lot of unfixed bugs. Firestorm 4.7.5.47975 is the current release build.

Does that mesh import okay on Firestorm 4.7.5? The old Firestorm beta (4.7.1) was released in May & does not have the new importer code.

I tried to reproduce this and so far I can't. I'm seeing the same behaviour as Darius - it's working as expected and the updated item is being redelivered to my alt who purchased the item before I made the update.

Chic Aeon wrote: I read that there were lots of issues with rigged mesh and the new version of Firestorm (and you would think the code that was adopted from LL? so perhaps before for some folks). I didn't update and I don't plan to. Too many people having issues. If you mean new bugs with rendering some rigged mesh correctly then yeah, there's a nasty new bug on Firestorm 4.7.5 which will cause some rigged mesh (ones using zero weighting) to render with spiky bits sticking out of it. This isn't specific to Firestorm 4.7.5 though, the same bug is in the current LL viewer - see https://jira.secondlife.com/browse/BUG-10747 If you mean problems uploading meshes on Firestorm 4.7.5 with the new importer code then so far we don't know of any bugs which don't also occur on the current LL viewer . The main 3 problems (only one of which is actually a bug) tripping people up on 4.7.5/any viewer with the new importer code are: BUG-10434 - Unable to texture meshes with spaces in the material names on the Importer viewer.This one's a bug & caused by materials with spaces in the name getting truncated so you may end up with several materials having the same name, which will mess up texturing those meshes. Ref: BUG-10326 - Latest Importer viewer buggy on uploading, and retaining material group order Material names are now sorted alphabetically when importing a mesh model and may not retain the order they had in the original model imported with the old importer. This is expected behaviour and If material order is important to your model, you must name them accordingly. Not following the new naming convention for LOD files. If anyone spots a bug with the mesh importer that's specific to Firestorm on 4.7.5 only, please file a Firestorm JIRA issue If the bug also reproduces on the current LL viewer, then it's best to file it straight on the LL JIRA

iOthman wrote: No they don't have spaces. Must be the new update. AFTER reading this post, Reverting to the previous viewer version solved the problem. If you think it's a bug with the new importer code, can you file a JIRA issue for it? If it doesn't get reported it won't get fixed. If the bug also repoduces on the current LL viewer, file a LL JIRA issue. If it only reproduces on Firestorm, can you file a Firestorm JIRA issue. You'll need to attach a dae that reproduces the problem to the JIRA. Ta!