Jump to content

HunniHope

Resident
  • Posts

    287
  • Joined

  • Last visited

Everything posted by HunniHope

  1. probably not such a good idea to post your email address. Make sure your settings are correct and that you have enabled to option to receive offline IM's to email on your dashboard. Test it by logging out and having someone send a group notice to a group which you are still set to receive notices in. After that, if still no go, file a support ticket.
  2. make sure you've followed all the steps for changing the card as per the KB also on that page you can double check that the replacement card is still one of the accepted card types. There are also links on that page for contacting billing support by phone and for filing a support ticket which is what you will need to do if still unsuccessful
  3. well seeing as today is day 32 when starting at Dec 1st then yes it's likely you can pretty much say ta-ta to the 1st Dec transactions. The workaround is to do what Pamela did last year and sign up for a months premium so that you get a 3 month history allowance
  4. was in the process of filing one when i spotted this so here it is if you wanna keep an eye out https://jira.secondlife.com/browse/BUG-226039 Keep an eye on grid status tomorrow (2nd). Last year shows they got it fixed when they returned on the 2nd FWIW, jiras are pretty easy to file, and fairly straightforward and self explanatory as you go through each field. the KB covers it in more detail
  5. If your dev kit is official maitreya and issued to you after dec 2016 (it changed sometime between dec '15 & dec '16) then there should be a skirt in the blend file, along with the loose body & body masters, feet & hands. If you don't have those extras or your kit is older than dec 2016 then contact the CSR inworld for an updated kit. it's also possible you may have deleted the skirt and saved the blend file thereby eliminating that skirt, so download and unzip a fresh copy from your original email to check. You copy weights at the time of binding by choosing the appropriate option from the drop-down. For dev kits which provide the weighted body and parts you choose meshes as the option before you bind. More detailed instructions at https://avastar.guru/avastar-2/reference/attachments/binding-meshes/. There's a whole section in the nav menu on the right for "Skinning & Weighting" which is broken down for different stages, from binding, to inspecting & editing weights
  6. the "failed to find [item] in database" message isn't viewer side, fixes are touch-n-go, you might get lucky, you might not. Firestorm have prepped a useful page to help troubleshoot through a few possible causes and should be useful regardless of which viewer you are using. If in doubt, or it happens again, or repeatedly, file a support ticket to LL https://wiki.phoenixviewer.com/failed_to_find_in_database
  7. if it's of any help this top & skirt is on the Maitreya dev kit, shown using body fat slider at 50 and breast slider to 100 if you're using the official maitreya dev kit then there is a skirt included in the blend file that you can use for weight copy at the time of binding (this is using blender & avastar, for other programmes you would need to do the equivalent process)
  8. from the KB page "Note that while it is still possible to sell a limited quantity of copiable items using the appropriate listing field" that sentence in and of itself says to me that Limited Quantity means Limited Quantity not no-Copy
  9. because it's rigged mesh, changing scale at the mesh upload window will only affect the size of the mesh when rezzed because when worn, rigged mesh will spring back to the size it was made/rigged/exported at, so if you are making it too big in Maya, then it's going to be too big when worn in SL no matter what you try to do to the scale in the uploader
  10. No-one can really say if something has a value to you, only to themselves. I don't know that particular head but I know the brand and it's reputation. In my opinion a well made Bento Mesh head with detailed, fully functioning HUD and lots of features is very much worth 5k. You need to ask yourself if its worth it you. Get the demo and work out if you can live with a head with little to no features or function for little more than a buck. Or do you really like the full HUD and think you would make the most of it, then ask yourself if its worth the saving of 1200L whilst you can
  11. perhaps the catalogue has a returns policy, something along the lines of satisfaction guaranteed or your money back, or perhaps free returns within 30 days, or you might just find you need to pay the shipping cost. Check the small print in case it needs to be in un-used condition and with original packaging
  12. just becasue i wanna annoy with christmassy sorta pics when we really are not sick of seeing christmas stuff in RL for the past 3 months already ..........my view of SL, and at only 64m cos frankly if i need to see beyond that, i know how to move my cam without moving my avi (yes avi is lazy but fingers sometimes get nosey)
  13. I tend to use several filters along with windlight settings and a camera hud tool, saving several versions of the same image and then editing and combining in Photoshop for different effects
  14. my eyes are precious, i've spent far too long customising them to give them away ... but you have given me an idea 💡
  15. on several occasions now after a brief exchange of general pleasantries I've been hit with "I'm lagging here can we go back o my place to chat" and it usually results in a conversation not too unlike this .. HIM: I'm lagging, can we go back to my place to chat ME: well, i'm not lagging, and i like it here, and the beauty of IM's mean we can be anywhere on the grid and still talk. Isn't that magic? HIM: but I like to look into your eyes when we chat ME: that's a shame, I just detached mine
  16. In addition to Rolig's reply above, those yellow triangles, are usually an indication of an issue & having a "good connection" doesn't necessarily mean its not gone bad. Even though you are not on the Firestorm viewer currently, the following page should help to troubleshoot these triangles you are seeing when logging in https://wiki.phoenixviewer.com/mesh_issues#pyramids_triangles_ducks
  17. secondly, to rig from t-pose to a-pose you need to be using the correct settings in Avastar, and you can find instruction on the on their website https://avastar.guru/workflows/bind-pose/ If you are working with a dev kit then it is not recommended that you do not alter the rest pose and instead just keep to the default pose that the kit is supplied in. Firstly. on the avastar website there is also a whole reference section related to rigging, and editing & inspecting weights https://avastar.guru/avastar-2/reference/attachments/ Yes some things get renamed, re-worded, or moved around in Avastar. It's not common practise, it is done when necessary or when improving or implementing new features or even when needed in the process of fixing a bug. The basics of rigging haven't changed much over time, and some videos are still very useful and if the layout is different in that older version and panels are named slightly different then you can search for the name, phrase or terminology on the website and usually get the answer you need which tells you what's where. There is also a very useful section related to the avastar toolshelf itself breaking down the different panels and what they cover https://avastar.guru/help/toolshelf You also have use of the inworld "Blender Avastar" support group and also the new Avastar discord server should you not be able to be inworld while working
×
×
  • Create New...