Jump to content

Anna Salyx

Resident
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

15 Good

About Anna Salyx

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @Fauve, I fully get that. Truly and maybe about 30% of the time I just want one piece out of a "set" but most of the time I'm looking for an outfit to add to my closet. I don't know if I'm the norm on that aspect of shopping or the rarity. Merchants might be able to tell based on buying patterns. Now, in counter point to some of your observations: * most designers who sell separates, usually bundle demo is an all inclusive box with all pieces and demo huds.. * Ad copy is usually one or two of the more aesthetically pleasing combinations (the logical set I referred to) and maybe a separate texture of the different options to one side. So in terms of demo and advertising it's no added work in most cases that I've come across. Moving on from that, in the biggest majority of cases that I've personally seen, the "in store" or "in event" displays, the merchant has arranged various separate pieces (top/bottom (/sometimes jackets or shoes or etc)) in an aesthetically pleasing display, in columns/rows suggestive of, again, what I term the 'logical set'. Buy the top, by the bottom under it (and sometimes the extras). Now, keeping it simple for this example though: buy the top for 300, buy the bottom for 300, all I'm proposing/asking for, is an added option right under each set column maybe an option to "buy this set" for 500. The merchant is, in many cases, taking the time to create the aesthetic sets for display already. I dunno of the potential extra sales it might generate would make for the extra work to create a few extra sale boxes. But for me, personally: I pass on a lot of "sets" that I'd like to have when the different components bought piecemeal ends up above what I'm ready to pay at that time...., so it might. Again, I'm not saying "do this or else!" Sometimes I do see different combinations than the merchant did when they set up the display when I do I'm very glad I can buy the outfit piece by piece and make my own set. Sometimes, I just want one single piece cause I have something already I think it will pair perfectly with. So, I don't want to see the separate sales go completely away. No, I'm simply just throwing a suggestion out, asking for options as it were and seeing what might stick. The conversations sparked has been good though, and that is always a positive. I just wanted to add a bit of extra on this on my perspectives that I didn't get to in the original post. I"m not sure if I have anything to add more, so closing it on up again.
  2. One trend that seems to come and go, and i wish would mostly go, is the idea of selling "sets" as separates. That is, tops and bottoms that logically go together being sold as separate items and thinly masking a (sometimes) significant mark up. I do get it that some people like to mix and match and in general I'm on board with that, but at the same time I like to see merchants maybe offering single logical sets at a cost point somewhere in the middle of buying the two (or more items) separately. then if I want to maybe do a bit of mixing, I can by added pieces at their normal separate price points. What really drove this post though was recently I saw a set at an event. It's a very cute outfit that consists of a shirt collar, top, skirt, and thong and each item was sold separately. The total cost to get a 'single' outfit was just shy of $L900. As a set I'd expect to pay maybe around 300 to 500 lindens (based on pricing on similar sets sold as sets) and that's a reasonable pricing based on the current market. I'd have bought it if there was a color set grouping option in that price range but I (personally) couldn't justify 900 for single color pack so I reluctantly passed it by. I'm not saying to creators to never split items in a set up. I agree in principle that it is a good way to generate extra sales for those who like to mix/match, I just want to spark some conversation on the idea of also having logical color sets available as well at a modest middle price point. Anyways, that's all I got on this. I tend to stick with designers who offer up sets more than separates, but if the pricing on the separates is reasonable I have no problem making my own sets, it just seems that some designers are using it as a way to double (or more) their income on some items. and now I'm starting to repeating myself, lol, so I'll end it here. Happy New Year everyone.
  3. The added channels and the new universal wearable that takes advantage of that I think will be allowing for single arm and single foot on bodies that conform to the standard body maps. However, (and somebody correct me as needed) for it to work it needs alpha blending to be enabled on the mesh itself, and as far as I know, the M.Lara doesn't support it yet for that reason. I know that you can't use a traditional clothing alpha mask (not a whole body mask) for that same reason, that ability is turned off in the current M.Lara bodies, so I'm doing some guessing on the universal wearable. I've been trying to figure it out and it's not working not matter what I do, so I'm assuming that is why.
  4. use llSetLinkPrimitiveParamsFast with the PRIM_SPECULAR flag. It is more complicated than a simple stand alone 'set specular' command, but it'll get the job done for you. edit: and on a reread you do state you are new on scripting. The set primitive params set of commands has a bit of a learning curve on the syntax needed to make it work, but it can get into some of the deeper parameters of a prim that can't be done with any of the stand alone commands, and, as a big pus, it can do several all at once. That can be very useful at times. Tinker and play with it.
  5. I'd be interested in reading up more on the specifics of flag value 8. Do you know off the top of your head the jira or release notes addressing this? Thanks.
  6. As a side note from the linden question, unless you have a compelling need to permanently close the account, I'd suggest rather than cancelling, simply change the account type from premium to free/basic (if applicable) and clear out any payment methods (again if applicable) for security reasons, and walk away. Your avatar and all it's current belongings will sit idle and if in the future you ever decided to peek back in, you won't start wholly from scratch. I get it if you need for personal reasons to make that hard line account closure to reduce/eliminate temptation in the short run, but for me personally I've come to appreciate the ability to go visit some old haunting grounds after years of being away and have been very glad that my accounts/persona's have remained. Sometimes I'll only drop in, say hi, remember why it was I left and go away gain. Sometimes though, I go back and find it was time to pick it up again making a new chapter in that particular experience. In any event, I do wish you safe travels away from here and may y our path lead to you what you need or seek and with luck both are the same.
  7. I"m not discounting that. The first recorded usage for the term is from 1887. However, the fact that the Harley stock ticker symbol is HOG, and in relation to motor cycles specifically the word hog has a very strong association with the Harley-Davidson brand specifically -- coming from multiple angles. Right or wrong, the usage of the term might be one of the flags for which that claim is being applied. That is all I'm saying as a point of conversation and contribution. I could very well be in error, but it's something to at least consider.
  8. Adding a bit to the conversation before it gets too far into the past. Harley-Davidson's stock ticker symbol is HOG. H.O.G is the acronym for Harley Owner's Group. The word hog has become fairly synonymous with the Harley-Davidson brand specifically, and I don't know if it's not a trademark or not, or how much it as a term is officially tied to the the brand beyond the ticker symbol. I did see at least one of the listings used the term hog motorcycle ("Road Hog"). I've not gone delving into any of the listings to see how common that term is being used but it might be a key word term that is being used to flag motorcycle type products as infringing. Just a thought added to the conversation.
  9. Business need to access SPI (sensitive personal information) is usually limited within a company to those who are directly customer facing, that is sales and customer service representatives. The company I work for, even then in most cases when a sales rep or CSR is working with a customer they will state "I need to access your account to proceed, do I have your permission". I work in billing operations and I have zero access to customer accounts. I don't have a business need. But I digress: to answer your question, access to your SPI is most likely going to be limited to only those people who have a direct immediate need for it at a given point in time. Employees will probably have to access your private data through an internal gated system that prevents the average worker from seeing it.
  10. Pity. I had just really learned about this feature change not long ago. I saw it as a niche thing with a very narrow application. But that said, I was kinda kicking around ideas on how it might be used within that niche scope. I'd not gotten nothing past the concept/idea phase so no big loss of time or effort though. But to be clear, it's only the title/role change part of that feature that has been taken away, not the general group change command, yes?
  11. As far as I have been able to tell in some quick playing around is: One of the things I can see that will be different from the still being sold version and the free version is the associated experience key. The sold version will continue to be done up under the AVSitter experience key. Users of the opens source version will have to obtain their own experience personal key if they can and associate it there -- That is there wont be a nice blanket AVSitter experience regardless of the who makes the final product. It's a small thing but it can be a significant thing in terms of trust. If I ever start making anything for more than personal use, it might be something that will give me some pause to think about.
  12. Replying to Ivan. Do you have anything that is RLV locked to your HUD space? This will cause the behavior you describe. Don't know why, but it does. If you do have a HUD that is RLV locked, simply unlock before you enter edit mode and you will be able to zoom way out again. If you don't have such an item, then, sorry, I have no other ideas. Luck.
  13. Another method if you want a slightly simpler solution is to use the get and reset time functions. They count the seconds since the script was started or since the last time the timer was reset. It's a useful set of commands. I like the timer multiplex solution listed above and use it and variants of it frequently but for some thing it's jut a bit much when when one is looking for small and simple. So to adapt your script in another way would be like this: integer touchActive = FALSE; default { touch_start(integer detected) { if (!touchActive) { llWhisper(0,"Timer started."); touchActive = TRUE; llSetTimerEvent(300); //5min llSetLinkColor(LINK_SET, <0.180, 0.800, 0.251>, ALL_SIDES); // green llResetTime(); } else { integer elapsedTime = (integer)llGetTime(); llWhisper(0, "Timer active, " + (string)(300 - elapsedTime) + " seconds remaining."); } } timer() { llWhisper(0, "Timer ended."); llSetTimerEvent(0); touchActive = FALSE; llSetLinkColor(LINK_SET, <0.694, 0.051, 0.788>, ALL_SIDES); // purple } } You could of course put in some code to manipulate the out put so it shows minutes + seconds remaining, or any number of things. But the llResetTime(), llGetTime(), and llGetAndResetTime() commands are handing for getting quick elapsed counts that don't require a whole lot of overhead for smaller and simpler scripts where a multiplex approach is not really justified.
  14. The link above to the doc API will help, but the critical step is the llSay or llShout,or llWhsisper or llRegionSay, and even llRegionSayTo. It must be on the standard RLV channel, including the UUID of the target AVI and the command and parameters. The target avi *has* to be wearying a RLV relay device of some sort that is turned on and in either auto accept or ask mode. That is where the magic happens. The relay listens on the RLV channel, looks to see if the command is directed to its owner and then parses the command. You might be able to around all that with experience keys on the land. But that is a different topic and discussion. Hope that helps
  15. Three...now, but I think I saw some shuffling behind me. Or it might be zombies. Hard to tell sometimes...... /shrugs.
×
×
  • Create New...