Jump to content

Whirly Fizzle

Advisor
  • Content Count

    4,092
  • Joined

  • Last visited

Everything posted by Whirly Fizzle

  1. Please see this thread for the new Aditi login problems.
  2. I can't login to Aditi either. I filed a bug report: BUG-227357 - [ADITI] Many people unable to login to Aditi for ~ 1 week
  3. Singularity need to merge in this fix: https://hg.phoenixviewer.com/phoenix-firestorm-lgpl/rev/5f073ce21cc1 You can work around the bug by using the shortcut CTRL+SHIFT+WINDOWS+B to reset the display adapter after closing the viewer.
  4. It sounds like your laptop may be overheating. Install GPU-Z from https://www.techpowerup.com/gpuz/ When your laptop hasn't been logged into SL for the last 30 mins, open GPU-Z & take a screenshot of the Sensors tab. Among other things, this will show the GPU temperature & fan speed. Keep GPU-Z running & launch Firestorm & login. Watch GPU-Z & see what happens to the GPU-Temperature. How high does it get before the laptop shuts down?
  5. While logged in on the 32bit version of Firestorm (which you say fixed the problem), go to Help -> About Firestorm, Click the "Copy to clipboard" button & paste all your system information here. Then reinstall the 64bit version of Firestorm (which you said has the problem) & paste your system information. It's possible that for some reason the 64bit FS version is detecting your available texture memory incorrectly. This can happen for various reasons. It's probably fixable too, but I need both system informations to see what your Texture Memory has been set at on each viewer version. Ta!
  6. If you're unhappy with this LL decision, I suggest you file a LL JIRA issue: https://jira.secondlife.com/secure/CreateIssue!default.jspa Be sure to give all the reasons that you don't agree with this change & request that LL revisit their decision. I would do this quickly though. Currently older viewers are still able to make use of "Disable Selected" & "Disable All". Reverting the viewer change is simple. However LL will soon block this feature serverside so it will break in older viewers too. Convincing LL to revert the serverside block will probably be more difficult.
  7. Reinstalling Firestorm should fix the problem. You could also set up SLURL Proxy This will allow you to choose which viewer is used to open SLURL links if you have multiple viewers installed.
  8. Grumpity answered this at the Town Hall. She confirmed the inactivity fee is monthly. Video set to the time she said this.
  9. Whirly Fizzle

    Froze

    We actually have this bug fixed in the new release of Firestorm: https://www.firestormviewer.org/os/ The cause of the freeze is wearing a jacket layer. If you login on the new Firestorm, take any worn jacket layers off. You'll then be able to log that account in on the LL viewer.
  10. If you login using a griefer/copybot/illegal viewer, it's quite possible that your IM conversations are sent to a 3rd party, along with your password & all manor of other information. Don't use griefer/copybot/illegal viewers
  11. Correct, it charges the parcel owner. If parcel is owned by an avatar, the L$ are taken from that avatar. If the parcel is owned by a group, the L$ can be taken from every member of the group who is in a role that has the "Pay group liabilities and receive group dividends" ability. So in a group where a lot of members are in a role with that ability, each avatar may not get charged L$ every week or you may only pay L$1-2 each week. The L$30 total for the week is taken (randomly?) from group members with that ability each week. Hope that makes sense!
  12. You could file an abuse report against your friend & explain that you think her account has been compromised. LL will check it out. It depends on what your friend is spamming in groups I guess. If her account is spamming phish links to a fake Marketplace page, she probably got phished herself & her account is now compromised. If you're a premium account you could use Live Chat to report it. If your friend is posting phish links then it's pretty certain others have abuse reported it already.
  13. Note that since UDP asset fetch was disabled a couple of weeks ago, that viewer will have major problems because it doesn't support asset-HTTP. Your avatar will never rez, you'll be unable to see any animations playing on yourself or other avatars, you'll be unable to hear any viewer sounds etc etc. Oz did say he was going to remove the download but he either changed his mind or forgot.
  14. Whirly Fizzle

    tiggy3

    Contact Linden Lab support, they can fix this: https://lindenlab.freshdesk.com/support/solutions/articles/31000131009-contact-support One cause of this problem happens if a Linden hijacked your account in a certain way for testing/fixing something. It happened to me once when my Aditi account was hijacked by LL & then released & it broke my ability to change password. Support fixed it quickly.
  15. Another TP disconnect JIRA: BUG-227332 - TP failure: logout and disconnect
  16. Got the dump thanks. Yours was a crash when entering the new region, rather then a disconnect. This crash should (I hope) be fixed in the next FS release with this fix we pulled in from LL: https://hg.phoenixviewer.com/phoenix-firestorm-lgpl/rev/6b753a247e1b This Octree crash has nothing to do with any server changes made by LL. STACK Operating system: Windows NT 10.0.17134 CPU: amd64 family 6 model 158 stepping 10 12 CPUs Crash reason: EXCEPTION_STACK_OVERFLOW Crash address: 0x7ffc745322ca Process uptime: not available Thread 0 (crashed) 0 msvcr120.dll + 0x22ca 1 msvcp120.dll + 0x3cdc5 2 msvcp120.dll + 0x3cf80 3 Firestorm-Releasex64.exe!LLMutex::trylock() [llmutex.cpp : 121 + 0xa] 4 Firestorm-Releasex64.exe!LLError::Log::out() [llerror.cpp : 1241 + 0x1a] 5 Firestorm-Releasex64.exe!LLOctreeNode<LLViewerOctreeEntry>::insert(LLViewerOctreeEntry *) [lloctree.h : 439 + 0xad] 6 Firestorm-Releasex64.exe!LLOctreeRoot<LLViewerOctreeEntry>::insert(LLViewerOctreeEntry *) [lloctree.h : 860 + 0xc] 7 Firestorm-Releasex64.exe!LLOctreeNode<LLViewerOctreeEntry>::insert(LLViewerOctreeEntry *) [lloctree.h : 449 + 0xc] 8 Firestorm-Releasex64.exe!LLOctreeRoot<LLViewerOctreeEntry>::insert(LLViewerOctreeEntry *) [lloctree.h : 860 + 0xc] 9 Firestorm-Releasex64.exe!LLOctreeNode<LLViewerOctreeEntry>::insert(LLViewerOctreeEntry *) [lloctree.h : 449 + 0xc] 10 Firestorm-Releasex64.exe!LLOctreeRoot<LLViewerOctreeEntry>::insert(LLViewerOctreeEntry *) [lloctree.h : 860 + 0xc] 11 Firestorm-Releasex64.exe!LLOctreeNode<LLViewerOctreeEntry>::insert(LLViewerOctreeEntry *) [lloctree.h : 449 + 0xc] 12 Firestorm-Releasex64.exe!LLOctreeRoot<LLViewerOctreeEntry>::insert(LLViewerOctreeEntry *) [lloctree.h : 860 + 0xc] 13 Firestorm-Releasex64.exe!LLOctreeNode<LLViewerOctreeEntry>::insert(LLViewerOctreeEntry *) [lloctree.h : 449 + 0xc] 14 Firestorm-Releasex64.exe!LLOctreeRoot<LLViewerOctreeEntry>::insert(LLViewerOctreeEntry *) [lloctree.h : 860 + 0xc] 15 Firestorm-Releasex64.exe!LLOctreeNode<LLViewerOctreeEntry>::insert(LLViewerOctreeEntry *) [lloctree.h : 449 + 0xc] 16 Firestorm-Releasex64.exe!LLOctreeRoot<LLViewerOctreeEntry>::insert(LLViewerOctreeEntry *) [lloctree.h : 860 + 0xc] 17 Firestorm-Releasex64.exe!LLOctreeNode<LLViewerOctreeEntry>::insert(LLViewerOctreeEntry *) [lloctree.h : 449 + 0xc] 18 Firestorm-Releasex64.exe!LLOctreeRoot<LLViewerOctreeEntry>::insert(LLViewerOctreeEntry *) [lloctree.h : 860 + 0xc] <SNIP Hundreds of line of the same octree barf> 786 Firestorm-Releasex64.exe!LLOctreeNode<LLViewerOctreeEntry>::insert(LLViewerOctreeEntry *) [lloctree.h : 449 + 0xc] 787 Firestorm-Releasex64.exe!LLOctreeNode<LLViewerOctreeEntry>::insert(LLViewerOctreeEntry *) [lloctree.h : 449 + 0xc] 788 Firestorm-Releasex64.exe!LLOctreeRoot<LLViewerOctreeEntry>::insert(LLViewerOctreeEntry *) [lloctree.h : 860 + 0xc] 789 Firestorm-Releasex64.exe!LLSpatialPartition::put(LLDrawable *,int) [llspatialpartition.cpp : 1005 + 0xe] 790 Firestorm-Releasex64.exe!LLSpatialPartition::move(LLDrawable *,LLSpatialGroup *,int) [llspatialpartition.cpp : 1077 + 0xe] 791 Firestorm-Releasex64.exe!LLDrawable::movePartition() [lldrawable.cpp : 783 + 0x1b] 792 Firestorm-Releasex64.exe!LLVOAvatar::idleUpdateMisc(bool) [llvoavatar.cpp : 2936 + 0x6] 793 Firestorm-Releasex64.exe!LLVOAvatar::idleUpdate(LLAgent &,double const &) [llvoavatar.cpp : 2674 + 0xd] 794 Firestorm-Releasex64.exe!LLViewerObjectList::update(LLAgent &) [llviewerobjectlist.cpp : 1063 + 0x10] 795 Firestorm-Releasex64.exe!LLAppViewer::idle() [llappviewer.cpp : 5688 + 0x13] 796 Firestorm-Releasex64.exe!LLAppViewer::doFrame() [llappviewer.cpp : 1694 + 0x8] 797 Firestorm-Releasex64.exe!LLAppViewer::frame() [llappviewer.cpp : 1563 + 0x5] 798 Firestorm-Releasex64.exe!WinMain [llappviewerwin32.cpp : 396 + 0x9] 799 Firestorm-Releasex64.exe!__tmainCRTStartup [crtexe.c : 618 + 0x15] 800 kernel32.dll + 0x14034 801 ntdll.dll + 0x73691 802 KERNELBASE.dll + 0xebc30
  17. That 4.88MB attachment limit seems to be per post, not per image. I've been bitten by that a few times too.
  18. If you can zip up that dump folder from the crashed session & send to me at whirly.fizzle at phoenixviewer dot com I can tell you why you crashed.
  19. Noone here is Linden paid staff or Linden unpaid staff unless they have the last name of Linden. ChinRey very kindly fixed the problem for you & provided the dae files, yet you still complain?
  20. The JIRA is BUG-227328 - Logoff by Teleport
  21. Those breaks in the mesh are going to be worse the higher the altitude you are at. Is your home higher then the store?
  22. As far as I'm aware, there is no limit to how many items you can blacklist. Though it really wouldn't surprise me if having an extremely large blacklist may cause problems. The blacklist has no serverside support & the blacklist is stored locally on your machine.
  23. No offense VirtualKitten, but you need to stop editing your JIRA issue with sly digs at the Lindens who triaged it. This is not the first time you have done this either. If you keep doing this, a Linden will just end up banning you from the JIRA.
  24. It's very likely nothing to worry about & not a bug. Every item you are currently wearing has a link created in your Current Outfit folder (COF) of your inventory. Each time you change outfit, the number of links in the COF folder will change, which will change the number of elements in your inventory total.
  25. That message will be automatically sent to all parcel owners on the region when an estate owner/estate manager unticks this option in estate settings.
×
×
  • Create New...