Wulfie Reanimator

You would just add a new cube to the scene and export it, then add it to the "Physics" tab of the importer. (There's an option to "Load from file") I can tell from the wireframe that you probably used a Subdivision modifier, which is fine since it gives that smooth look, but a real-time environment like SL, the model should be optimized to get rid of as much geometry as you can. For demonstration purposes, I made a similar plate from a cube: You can select entire "loops" with Alt-Click. (Hold Shift to select multiple) The easiest place to start reducing geometry is in the flattest surfaces, like the top rim: You can press X for the "Delete" menu, and select "Limited Dissolve" so Blender will try to delete things without breaking holes into the surface. It doesn't have to be perfect quads (squares) either when you're optimizing. If you open the command search (Space for me, not sure what the default is), you can type in "Select Linked Flat Faces" and then "Merge" (Alt-M) whichever way works best. For example, here I would just merge at center: TLDR on how to optimize: Step 1: Select loop. Step 2: Delete.

You might also need a physics model, which could just be a (flat) cube. The physics model created by the importer is not great. What does the Edit view look like? As far as I can tell from the shading, that plate looks to be in the tens of thousands of triangles. Edit: Oh, you can tell from the lower-right corner. 15K triangles is very heavy. You should remove most of the edge loops from the plate as there's too much detail in that plate that won't ever be noticeable.

For those who miss the joke: Dunkey is a comedy/satire channel.

It's always the Russians (or furries) isn't it?

It does the exact same thing as regular C/C++ compilers. You can try this in any online compiler for example. If the value is signed and negative, it pads with 1s. integer i = -777; // Binary: 11111111111111111111110011110111 i = (i >> 1); // Binary: 11111111111111111111111001111011 llOwnerSay((string)i); // Output: -389 #include <stdio.h> int main() { printf("%d\n", -777); // "-777" printf("%d\n", -777 >> 1); // "-389" return 0; } If you have more questions, make a new thread (or PM me) and I'll be happy to answer them.

Firstly: SL definitely allows logical right shifting. integer i = 4; // Binary: 0100 i = (i >> 1); // Binary: 0010 llOwnerSay((string)i); // Output: 2 Secondly: You've entirely missed the point of the exercise. I'm not trying to have a practical solution -- a working script -- with any number of integers or any large lists. I'm very aware of everything you've mentioned and pretty experienced with bit-twiddling. This is a purely technical examination. I was trying to figure out "at which point does the internal server compile error happen?" The more things I try, the more convoluted the error gets. For example if I add a function call into state_entry, the internal error shows up until the predefined list length is satisfied. Otherwise it doesn't show up, except for the syntax error at the limit I originally found.

I looked into this, and found more weird things. If a global list has more than 4998 elements or a local list has more than 4995 elements, you will get a syntax error before the next comma. (Of course, the script crashes long before these limits are reached, due to stack-heap collisions on or before state_entry.) Here's a reference script. If you stay within that limit, but too many for a predefined list, you'll get the internal server error. That said, I have no idea what exactly causes the internal server error. It doesn't happen when I have 4800 integers (75KB) in a single list. I can't say if it's caused by some kind of memory limit or another problem.

As a very non-exhibitionist furry (not that I'm judging or innocent), everything I saw on the search results is pretty standard for any furry-specific places, or ones that also target furries. Sandbox, hangout, club, it's all mostly the same with people hanging with their bits out or otherwise unmodest outfits, other places just have a higher concentration of them. Full-on sex in public is not that common though. I also don't think companies care about furries. Just the graphic content in general. You can find just as many weird "human" places that heavily focus on more realistic taboos and degradation, but including all the kinks furries are into.

Receiving a refund is no reason to remove a bad review. It does not matter what the circumstances are. If your opinion of the product is poor, getting your money back should not change your review as reviews are intended to help others determine what the product is like. The actual rating (1-5 stars) is extremely subjective and shouldn't be looked at too closely. What you have to say about the product is important. If a piece of clothing has no demo (and I was still thinking about buying it blind), seeing a review telling me that it has rigging issues is very valuable information.

A friend of mine just showed me something weird. This code, which is 1040 lines long, compiles fine. But if you add one extra element to the test list, it refuses to compile with the error "Internal server compile error." The working code reports 14628 bytes of used memory before and after touching the object, so there's no stack-heap collision or impossible memory requirements. There are 43278 characters in the code, so it's not hitting the viewer's default limit. I don't know whether this "internal server" is internal to the viewer or internal to the actual server-server (technical term). Pre-post edit: The working test list has 1023 elements (last index is 1022). 1024 elements seem to break it. If you start another list, you can keep going just fine. Appending an element to test list in the touch_start event works just fine, even though the list starts at 1023 elements. I'm posting this because 1) it started as an interesting problem and 2) it turned out to be a seemingly undocumented quirk. It's not listed in the Limits page of the wiki. Real edit: Yeah, there are no hard limits beyond that besides the memory limit itself. It's actually possible to compile a script that will run out of memory immediately on state_entry. The maximum predefined list length may vary based on the data type, obviously this code only used strings.

Fortunately you won't have to see your inventory if you're using local textures. They are in their own tab, no folders, and they are removed every time you log off. Very clean in a way you can't mess up.

The head literally has the Omega system pre-installed. You won't need a relay, all you need is an Omega applier. (I have the head -- it's a great one.)

I'm pretty sure Animats agrees with you... Those were examples of "worse things." The same customer base that allegedly abandons a store for a 5% raise in prices?

The script shown in this thread has a couple bugs in it too. It requests permissions when the script starts. It will not check whether or not the object is attached to an avatar. It does not rely on the run_time_permissions event. It will assume the script will be automatically granted permissions. If the an object with that script in it is rezzed on the ground, it will make a permission request and try to play an animation 1 second later (because of the timer), causing an error that repeats every second until the permissions are accepted.

The people (like moi) who are giving their opinion that it's practically impossible (which does not mean literally impossible) don't decide what actually happens. You're allowed to talk about what you want and I'm allowed to respond to you with whatever opinion I have, but ultimately LL can (not) do whatever they want.

This is just a "lore-dump." It translates to "our system has multiple factions," it does not translate to "some of our players just don't respect rules." Your club has been the target of entitled people and/or just griefers who happen to also play in those systems. You shouldn't slam Progeny/whatever-else just because someone using that system is causing you trouble. You deal with those people as individuals and that's all you need to do. That said: lol vampyrs r still dum in sl

Matty Luminos Resident doesn't sound so bad. (Also yes, some MMOs allow spaces in names. For some reason that's not a common convention.)

