Jump to content

LSL HTTP Changes Coming


Recommended Posts

On 1/12/2021 at 1:50 PM, Monty Linden said:

I'm going to assume you mean the desktop app is failing with that message.  One thing LSL doesn't yet provide is a fixed point where pieces of a distributed, scripted system can go to find the other pieces.  This usually means a small service on the internet where the pieces can register and search for other pieces (and do license checks, etc.).  Looking at the installation instructions, for the HUD, I'd guess that this function is associated with the 'AOS-Extreme: Object-DNS successfully updated:[200]' line in Local Chat.  If you are still getting this status, there's a good chance that part is working.  If not, the HUD needs a patch.

If the HUD is fine, problem will be either with the service or the desktop app or both.  There are some debug modes and interesting buttons ('CM') on the app.  Look for clues there as to what the app thinks it is trying to connect to and where data may be corrupted.  Look out for truncated hostnames in particular.  If the app lacks sufficient debug capabilities, you'll need to look at environmental tools to tell you what is happening:  Wireshark, syscall tracers, etc.  Those will inform possible actions.

 

Yes it's the desktop app that fails.

 

Link to post
Share on other sites
  • Replies 54
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

A few of the features of LSL HTTP usage will be changing slightly as a part of the migration to using cloud hosted simulators. Our hope is that these changes will not cause any problems, but hope and

The first testing region for these HTTP changes is available now: Cloud Sandbox 4 on the Aditi (beta) grid If you have difficulty logging in to that grid, it may be because your account has

Some more Aditi regions have been moved to this test version, for more convenient testing.  The current region list is: Morris Cloud Sandbox 1 Cloud Sandbox 2 Cloud Sandbox

Posted Images

On 1/12/2021 at 3:38 PM, Lucia Nightfire said:

Just an FYI, such setups can most definitely miss things as it's using sensors which have arc based ranges, meaning spherical or segments so unless there is complete overlap of all scanned areas of interest you will have blind spots. Also, there is a limit to the number of returns sensors can make so anything beyond that limit could be missed.

It would help if we had a script function to scan a parcel with filtering options and specified object key return limit.

Thomas did a fine job.. His sim scanner didn't miss anything at all.  I used it extensively. I've moved entire sims going down the excel sheet and moving each object either by "restore to last poition" or drag and drop then edit for the no copy ones.  

Link to post
Share on other sites
On 1/12/2021 at 1:50 PM, Monty Linden said:

I'm going to assume you mean the desktop app is failing with that message.  One thing LSL doesn't yet provide is a fixed point where pieces of a distributed, scripted system can go to find the other pieces.  This usually means a small service on the internet where the pieces can register and search for other pieces (and do license checks, etc.).  Looking at the installation instructions, for the HUD, I'd guess that this function is associated with the 'AOS-Extreme: Object-DNS successfully updated:[200]' line in Local Chat.  If you are still getting this status, there's a good chance that part is working.  If not, the HUD needs a patch.

If the HUD is fine, problem will be either with the service or the desktop app or both.  There are some debug modes and interesting buttons ('CM') on the app.  Look for clues there as to what the app thinks it is trying to connect to and where data may be corrupted.  Look out for truncated hostnames in particular.  If the app lacks sufficient debug capabilities, you'll need to look at environmental tools to tell you what is happening:  Wireshark, syscall tracers, etc.  Those will inform possible actions.

 

Thank you, this makes total sense. 

Link to post
Share on other sites
On 1/13/2021 at 8:33 PM, Rolig Loon said:

My own scan object, which I have sold in MP for years, is clunky and brute force, but it works.  It's just a spherical object, essentially a drone, that hops all over the region, following a grid pattern and doing overlapping 16m scans.  It stores everything internally, cleans up duplicates, and dumps a report out at the end.  I made a second one that makes a series of vertical hops from ground level to 4000m.  I've never taken the time to make either version very sophisticated, so they don't send data to a remote server or anything.  Designing something like that is pretty simple.

TYSM,  I'll check it out.

As an aside, why doesnt' Area Search work better? It's not possible to find all objects within a specified range without using drones?

There's nothing in SL that does what Conover's program did, so far as I can tell.  The usefulness of an Excel sheet that lists every object in a sim giving locations, owner, group assignment is just fantastic when moving parcles, repairing areas, finding objects, or seeing what other people have littered on the land.  

Conover.jpg

Edited by Knobs Slade
Link to post
Share on other sites
2 hours ago, Knobs Slade said:

As an aside, why doesnt' Area Search work better?

That would be a question for Firestorm developers, wouldn't it?

AFAIK, the nearest approximation in the Linden viewer (and present in all others too, I suppose) is Build / Pathfinding / "Region Objects" which can list all the stuff you could move around (mostly your own stuff). Catznip (at least) also has World / "My Objects..." which is really limited to your own stuff but has more handy filters. These don't find all other folks stuff, but I've nonetheless found them very useful for finding items I've accidentally strewn about the place. Unfortunately, whether Linden or third-party, SL viewers seem to eschew APIs at all cost, and even (for now?) only rarely offer text copy-to-clipboard at all. Not gonna get a spreadsheet that way.

There would be enormous utility in an LSL function that could fetch batches of all objects in a region, filtered by owner and parcel and probably other "Area Search"-inspired criteria, without needing to rez a probe and push it around while managing llSensor ranges and angles to try to stay under the 16 item return limit.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...