Jump to content

Kardargo Adamczyk

Resident
  • Posts

    174
  • Joined

  • Last visited

Reputation

95 Excellent

Recent Profile Visitors

1,384 profile views
  1. Among a few issues that it could be, Its always DNS but seriously, this could be the result of a slow DNS response telling your computer on what IP Address the server lives that holds the region. you can try to open your network settings and change the ip4 settings, then change dns from automatic to manual and enter 8.8.8.8 and 1.1.1 (Google & Cloudfare) as the servers, then see if the issue is resolved.
  2. Its because 2 homesteads share core and memory on a server, 4 open space regions share a core and memory on a server , a full region gets its own core and memory.
  3. File a support ticket on the support page, LL will copy your account to the beta grid and access will be restored. Good luck
  4. you are still thinking of banning accounts... that's the wrong way around, they should close the backdoor that makes it possible to crash a region in the first place, i have no access to the logs, i can not see what is used and how they are able to crash a region, i do know that this has been going on for years and Linden Labs seems to be unable to fix it, that shows sheer lack of competence.
  5. well clearly it does not work, here is the result of the past 2 hours... think that's funny? i think its a blatant shame that Linden Labs seems to be unable to get their act together and fix it, clearly there's some scripting that accounts for this, or some object being attached that crashes a sim, perhaps even a ddos from outside towards the server, none of which are hard to prevent. don't forget we pay for this service, and its not to much to ask for some decent support and security. [2020/07/18 10:07:44] Advanced SIM-Watcher 1.2a: (2020-07-18) 10:07 AM: 'WIKKED COVE' entered status 'STARTING'. (Been 'UP' for 72 hours, 45 minutes) [2020/07/18 10:08:44] Advanced SIM-Watcher 1.2a: (2020-07-18) 10:08 AM: 'WIKKED COVE' entered status 'UP'. (Been 'STARTING' for 0 hours, 1 minutes) [2020/07/18 10:15:44] Advanced SIM-Watcher 1.2a: (2020-07-18) 10:15 AM: 'WIKKED COVE' entered status 'DOWN'. (Been 'UP' for 0 hours, 7 minutes) [2020/07/18 10:16:44] Advanced SIM-Watcher 1.2a: (2020-07-18) 10:16 AM: 'WIKKED COVE' entered status 'STARTING'. (Been 'DOWN' for 0 hours, 1 minutes) [2020/07/18 10:17:44] Advanced SIM-Watcher 1.2a: (2020-07-18) 10:17 AM: 'WIKKED COVE' entered status 'UP'. (Been 'STARTING' for 0 hours, 1 minutes) [2020/07/18 10:20:44] Advanced SIM-Watcher 1.2a: (2020-07-18) 10:20 AM: 'WIKKED COVE' entered status 'STARTING'. (Been 'UP' for 0 hours, 3 minutes) [2020/07/18 10:21:44] Advanced SIM-Watcher 1.2a: (2020-07-18) 10:21 AM: 'WIKKED COVE' entered status 'UP'. (Been 'STARTING' for 0 hours, 1 minutes) [2020/07/18 10:26:44] Advanced SIM-Watcher 1.2a: (2020-07-18) 10:26 AM: 'WIKKED COVE' entered status 'DOWN'. (Been 'UP' for 0 hours, 5 minutes) [2020/07/18 10:27:44] Advanced SIM-Watcher 1.2a: (2020-07-18) 10:27 AM: 'WIKKED COVE' entered status 'STARTING'. (Been 'DOWN' for 0 hours, 1 minutes) [2020/07/18 10:28:44] Advanced SIM-Watcher 1.2a: (2020-07-18) 10:28 AM: 'WIKKED COVE' entered status 'UP'. (Been 'STARTING' for 0 hours, 1 minutes) [2020/07/18 10:34:44] Advanced SIM-Watcher 1.2a: (2020-07-18) 10:34 AM: 'WIKKED COVE' entered status 'DOWN'. (Been 'UP' for 0 hours, 6 minutes) [2020/07/18 10:35:44] Advanced SIM-Watcher 1.2a: (2020-07-18) 10:35 AM: 'WIKKED COVE' entered status 'STARTING'. (Been 'DOWN' for 0 hours, 1 minutes) [2020/07/18 10:36:44] Advanced SIM-Watcher 1.2a: (2020-07-18) 10:36 AM: 'WIKKED COVE' entered status 'UP'. (Been 'STARTING' for 0 hours, 1 minutes) [2020/07/18 11:56:19] Advanced SIM-Watcher 1.2a: (2020-07-18) 11:52 AM: 'WIKKED COVE' entered status 'DOWN'. (Been 'UP' for 1 hours, 12 minutes) [2020/07/18 11:56:19] Advanced SIM-Watcher 1.2a: (2020-07-18) 11:53 AM: 'WIKKED COVE' entered status 'STARTING'. (Been 'DOWN' for 0 hours, 1 minutes) [2020/07/18 11:56:19] Advanced SIM-Watcher 1.2a: (2020-07-18) 11:54 AM: 'WIKKED COVE' entered status 'UP'. (Been 'STARTING' for 0 hours, 1 minutes) [2020/07/18 12:00:43] Advanced SIM-Watcher 1.2a: (2020-07-18) 12:00 PM: 'WIKKED COVE' entered status 'DOWN'. (Been 'UP' for 0 hours, 6 minutes) [2020/07/18 12:01:43] Advanced SIM-Watcher 1.2a: (2020-07-18) 12:01 PM: 'WIKKED COVE' entered status 'UP'. (Been 'DOWN' for 0 hours, 1 minutes) [2020/07/18 12:05:43] Advanced SIM-Watcher 1.2a: (2020-07-18) 12:05 PM: 'WIKKED COVE' entered status 'DOWN'. (Been 'UP' for 0 hours, 4 minutes) [2020/07/18 12:06:43] Advanced SIM-Watcher 1.2a: (2020-07-18) 12:06 PM: 'WIKKED COVE' entered status 'STARTING'. (Been 'DOWN' for 0 hours, 1 minutes) [2020/07/18 12:07:43] Advanced SIM-Watcher 1.2a: (2020-07-18) 12:07 PM: 'WIKKED COVE' entered status 'UP'. (Been 'STARTING' for 0 hours, 1 minutes) [2020/07/18 12:22:43] Advanced SIM-Watcher 1.2a: (2020-07-18) 12:22 PM: 'WIKKED COVE' entered status 'DOWN'. (Been 'UP' for 0 hours, 15 minutes) [2020/07/18 12:23:43] Advanced SIM-Watcher 1.2a: (2020-07-18) 12:23 PM: 'WIKKED COVE' entered status 'STARTING'. (Been 'DOWN' for 0 hours, 1 minutes) [2020/07/18 12:24:43] Advanced SIM-Watcher 1.2a: (2020-07-18) 12:24 PM: 'WIKKED COVE' entered status 'UP'. (Been 'STARTING' for 0 hours, 1 minutes)
  6. I don't get paid by Linden Labs to create solutions, all i know that this stuff is going on for years, and somehow Linden Labs will not prevent giving every account the ability to crash a region.
  7. <rant> Why is it still possible for an individual to crash a sim, groups of avatars go around sims and crash them, again and again.. sometimes every ten minutes, if you ban them they pop onto another parcel and happily keep doing their thing, if you region ban them, they create another avatar. if you abuse report them, it takes a week or more until something is done. This problem has been going on for years! How is this still a problem? its time for Linden Labs to get their act together and fix this! </rant>
  8. T-Nation proudly presents: "The Sunday Service" The newest tracks out of the Beatport Trance Top 100, Hosted by Dulcix and mixed together by DJ Dargo. 2-4 AM PDT http://maps.secondlife.com/secondlife/WIKKED COVE/213/236/22 Be welcome @ T-Nation
  9. The Best & New Tracks out of the Beatport Trance Top 100. This Sunday 2-4 AM PDT Episode 83 of the Sunday Service. https://maps.secondlife.com/secondlife/Beloved/34/32/0
  10. The Best & New Tracks out of the Beatport Trance Top 100. This Sunday Episode 82 of the Sunday Service. https://maps.secondlife.com/secondlife/Beloved/34/32/0
  11. I was about to say, its been done before, I remember an article in "New Worlds Notes", after a bit of searching i found the clock, and its.... yours..
  12. Yup.. rezz the old AO inworld, edit it and go to the contents tab, identify the run animation, then you drag that animation from the object contents into your inventory, Next you rezz the new AO inworld (not as a HUD!), go to the contents tab again, identify the run animation, drag it into your inventory (making a backup copy), then right-click the animation in the contents tab and choose delete, After that drag the new animation (from the old AO) from your inventory to the contents tab of the new AO... Next open the notecard in the AO inventory, (its a BENTO AO so definitely not an AKEYO) and edit the run animation from the old name to the new name Reload the animations from the AO menu All done Good luck Dargo
  13. Hi, On your example case 1 is faster.. if someone touches an object, the detected function is triggered anyways, so better use it, if there is no event that triggers the detected function you can only use the llSamegroup, i.e. you can run the return of an llGetAgentList request through llSameGroup one by one to determine if the avatars in a region or parcel are in the same group as the object holding the script. on your second question, the simple answer is no, the more elaborate one is that there is no return key from the detected group function (to protect the account's privacy) just a simple integer 1 or 0, in case you use this function in an HUD or attachment, there is a possibility that there is no active group. You can however in a HUD or attachment run llGetObjectDetails(id,[OBJECT_GROUP]) This will return the objects group key, and a NULL_KEY if there is no group, you can compare the result of this key with another HUD or attachment to verify if both object have the same active group. attachments and huds will change the group when the avatar changes the group. Hope this helps, have fun Dargo
×
×
  • Create New...