It means inside the solid volume. More specifically, the ray will only hit the side of a face where the normal is pointing. A ray will never hit the "back" of a face, which is how it can "penetrate out" of an object. That said, I don't know what's going on with the floor. Have you tried a visualizer or starting the cast higher? Is the trailer available inworld?

JIRA is not for customer support. The issue that was closed was also marked as "duplicate" and added to the parent issue (the one linked in this thread, and the one you saw that text in). It was made after the one that's still open. Having separate issues for the same thing is detrimental to documenting and keeping track of it.

You just type them in while you're creaing a new thread. It cannot be done for comments. Almost nobody uses tags so they're pretty useless for this forum.

I know it's not a realistic option unless you have more money than sense. The way last names currently work (If I recall correctly) is that they're actually just sequential entries in a database, related to some unique number, which is used to generate the avatar's key and other data. This means that there's a limit to how many last names can even exist, which is why people can't just add their own last name into the list. We'd literally run out of last names in a few years. To make custom last names possible requires the entire account system to be reformed, which is even less realistic for LL than the $500 annual fee for you. That's the reason why last names are coming back as they were, instead of some new system.

If you want a specific last name, there is this option: http://wiki.secondlife.com/wiki/Linden_Lab_Official:Custom_Name_Program Otherwise you're stuck with picking from a preset list like everybody else (excluding the Resident era).

Probably this, under "Viewer Control": http://wiki.secondlife.com/wiki/LSL_Protocol/RestrainedLoveAPI Allow/prevent changing some debug settings : @setdebug=<y/n> Force change a debug setting : @setdebug_<setting>:<value>=force (*)

Not if you can't answer simple questions...

You make them or buy them -- most likely. As long as it isn't no-transfer, you can sell it.