Jump to content

Chellynne Bailey

  • Content Count

  • Joined

  • Last visited

Community Reputation

113 Excellent

1 Follower

About Chellynne Bailey

  • Rank
    Advanced Member

Recent Profile Visitors

336 profile views
  1. As long as the meshes keep their Onion Layers this is how it will work yes. Appliers will continue to function for a long while simply because there's not much reason to immediately strip the layers off existing meshes. New meshes and Future updates of the meshes will likely have fewer layers, and eventually no layers, but I'm doubtful that will happen quickly, as it will take time for various texture creators to repackage things. It only takes one tattoo, makeup or skin that someone is particularly attached to for someone to NEED the layers. And people get REALLY attached to their Skins and Tattoos. ~\o/~ So I will be super surprised if Onion layers disappear overnight. That being said, if you have a mesh body, make sure you keep a boxed current version of it tucked away. Someone might get overzealous. ?‍♀️ And if you're a texture creator of any kind, make sure your stuff has Appliers + System Layers. At least until they listen to my Jira! -flails dramatically for attention before giving up and wandering off again-
  2. Congratulations. You're a normal person. I, however, cannot help but get distracted by IMs popping up. I also use an outside editor, but I'm still tabbing in and out testing the scripts frequently to make sure I'm on track and every time I tab in, I'm liable to get distracted by someone needing something they think is important >.>
  3. Have one. It's not practical for most things I do. I need access to my giant inventory of meshes and tools I've built for myself. Get LL to change the permissions system so I can hand myself all my tools and scripts in one fell swoop without having to change all the nested perms... then it'll sorta be viable.
  4. I DO have a building alt I use for larger projects, but because of the nature of the work I do, it's only practical a small fraction of the time. I also have a customer support person. That helps a great deal, but people still IM me even though she's listed in my profile and a million other places. And there are some things they HAVE to come to talk to me about. It's nothing a CSR could handle. So I don't BLAME them.. I just need to be able to ignore them for a couple hours at a time...
  5. Chellynne Bailey

    Work Viewer

    I need a new viewer for scripting. I love my customers and clients, but it's utterly impossible to get anything substantial done when I'm constantly getting IMs. I finally said enough this week and started using "Unavailable" during my aloted "get ***** done" times, thinking it'd keep me from seeing incoming messages and distracting me..... annddd I still get messages. -.- (Like srsly, whats the difference between this and autoresponse if you can see them?) So, does anyone know a good work viewer that will actually let you turn off incoming messages and isn't a major pain to do scripting work in?
  6. This is not a recent thing. This has been a requirement of the system since the beginning. If you see an Omega Skin applier that doesn't do this, they're doing it wrong and should be sent a notecard letting them know they goofed. (Nicely). You can tell em I said so. (Bear in mind sometimes the hand/feet appliers are sold separately. This is ok as long as they are available)
  7. Can't say I predicted this.. but this doesn't surprise me in the least. I'm sure all the image-conscious skin makers are considering this. There's a healthy number of creators who ONLY want their stuff to appear on certain meshes. And even the folks who aren't so exclusive minded know they are going to be blamed when people try to use Bakes on mesh on stuff like hands and feet and this happens: Frankly, skin makers are going to have to rush to get new system skins out that have the Mesh Friendly Textures on them.
  8. Hi! The first thing to note is that Bakes isn't fully released yet, so if you do any sort of bakes on the mesh, it'll look funny to anyone not using the project viewer. Second is, that you will need the BoM project viewer. Once you've gotten on your project viewer, you can change meshes to BoM manually if they are mod in the texture tab of the edit window. If your meshes are NOT mod, the easiest way to enable it is to use an applier to apply the BoM uuids. If you have Omega Installed, you can use the free ones I tossed in here: https://marketplace.secondlife.com/p/Omega-Add-Ons-Applier-FixerConverters/10734638
  9. They do however cost labor. It's become habit in SL for everyone to build everything themselves, but getting a team together and actually paying them lets you churn out products much more efficiently. This is important when you start into complex projects like games since many skill sets are needed and frequent updates expected in order to keep users engaged.
  10. Well I presume people will want to. Alpha HUDs are the absolute WORST. -chuckles- But yeah, they'll work for now. That is a good point about being able to adjust the alpha. I wonder how many creators would want to make that an option...
  11. Well this is amazing. Is it just certain viewers? Certain Sims versions? Do we need an update? Or will it work on all viewers now?
  12. Mapping and other considerations aside, there WILL need to be one update for all no-mod meshes in the Human Body/head Market. They're going to need a button to switch the skin layer from Alpha_Mode_None to Alpha_Mode_Masking. Otherwise any bits you alpha out turn into blank space. I have spent the last 3ish years making sure everyone knows to set the skin to none to avoid the alpha glitch annnddd now it's gunna futz things up. -chuckles- And yes Mesh Makers, if you have one of my scripts in your stuff, unless we're doing API application only, your skin is set to Alpha_Mode_None with every skin application.
  13. Yeah, as I said, I got it working when I shunted both through a llStringTrim A few minutes after posting this. Because of course you always find the solution as soon as you open your mouth to complain about it.
  14. It's a distinct possibility. It is the first item in a list of data that's getting parsed out, so thats probably it.
  15. Yip, I'd type cast them, sent them through llToLower, llEscapeURL, everything I could think of. I finally got them working when I sent them both through llStringTrim. Which is weird, cause neither appeared to have any trailing anything. But if it works, it works.
  • Create New...