Wulfie Reanimator

You could try putting up a Jira about it, that way devs are sure to look at it and check whether this is expected behavior or a bug.

This may be related to your text having anti-aliasing on it, which causes different Roughness values for the outline. Not exactly sure why it shows up like that visually, though.

There's no mention of any disabilities in your profile. The amount of details you've left out are a little telling that there's more to this than you let on.

I tend to enter the local province/region, or just the country again. "N/A" should also work, or any similar "no state" text.

The problem is line 19: if (intOffset == 0) { return strTimestamp; } In that case, it'll just output the raw string from llGetTimestamp() instead of doing any of the formatting below (eg. 2023-11-21T15:33:10.530729Z) If you remove that line, it'll format correctly again. (eg. 21-11-2023 15:33:29)

Would you pass a copy (with modifiable scripts) to me in-world? Seems like an interesting problem.

All the chatter tends to happen elsewhere, before code is submitted/merged into the viewer. Places like the public LL meetings, forums of TPVs, Jira tickets, and of course internally within LL that we can't see.

What if you just make a support ticket asking for them to restore the group?

To be fair, the signup bonus is terribly mentioned. On the page where you choose your plan, the "45 days" line is at the very bottom of the page, and there's no indication on the bonus that there's a caveat.

Yup.

If you were logged in when you paid it, you probably need to relog. The sign-up bonus is given to you only after you stay subscribed for 45 days consecutively. If you only subscribe for one month and stop, you have to start over and sub for 2 months, not counting the first.

Anyone know where's the wiki page to actually edit those GLTF params?

Try logging into a different sim.

If you own the notecard, you can always read it. The "you do not have permission to view this notecard" message is only shown if you're trying to read a notecard you don't own, for example in someone else's object. What are you trying to do? If you want a scripted object to read a notecard without the owner being able to see the notecard.. you can read notecards by their UUID, the notecard doesn't have to be in the same inventory as the script.

The flickering you see is caused by the behavior described in the wiki. Ribbon particles are always connected to each other, regardless of distance. The last/oldest particle, which has arrived at the target, is only connected to the particle that will come after it. When its lifetime ends, the ribbon "chain" gets shorter because one particle has been removed. More burst rate and lifetime helps, but the flickering section grows with distance. One solution would be to use two particle systems, going both ways. That way the flickering is hidden by the other ribbon chain. Another solution might be getting LL/TPVs to change how ribbon particles are rendered, so that the oldest particle is also attached to the target, similar to the newest particle. That would probably cause a straight line between the source/target until enough time has passed for the particles to travel their actual path.

There's a whole bunch of "hidden" data in the page that's just not visible by default.

If you plan on making the kind of money that pays the bills (or at least groceries), you'll probably want to focus on just service/commission work. (In which case you could just invoice them through PayPal and avoid the LL fees.) I can't imagine any amount of games in SL (especially Portal Park) would get you enough lindens to cash out anything meaningful per week/month. Content creation is an option, but it takes significantly longer to build a store, let alone finding traction.

Yes, I understand. With the exception of that one caveat, what I said holds true.

Is there a difference? When you rez a new object with build-tools, that's when that object is originally created. When you upload a mesh file, that's when that object is originally created. (Whether it uses the current date or the source file's date doesn't matter much.) Either way, OBJECT_CREATION_TIME returns the same date for all copies of whatever the original asset had as its creation date.

This may be a side-effect of how uploading identical assets works. For example, if you upload a texture... and then upload the same texture again, you'll get the same texture UUID both times. Basically, LL will check if the asset already exists, and then give you that copy instead of creating a brand new one. I hadn't tried it with mesh, but it seems very likely that they handle all assets the same way. If you want two creation dates (neat thought), just make any change to the mesh (like move one vertex by 0.001 units) and it'll no longer match the other asset.

Europa immediately comes to mind. This is a creator who made original stylized content, before moving on to game development. I don't think it's a problem that users can change their lighting at will.

And just to be clear, PBR is not fully released yet. Sure, you can see PBR content in PBR-enabled regions, but many regions and most viewers don't have that functionality yet.

The "update" to petite/flat that was talked about earlier in this thread was about them becoming part of the body itself, instead of a separate attachment you wear with the full body. Similar to Legacy / Legacy Petite. I dunno if that's still accurate or if it was just speculation, or how it would affect the prices of those addons.

Some of your products definitely step into keyword spamming. You copypaste the same tags a lot, even between unrelated products. For example, a stack of 3 books with these keywords: drapes, curtains, couch, chair, desk, lamp, light, table, stool, barstool, fireplace, mugs, pouffe, daybed Or for example when you sell pants and shirts separately, you have the same keywords on both. Shirts tagged as pants, and pants tagged as shirts. I don't think you should cry about Big Brother when another user reports your items for keyword spamming, especially if it took 10 years. Just fix your keywords and move on.

If a bone is no longer animated by anything, it appears frozen in whatever position it was in previously. There's also a long-standing bug where an object whose UUID is lower than your avatar will stop all animations instead of just the animation it tried to stop.