Jump to content

Whirly Fizzle

Advisor
  • Posts

    4,719
  • Joined

  • Last visited

Everything posted by Whirly Fizzle

  1. Grumpity Linden wrote: Whirly and animorf, you'll notice you now have same number of items in beta and production Yep, confirmed those two stores are fixed. Thanks!
  2. Do your material names have spaces? Theres's a bug where material names with spaces get truncated and it can cause your symptoms when texturing - see https://jira.secondlife.com/browse/BUG-10434
  3. Arwen Serpente wrote: - For some reason, the "beta" website only shows 585 of my products when I use the "my store" drop down from "My Marketplace", or "visit this store" from a listing. This may or may not have anything to do with the beta search engine, but it's rather annoying to have 588 products listed and active, and have 3 go missing in the Beta. Where are they? This is happening to a lot of stores, though not all. I filed a bug report for that here: BUG-10769 - [sLM Beta Search] Some store pages have missing listings when using beta search
  4. Try for example... candle* NOT mesh or candle* AND mesh
  5. You may not actually be doing anything wrong. There's a bug which started with the attachment fixes in the 3.7.25 which causes an avatar wearing joint rigged mesh to shoot up in the air, or off to the side or even totally underground when you edit at attachment on the avatar or take off an attachment. This video shows it happening. See https://jira.secondlife.com/browse/BUG-8616 There's actually 2 seperate bugs lumped into that one JIRA report - for your problem, see "Steps To Reproduce - Part 2" and the comment section.
  6. Ahhh thanks. I just checked and BUG-10170 is actually listed as fixed in a later version of the importer viewer. MAINT-5601 [importer-RC] Physics model not previewed, physics model not applied to mesh on upload - is a resolved issue in http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/3.8.4.305119 Maybe it was never fixed for the case of meshes with more then 8 materials though? Worth filing a new JIRA issue for anyway.
  7. Drongle McMahon wrote: *Tested it - yes, it's alphabetical now. Is it in Firestorm too? Yes, Firestorm 4.7.5 behaves the same way as the LL viewer.
  8. Aquila Kytori wrote: Hi I had wondered, if a mesh object with more than 8 materials got split automatically into 2 or more separate objects, how the Uploader would handle the physics and assumed it couldn’t know how to recreate the physics properly and so be unusable. This morning after reading this thread I thought I should try anyhow. I created 10 posts in Blender, 0.4 x 0.4 x 5m high with 2 meters spacings . Each was assigned its own material. The Physics mesh was the same posts but with the end faces deleted: When it came to uploading the Physics mesh was not showing in the preview window: when rezzed and edited t ochange the Physics Shape type thers was no prim option: So the uploader solves the problem of physics for automatically split objects by simply ignoring the Physics mesh and uses the default convex hull when the objects are rezzed ! There's a bug report for that at https://jira.secondlife.com/browse/BUG-10170
  9. Windows 10 32bit, TH2. Edge browser. Ewwwwwww! Man thats really broken, yes, reproduces.
  10. Prokofy Neva wrote: Firestorm is a particular problem in my view because it enables people using it to return group-set prims when they were not granted that power in a Second Life group -- a function they could not perform on a regular viewer made by Linden Lab. That's a serious exploit and serious undermining of the rules/technicalities of Second Life, but LL turns a blind eye to that for reasons I can surmise but which are never stated. Would that happen to be that serious expected behaviour exploit on https://jira.secondlife.com/browse/SVC-121 ?
  11. Do you have f.lux installed or any other custom colour profile software? Those are known to cause the symptoms you described when quitting any SL viewer. See http://jira.phoenixviewer.com/browse/FIRE-12561
  12. I suspect it may be because the viewer forces Max Core Clock after a system reboot. This is actually done on purpose but there have been quite a few complaints about this behaviour. This is the code commit which added this behaviour: https://bitbucket.org/lindenlab/viewer-release/commits/6a2054a7cf5b83220f6f0342af51b3d0d0ae25cd MAINT-1841 Use NVAPI to force NVIDIA GPU power management mode to prefer max performance Relevant JIRA issues & forum threads: BUG-9906 - Second Life messing up NVIDIA drivers https://community.secondlife.com/t5/General-Second-Life-Tech/Issue-with-SL-taking-over-my-Driver/m-p/2878074 https://community.secondlife.com/t5/General-Second-Life-Tech/Second-Life-is-Messing-with-Nvidia-s-Drivers/m-p/2969993 https://community.secondlife.com/t5/Second-Life-Viewer/Second-Life-and-nvidia-drivers/m-p/2958336 FIRE-16667 - Running Firestorm 4.7.1.45325 causes issues with nvidia drivers (now fixed on Firestorm)
  13. Empty groups list, friends list names stuck on "Loading...", inability to initiate an IM & inventory failing to fetch are usually symptoms of either a sick region which has capability failure or a connection problem with DNS. Try logging directly into a different region & see if everything is back to normal. If you only have the problems when logging into a certain region then that region most likely has caps fail, everyone else will also have the same problem who logs in there & the region needs to be restarted.
  14. I just wanted to make a note here about what's going to happen on the RC regions after the roll to 15.11.11.307649 for Firestorm & CtrlAltStudio users on OLD viewer versions. This will affect any viewer forked from an old Firestorm codebase. The only version of Firestorm viewer affected is Firestorm 4.4.2 (34167). The other affected versions are already blocked from login. Firestorm 4.6.9, 4.7.1 and 4.7.3 are not affected. The Linden Lab viewer is not affected, even old versions. One of the changes in the RC is "Back end enforcement of attachment point ids". This will break the Firestorm Bridge attachment on Firestorm 4.4.2 on the RC regions because it uses a non-standard "Bridge" attachment point. This is expected behaviour and it's not going to be fixed. The fix is to update your viewer to the latest Firestorm release. If you do not want to update your viewer, you will need to disable the Bridge and keep it disabled. On Firestorm 4.4.2, go to Avatar -> Preferences -> Firestorm -> General -> Untick "Enable LSL-Client bridge" -> Apply -> OK and detach the Bridge attachment. Anyone who logs into an RC region on Firestorm 4.4.2 with the Bridge enabled will be "rocked". The bridge attachment will fail to finish creating and you will be left wearing the medium round rock from the Library - it's not a good look :smileywink:
  15. Willow Wilder wrote: A mental health day is still being considered. :matte-motes-smile: Every day for support is a mental health day :matte-motes-dead:
  16. I want to post about some HTTP issues I'm having... ...but I'm feeling kinda insecure about it...
  17. Ayesha Askham wrote: It's not as if Whirly goes around prophesying the falling of the sky, now is it? :smileysurprised: I use protection...
  18. That last one is pretty common. See https://jira.secondlife.com/browse/BUG-9066 If you are getting all these error messages frequently, plus frequent TP disconnects & clothing slow to change, it does suggest a connection problem. It could also be a poorly region you are hanging out on though so see if you have the same problems on other regions first before you start banging on your connection.
  19. Yeah, it's an odd one. I doubt it affects all system with an AMD R series card (as you just verified too) because there would have been more screams. What's "special" about those affected systems, I really have no idea.
  20. There is one known problem that's specific to the AMD R series of cards and it's a bit of a deal breaker. The bug affects all viewers on systems that suffer from it. Details: http://jira.phoenixviewer.com/browse/FIRE-16829
  21. Marketplace error message like that are "normal" since the move over to VMM. If you only see those errors very occasionally, it's nothing to worry about. You'll most often see them just after login or after TP into a new region. Causes can be backend problems with the Marketplace (which looks like your case), entering a sick region or connection problems. Ref: http://jira.phoenixviewer.com/browse/FIRE-16599
  22. Caleb, on 15.11.07.307443 which is due to go to the RC's on Wednesday, most of my animations AND a lot of the official BVH animations from http://static-secondlife-com.s3.amazonaws.com/downloads/avatar/bvh_files.zip are refusing to upload - they are giving an "Upload_InvalidAsset" - "references unknown joints" error on upload.  I filed a JIRA issue: https://jira.secondlife.com/browse/BUG-10667
  23. Looks like it's finally fixed! See Simon Linden's comment on https://jira.secondlife.com/browse/BUG-10643 Simon Linden added a comment - 09/Nov/15 6:46 PM - edited We just rolled out a new update mechanism - please log into the Aditi beta grid using your old password. Overnight your inventory should be merged from the main grid. This will happen after each day you log onto the beta grid, and new additions on your main inventory will be available on the beta grid the following day. Please let us know if that doesn't work.
  24. If you are crashing when trying to save a snapshot to disk, it's probably the known file picker crash. Does this help? http://wiki.phoenixviewer.com/mac_crash_upload
×
×
  • Create New...