Jump to content

Whirly Fizzle

Advisor
  • Posts

    4,719
  • Joined

  • Last visited

Everything posted by Whirly Fizzle

  1. Best thing to do for now is to disable media auto-play. This will stop the viewer automatically loading that web prim in your neighbours house. Go to Me -> Preferences -> Sound & Media -> Untick "Allow media to auto-play"
  2. Hmmm there is a media prim close to your house pointing to the URL http://crashsafari.com/0 . That URL crashes Firefox when opened too.
  3. Which viewer version are you using? In the top menu bar of the viewer, go to Help -> About Second Life, click the "Copy to clipboard" button & paste all your system information into a comment here. I suspect you are using the Http-update RC. There was a bug similar to this filed at BUG-10616 but it's supposed to be fixed...
  4. Hmmm sounds like all your viewer settings are getting wiped or corrupted in such a way that the viewer cannot read the settings files on launch. It's hard to say what could be causing that without seeing your viewer from a session where the settings were wiped. In the top menu bar of the viewer, go to Help -> About Second Life/Viewer name, click the "Copy to clipboard" button & paste all your system information into a comment here. Have you been using any kind of "system clean up" type software that may have deleted your viewer settings files?
  5. That error can happen on install if you have a stuck win_crash_logger.exe process left over from an old viewer session. You may also have other stuck processes so easiest way to fix that is to reboot your computer, do not launch an SL viewer after reboot, download the latest release installer from https://secondlife.com/support/downloads/ , run the installer & it should be fine. Does that help?
  6. It's a bug that happens on any viewer that has the CEF changes. See BUG-10415 - [Valhalla] profiles and marketplace are asking for a login each session If you tick the "Remember me on this computer" checkbox when you sign in, the viewer should auto login to the profiles each session. However, this is really buggy & will often fail to work. Nothing you can do about this until the bug gets fixed in the viewer code I'm afraid.
  7. Hmm "llceflib_host.exe has stopped working" sounds like that plugin is crashing. Which viewer are you using? In the top menu bar of the viewer, go to Help -> About Second Life/viewer name, copy all your system information given there & paste it into a reply here. Are you doing anything in particular when you see that error message? Are you hanging around in places where there is lots of media content? Does this only happen in a certain location?
  8. For Firestorm users, all users, not specificically creators: ~ 1% use Linux. ~ 10% use Mac The rest are Windows.
  9. Yeah the problem is Webroot. You can see more details about the Webroot problem on these JIRA issues. LL JIRA: BUG-11314 - Graphical Errors - Webroot + Pipelining incompatibility Firestorm JIRA: FIRE-17661 - HttpPipelining - Webroot Crash with fault error ntdll.dll mesh fails to render, texture corruption Izenagi wrote: Is there any possible free Anti-virus softwares you could potentially recommend me to? And thank you so much for this help! I truly appreciate it! Avoid any of the antivirus software listed as a problem in the comments on BUG-8631 I use the free version of Avira antivirus on my Win 7 desktop & Win 10 laptop and that doesn't have any problems with Pipelining. Avast free is also fine, I use that on an older laptop. If you wish to keep using Webroot then you will be fine as long as you keep HttpPipelining set to FALSE in the viewers. Webroot does cause other problems with SL viewers though, most notably extreme slow loading of textures & mesh. If you have the business edition of Webroot, this can be fixed by whitelisting the viewers cache folder. The normal version of Webroot does not allow whitelisting by folder though and there is no way to fix the problem. Webroot is also known to break copy/paste between the viewer & other programs. Honestly, I would get rid of Webroot & switch to an antivirus that causes less problems with SL viewers. Webroot just really does not work well when you run any kind of "exotic" software on the system and it flags SL viewers as "exotic".
  10. Do you have an Intel Skylake processor & is the viewer using the integrated Intel HD 520 or 530 graphics? If so then it's likely you are seeing this bug: BUG-10819 - [intel HD Graphics 500 series] Screen flashes with certain graphics settings when any worn rigged mesh is in view textured with a diffuse texture set to alpha blending mode. Updating the Intel graphics drivers to the latest 20.19.15.4352 driver version will fix that problem. If that doesn't help, can you go to Help -> About Second Life / viewer name, copy all the system information given there & paste it here. Do you happen to be using Webroot antivirus software? If not, which Fireall & antivirus software are you using? Do you also see corrupted rainbow coloured textures or is the problem just exploding mesh?
  11. The forum is being stupid again & will not let me post my reply to you. So, here is a screenshot of the reply :smileymad:
  12. Are you currently using the Linden Lab Maintenance-RC viewer? If so, this viewer breaks invisiprims even more then they were already broken - they will render solid grey or black (depending on which invisiprim texture is used) when ALM is both enabled & disabled. If you go to Help -> About Second Life & the top line shows the viewer version Second Life 4.0.2 (312269), then this is the problem. JIRA issue for this bug: BUG-11562 - [MAINT-RC] Maintenance Viewer Breaks Content Using Invisiprims
  13. Hmm. I would need to see your viewer logs after reproducing the crash to have any idea what's going wrong. If you use Firestorm (I'm Firestorm support), file a Firestorm JIRA issue & reproduce the launch crash & attach your logs to the JIRA issue. Reference this forum thread if you file a JIRA issue so I know it's you. Alternatively, if you usually use Alchemy, file an Alchemy JIRA issue & attach your logs & one of their people will look at it.
  14. ObviousAltIsObvious wrote: seeing some old videos that Jelli posted, is the feature the one where you can edit your shape without going into the scarecrow pose and forcing the camera? Ahh good thought! Though on those videos it looks like there is an extra morphing effect when the shape is changed but it's hard to tell whether that was post processing effects added on the video.
  15. Huh! Thats pretty neat actually. I wasn't aware of that feature at all. I imagine it probably broke when serverside baking was added though. Did observers also see the shape morph effect or was it local on your screen only? Or could only other Imprudence viewers see it? How did it actually work? Are you just changing shapes normally on those videos and the viewer displays that morph effect?
  16. If you still cannot login to the beta grid after following Rolig's advice then file a support ticket with LL suport here: https://support.secondlife.com/create-case/ Aditi account & inventory syncing has been problematic recently & support should be able to fix this for you by doing a manual sync so you can login.
  17. Jelli Kohime wrote: As for what feature I need? The morph effect when switching body types. Imprudence is the only viewer I've found that still does that. I still have no idea what this feature is. Do you by any chance mean the ability to export the avatar shape to obj using the old "Meshes & Morphs" feature? On the old V1's this will be under Advanced -> Character -> Meshes And Morphs I know this feature broke on Phoenix viewer when mesh support was added. Possibly CoolVL Viewer or Singularity viewer still support this. If that is what you are trying to do then you can do similar on current viewers if you want to export your worn shape. You can import the exported shape into Avaster/Blender.
  18. According to Drongle's old bug at VWR-27992, which was moved to an internal project, so we can't see it, this bug only affects mesh with 3 or 4 materials, not 4 or 5 materials." "Thus it is the models with three or four materials that exhibit the unexpected behaviour while the otherts behave as expected." VWR-27992 can still be viewed HERE. Also more info on BUG-6287 - LOD Switch Distance bug? (also 3 materials). ChinRey's new JIRA issue: BUG-11561 - Mesh uploads have incorrectd switch points
  19. Huh I've never seen anyone getting that login error before. If I had to take a guess it would be that when your account was created it was locked to a certain estate because you signed up through a RegApi for an educational institution or you were under 16 years old when the account was created, and that estate the account was locked to has now gone. You need to contact Linden Lab support directly by submitting a support case form here https://support.secondlife.com/create-case/
  20. Have you tried the latest Nvidia driver? The 320 driver is a couple of years old now. The latest driver for your card appears to be 362.00 - http://www.geforce.com/drivers/results/99204 I'm currently running this driver on a Win 10 Optimus laptop with a GTX 960M & current viewers will run okay when using the Intel or Nvidia graphics. Having said that though, which viewers did you test on? There have been a few support cases now filed with Firestorm from users with Win 10 Optimus systems who can run the viewer just fine using the Intel graphics but the viewer crashes during detecting hardware when using the Nvidia graphics. All of their crash stacks show that the viewer is actually crashing in the Intel driver igd10iumd64.dll This particular crash is specific to 64bit viewer builds only - they crash on Firestorm 64bit, Alchemy 64bit & Singularity 64bit . They can run any 32bit viewer build just fine using the Nvidia graphics though. So if you have not tested a 32bit viewer, give that a try & see if it works.
  21. NJMike, do you have Nvidia Shadowplay enabled? If so, disable it. I suspect your crash is BUG-11530 - Viewer crashes in nvwgf2umx.dll or nvwgf2um.dll when Nvidia ShadowPlay is enabled when opening Help -> Report bug, Help -> About, & sometimes when detecting hardware during launch.
  22. Test reply - testing https://jira.secondlife.com/browse/BUG-11543
  23. It depends which viewer you are using. Some TPVs allow exporting of the group member list and some don't. I can only tell you how it works on Firestorm Viewer - Group members with the GP_MEMBER_VISIBLE_IN_DIR ability are allowed to export the member list, ie) only users who are publically visible in the member list, to non-members. In other words, those whose role has “Reveal Members” enabled.
  24. I suspect the viewer is using the integrated Intel graphics & that laptop likely has a Skylake processor. If so, you are likely being hit by https://jira.secondlife.com/browse/BUG-10819 Update the Intel graphics driver to the latest version, which has a fix for the flashing bug. Then you need to set the viewer to use the Nvidia card rather then the integrated graphics, If you right click the viewer shortcut, you should see an option to run using the high performance (Nvidia) graphics. If you dont see that option then enable it like this: http://acer--uk.custhelp.com/app/answers/detail/a_id/9073/~/assigning-a-graphics-card-to-an-application-with-nvidia-optimus That's an Acer forum but the method is the same for most optimus laptops. It's better however to just have the viewer to automatically run using the Nvidia card. This video explains how to set that: - follow the "Assigning graphics solution for an application" steps starting at 57s.
  25. It's generally a bad idea to have more then one antivirus software running at the same time. So yes, if McAffee is in use I would uninstall Webroot. Once Webroot is uninstalled, you should clear your viewer cache. You only need to do this once to get rid of all the corrupted textures that fetched with Webroot+Pipelining. On the LL viewer: Me -> Preferences -> Advanced -> Clear cache -> OK -> Restart the viewer. On Firestorm viewer: Avatar -> Preferences -> Network & Files -> Directories -> Clear Cache -> Apply -> OK -> Restart the viewer. Does this fix the problem?
×
×
  • Create New...