Jump to content

Yingzi Xue

Resident
  • Posts

    259
  • Joined

  • Last visited

Everything posted by Yingzi Xue

  1. I have many thoughts on this, but have struggled to put together a coherent post thus-far, having spent a good hour or two writing and rewriting this post. I'm going to try to get it all in the post. It might be a jumbled mess. I apologize in advance. History When I joined Second Life in 2007, Hippo was the product to use for vending and renting. It was far from perfect. It was bloated because it had to be, to ensure reliability. Script functions would be added later to make way for better solutions. At the time, as a budding creator (scripter, builder), I wanted to open my own store and sell products. Hippo seemed the logical choice, so I purchased it. I never did end up using it, because I couldn't abide by the inefficiency of how it was designed. Like Casper, I wrote my own vendor system out of necessity, but ended up selling it as one of my products for many years. (It is no longer on the market.) Hippo lit a creative fire in me to do better, so the purchase was not a loss in my view. Keep in mind, I never intended for my vendor system to compete with Hippo, nor be the next big thing. It was aimed at a niche market that shared my view that vendors should be efficient, reliable and minimal. At around the same time, Casper's work was starting to gain traction. I eventually purchased CasperVend and CasperLet (et al), not only to support Casper's work, but to see the design of his products. CasperVend and CasperLet CasperVend and CasperLet are great products and will make a great addition to Second Life, but they're not for me. Here's why. Even though I own these flagship CasperTech products, I don't use them. The philosophy I held back in 2007 is still the same today. A vendor system should get out of your way and let you sell your products, not mire you in configuration settings and feature checkboxes. Upkeep should be simple and straight-forward. Closing Thoughts I hope Second Life takes their new acquisitions in the direction of efficiency and minimalism, updating the Marketplace with the same workflow. I would also appeal to the sensibilities of the creators out there, that less can be more.
  2. Thank you all for your responses. Yes, I was aware of the spacing between prims to get physics to come out correctly, and the physics shape looks perfect, even when rendering metadata for physics. The physics shape was solid, until you bumped into it a few times repeatedly, and then you popped out the other side. I do think .2m+ is definitely the way to go for consistent results. I'm still trying to develop a good (simple) workflow for modeling buildings in Blender for Second Life without it becoming a convoluted mess, so I'm looking at the work of others for clues. I was looking at one builder's work. He seems to make all of his walls out of planes, and his physics turn out just fine. I tested with a single plane wall and I couldn't walk through it, even though it's not .2 thickness. I'm guessing he uploads each wall piece individually as planes then assembles them. Another interesting thing he does is overlaps his walls by .2m on each end. These responses have helped. Much appreciation.
  3. .1 works as well. Edit: Although this may not be consistent either. I recommend thicker.
  4. I made it .2 thick and it fixed the issue. I may experiment with slightly thinner just to see where the sweet spot is.
  5. I'm working on a mesh boat. I've made a physics shape out of planes in Blender, and upload it with the mesh object. The physics shape shows solid in Render Metadata, but if I collide with it repeatedly, it will allow me to walk through it, even though it's supposed to be solid. Is there a certain thickness a physics shape has to be to keep this from happening? Or am I missing something?
  6. Thank you for answering. I don't think it has, unfortunately.
  7. I've been trying to get a front view (facing the avatar) camera view to work with walking, but the camera does not move with the avatar. I assume you have to update the position of the camera, whereas the follow camera is dragged behind the avatar. I wanted to ask here if anyone has gotten it to work before I give up on it.
  8. It did the same thing for me. I did try a few different things to see if I could keep it from happening, but nothing fixed the issue. You can reverse the order of request functions in the code and pass a NULL_KEY on the outset; llRequestUsername silently fails. If you pass it a good key, you get the username, as expected. Granted, this is reverse of the functionality of the script, but it avoids the bug. One possible workaround... Since the username is already known, just check to see if the returned data == username, if so it's a fail.
  9. I would point to Blender as one example of a great open source project (there are countless others). Most Linux distributions have thriving communities and you can find all the support you could ever want. The beauty of open source is that you can modify it to your liking, to get the functionality you want. Open source, by its very nature, keeps the software clean, because the source code can be downloaded, perused, compiled and used by anyone. LSL is an easy language to learn. There are plenty of examples available to get you started. There is a support forum where people are willing to help. There is a Wanted forum where scripters are willing to help make your project a reality. If you don't agree with the ideology of a developer or their software license, don't use their software. If enough people disagree with their way of doing things, it will cease to exist. It's okay to disagree with another person's opinion, with an ideology, with their way of doing things.
  10. I can empathize with creators, sellers and resellers over the banning of gacha. However... the situation they find themselves in is of their own making. Rares What constitutes a rare item? Is it the extra work that goes into making an item unique? Is it the creator's emphasis on said item? Or is it the vendor script that makes it rare? Aside from the first question—the creative aspect—said "rare" status of the item is artificially produced and presented to the customer. Can extra work make an item truly rare? No. It's the selling method the creator chooses to use, to limit the purchase of said product. Campers, Traffic and Lag What causes camping, traffic and lag issues? The elusive item? The timed freebie? Is it the potential customer pining after them? No. These are problems caused and reinforced by the creators and sellers who use scripted methods to limit access to said items, thereby making them artificially hard to get. The false sense of the rare. The elusive item. The issues with campers, traffic and lag are self-inflicted by the creators and sellers that present these methods to their customers. The customers then adjust their behavior, to obtain an artificial rare through the means they have—camping, clicking, etc. Yes, using these methods can increase sales, but they introduce a host of problems that shouldn't exist if the products were sold outright, not withholding them from the customer through artificial means. It's a clever tactic. Present the prize, then make it hard to get. While it may be a dopamine goldmine, the consequences are many. Cause and Effect The issues I see complained about on this forum, by creators and sellers of gacha and the future problems of the potential conveyor system(s), and others that exist now, like lucky chairs, et al... are caused the creators and sellers themselves and how they choose to sell their products. The problems being discussed here, because of said systems being used, should give pause to creators who seek to place their products behind constructs, to artificially inflate their value. The conveyor system exposes what was hidden behind the gacha gambling mechanic; machines of excess profit and dopamine manipulation. Problems with other systems should be readily apparent. There are countless innovative ways to sell products and fix the problems that exist today. Innovate, don't manipulate. There is value in a special item that took longer to create. Charge the appropriate price and it will sell. If you can't sell your products without some sketchy methodology, then maybe you shouldn't be creating and selling products.
  11. Regarding how some script... As a scripter who prides themselves on efficiency, I find that sad—but I know it's true. lol It'll be interesting for sure. I can't wait to read about it on the forums.
  12. I think a queue will keep that from happening, as it will dump all of those extra attempts to interact with the object. If scripted properly, it should only respond to the current user. Much like some vendors operate. Once mitigated, lag shouldn't be much of an issue.
  13. The script for making this function would be super simple to write, but as you said, handling input in an efficient, low-impact way is going to be key. No matter the delay, you're still going to have the potential for campers mass clicking on the object, unless you use a waiting list or queue for interacting with the unit. Cycle through avatars who have clicked on the unit and give them each time to use it. If an avatar leaves, drop them from the queue. This would make it somewhat fair and help dump unnecessary clicks. It'll be interesting to see how the creator handles it.
  14. I was in the process of writing a post to make this point, but you beat me to it. Whatever profit you are used to receiving above and beyond the market value of your product(s) is not actually profit, but cash that wouldn't/shouldn't exist. Supply and demand. If there isn't a demand for your product(s), then they won't sell and you will go out of business. Businesses adapt or die every day because of this very thing. Being reliant on a gambling mechanism to make up the difference isn't a sound business practice. 1) It's unreliable to say the least, 2) It gives a false sense of value to your product(s), 3) It becomes a crutch. I sympathize with creators who are struggling with change, but I see a world of opportunity (untapped potential) for gacha style product(s) without the gambling aspect. Rather than trying to make an alternative gacha vendor to skirt the new rules, I'd be focusing on ways to maximize legitimate profits in the SL landscape.
  15. I did. Here's a direct quote from my post: The illusion of value of a rare is what makes gacha so alluring. Actual value of said rares vary. Some rares are just a retexture, while others are unique models. The amount of time a creator spends on a rare might be a few seconds to a few hours. Sometimes the rare is worth it, but most of the time it's not.
  16. My post spoke specifically of rares and the fact that the extra work done by the creator to make said rares may not necessarily justify (or most often does not justify) the extra expense a consumer puts into acquiring them. This in no way negates the worth of gacha products in general, but puts into perspective the minimal effort often put into a rare by the creator (a retexture, for instance) vs the cost to the consumer, which definitely is not worth it to the consumer. Some of the most innovative products in SL are sold in gachas. I have no doubt they will continue to sell outside of the gacha mechanism.
  17. Full Disclosure—I stopped after reading several pages of the thread to write this reply. I haven't read all posts yet and I don't know if I will. Long time creator here. I have never used gacha machines to sell my own products, but I have purchased many products from gacha machines over the years. My own experience has been that I feel the same feeling from gacha machines that I get from slot machines. The desire for the rare prize, the endless optimism that the next purchase will be the rare, the exhilaration of the game of chance. It can be addictive. I've emptied my meager account a time or two in the pursuit of the rare. I've purchased extra money so that I could try again. The illusion of value of a rare is what makes gacha so alluring. Actual value of said rares vary. Some rares are just a retexture, while others are unique models. The amount of time a creator spends on a rare might be a few seconds to a few hours. Sometimes the rare is worth it, but most of the time it's not. Gacha enables consumers to willfully spend way over the actual worth of the product in pursuit of the shiny bauble. This, of course, greatly benefits the creator/seller as any extra money paid is free cash that they would otherwise never receive from the sale of their products. I can see why creators and sellers might be upset. Gacha is a cash cow. Gacha enables creators to earn well beyond the actual worth of their product. If anything, the removal of gacha levels the playing field, and forces creators of gacha content to sell their products at market prices. In my view, that's a win for the consumer. I can see why consumers might be upset. I do admit, I will miss the thrill of paying a gacha machine, but I won't miss the zero balance on my account, and the creator in me is happy that consumers won't be taken advantage of anymore—even if they are/were willing participants.
  18. I'm using alts to test on my parcel, so it's my same viewer, which is the latest SL and Firestorm viewer. I've tried leaving and coming back, relogging, but the parcel EEP settings do not take effect on my alt. This is on a mainland parcel. EDIT: It would appear that an experience must be used for parcel environmental settings for mainland. I'm not sure yet. I've set up an experience and used a script to set a specific EEP setting and it seems to work. I'll play with it some more.
  19. I've set a customized parcel setting, but it isn't triggering for other avatars. I'm using the latests SL version as well as the latest Firestorm. Am I missing something? Use Shared Environment is checked.
  20. Right now, all you're doing is setting FULL_BRIGHT and GLOW. Check out PRIM_COLOR for prim color. Check out PRIM_POINT_LIGHT for light emission color. Detailed info can be found here: http://wiki.secondlife.com/wiki/LlSetLinkPrimitiveParams#llSetLinkPrimitiveParams Also, I suggest using PRIM_LINK_TARGET instead of 34 in your statements, it's much easier to read.
  21. You could get around having to use a script by putting x copies of the product (packaged in no copy boxes) in the vendor object, rezzing it at the start of the event and deleting at the end of the event. It would require very little effort to set up and maintain and it would save you the cost of a custom script.
  22. If you just want a basic send-to-SQL system, it's not too difficult. Before you begin: Learn Linden Scripting Language, or at the very minimum, how to send/receive HTTP requests and parse incoming data. Learn an appropriate server side language that can receive HTTP requests and access SQL (PHP, for instance). Setup: Find a host service that provides a web server with SQL. I use a Virtual Private Server. Create the SQL database(s) with the desired tables and fields. Write your vendor script that sends sales info to your server through HTTP requests. Write server-side web pages (PHP, for instance) to process the HTTP requests and write to SQL. Test it until it works as expected. If you want, develop web pages that display the stored info. Long-term: Save backups of your database(s) frequently. Grow the system with added functionality. That's how I did mine, for my own business. NOTE: I do not sell my system, it's proprietary. Nor do I offer to do custom work for this sort of thing.
  23. Already did. Every place I select gives me the same error. EDIT: Looks like they fixed it. I just logged in.
  24. I'm having the same issue. I can't connect to a simulator.
×
×
  • Create New...