Profaitchikenz Haiku

Or, throttling if too many messages have been sent. I've had this before with a railway system that sent messages to and from vehicles, signals and stations. My suggestion is prior to sending the message, count the total number of characters in the concatenated strings, including the seperators, which amongst other things will warn of a string-truncation problem. Send the message. The receiving object counts the string and sends as a reply to the sender the number of characters it has received. The sender needs a queue of messages , recipients and lengths, and only removes a message from the queue when it has got an expected reply.

Ditch Windows, use Geany or Gedit

It's not shown as the beta version but it's here ETA correction, it looks as if the last version of the older Qavimator was re-committed in April this year, the version numbers don't match what I have on my machine.

One of my cats created an account and was trying to buy Meroo food but as it didn't have a paypal account the idea fizzled out. Apart from that, no, and I think I would find it a little strange if somebody I knew in RL turned up.

UDP was discussed a few times during last year's server user group meetings, particularly after LL turned off UDP use for body parts and animations, giving many oldies the white-cloud behaviour. It would be worth passing this question on to @Oz Linden because when I queried the use of UDP after the earlier announcement that UDP was now no longer used for avatar body parts and animations he replied that there were proper ways to use UDP. (or words to that effect) I can't recall what was proper and what was improper, though.

I started seeing something like this yesterday when TP-ing. TP failed, an attempt to try again got a message saying TP was currently disabled/not working, it wasn't possible to move around, attempts to IM failed, ultimately I crashed out. It happened about 8 or 9 times, on both Firestorm and Catznip, both normally very stable viewers for TP-ing.

I want cookies for life, not just Christmas. I got asked on the initial browser startup, then again when I tried the search, and again when I used the built-in browser, plus of course logging into the web site, but I haven't had a repeat. Guessing from what else you've found with the firewalls, are cookies being deleted too soon from your PC?

It's not just them, it's everybody, and it's annoying the hell out of me. The BBC news site periodically insists I once again agree to their cookie settings. I suspect it's to do with site revisions or updates that either wipe out saved details or else somehow trigger a "we have to do this because of legislation" thing. I just wish that once they've got your agreement to set cookies they'd sat a dam cookie so they don't have to periodically ask you if it's Ok to set a cookie. Glad to hear you sorted out the problem.

Oh dear, search works fine in the LL viewer. So maybe it really is ----- (long drawn out drum-roll) --- the OP's machine? It took a short while before the mini-browser got pictures and text on the screen, and I had to accept a cookie agreement popup, but it found places quite quickly. There might be some preference settings that have to be tweaked in the web-browser section? ETA just checked and there's just radio-buttons for opening links in the default or built-in web browser which had no impact on search when I toggled it. I have to say the delay between clicking the search button and the subsequent window clearing from empty black to text and colours would tempt me to cancel the operation and assume search was broken if I was in a bit of a rush or had expectations greater than I already have of the viewer. ETETA I tried Catzip, it was the same as the LL viewer. Just out of interested as well as "Places" I tried the "Web" tab and found that I had to log in before I got Mature and Adult checkboxes to respond. As with the LL viewer I had to agree to cookies.

Sadly, you'll not like this, but search is working quite happily for me in Singularity. The LL-viewer issue could be due to the recent web-upheavals, the LL viewer uses a web-based search that always seems to take ages to wake up, as does trying to open the preferences. I would use the LL viewer more often if they made it more responsive. Just waking up the second machine to try the LL viewer search.

The Context editor has an LSL syntax highlighter that is often updated by builders Brewery, it works well enough for me.

I thought everybody saw it, but they all would see different rotational angles as their viewers would have started the rotations as and when, not synched to a server message?

Logged in from the UK with no problems, looks like it's chunks of mainland europe? Have a look for rabbit tooth-marks on the transatlantic fibre cables?

I stay with the day cycle unless I'm building, when it's vital to have sufficient light to see seams and edges and gaps that would be harder to spot in the dark.

A slight problem here (although I admit I was impressed with the proposed hack). A 512 by 512 image needs 262144 pixels. Creating a mesh square tile with 8 forward-facing individual faces would reduce this number to 32768 prims, but region prim-limits are going to bite you in the bum. A 64x64 image could be done this way using 512 prims, which is actually doable in most areas.

Some sort of algorithm working out what can be seen and what is occluded by intervening objects? Staring into the void presumably clears the working space, turning around causes a rush to populate it. I always assumed that the viewer code not only looked ahead but looked to the sides and behind the direction of the avatar face, to keep an interest list populated. Lately though it feels as if so much priority is given to what's directly in front of you that there's no spare time left to keep track of what's behind. Maybe some coders with an insight into how the rendering is organised and prioritised can enlighten us.

Yeah, rattle that agenda

The simplest solution is to have a different viewer, the builder has one and the explorer another, each gets a unique cache. Trying to define two different caches for one viewer is awkward, but not impossible. It requires having two folders, one for each avatar, and whichever avatar is not logged in has the cache folder name altered, say by adding the avatar name to the end of it. The cache file for the avatar which is actually logged in does not have the appended name. You have to remember to rename the folders before logging in with a different avatar and it's easy to forget and mix them up. Assume the viewer in question has a cache folder MyCache. Create two folders MyCache_avatar1 and MyCache_Avatar2 Before logging in avatar1, rename MyCache_avatar1 to MyCache. After logging out avatar 1 and before logging in avatar2 rename MyCache to Mycache_avatar1 rename Mycache_avatar2 to Mycache Login avatar 2 Different viewers is much easier.

And pursuing them carrying a piece of smouldering turf is a fine old Northumbrian tradition

Isn't this rustling?

First, turn on physics shapes (in the same area where you turned on wireframe and bounding boxes) and look for a blue or green shape where you would not expect it. Assuming there is still no obvious block, edit the house and raise each child prim up a set amount on the Z axis, say 10 metres, until you are able to walk through without hindrance. The prim you just lifted will be the problem one. There are a lot of possible causes,. from a mesh item with poor physics to a path-cut mega-prim, but this is the only way I know to track down the problem when there is nothing visible in the physics. Start with the obvious ones in the vicinity of the problem and expand outwards. When identified, you might be able to cure the problem by setting the particular child physics to none. Once you're done, edit the house and lower each child prim by the same amount you raised them.

Is this a distance problem? Instead of using Say to chat the command, try a shout in case you are more than 20 metres from the centre of the particular blind.

First thing that is noticeable is that the vector you are giving after PRIM_POS_LOCAL looks more like a region coordinate, change PRIM_POS_LOCAL to PRIM_POS. Also, PRIM_ROT_LOCAL is probably redundant. My suggestion is to add a line to each of the two functions so that it tells you when it enters each of the two routines using llOwnerSay(). Tell the blind to close, observe that it has closed, then go around the other three blinds closing them. Come back to the first blind and observe it. If it looks open, tell it to open and see what both the visual result and the report from ownerSay gives you. Then close it and observe the results. Is the order in which you go round the blinds closing them always the same? Does varying it change the behaviour? To rule out Firestorm I'd suggest repeating the tests with the LL viewer, because if somehow you have discovered an issue with the server (or client) code it will help to establish if it is viewer-dependant. If you have indeed found a situation where a prim changes size and position but then reverts to an earlier size and position for no good reason this is definitely reportable.

I'd claim it was a segue, not an escalation, but yes, I'm amazed by just how much it did wake the thread up Niran's suggestion of saving up for parts is what I have been trying to achieve, the issue comes not with putting in a different graphics card but in finding that you can't really upgrade from Windows7 to Windows 10 if your motherboard is capped at 4GB Ram. This is where I am so grateful to the TPV's maintaining 32-bit versions of their viewers, I can just about scrape by that way. In a bit of an anti-swerve... let's get back to texture memory @) I am currently able to get onto sims that aren't too busy with mesh avies or have hundreds of buildings with diffuse, bump and specular textures all at 1024x1024. In fact, I can even run his Black Dragon viewer in 4GB of Ram with care. I have previously asked about the significance of texture memory because of some graphics driver failures, but I have now discovered the GTX1050s sold quite cheaply on ebay are chinacanery, they're not genuine and tend to fall over when passed a hefty list of big textures to get loaded. I have tried drastically reducing the texture memory setting to see if that slows down the rate at which textures are given to the GPU ( I was going to say thrown but that's a bit unfair). I would like any advice about how to work with what I've got rather than what to save up for because I'm now reluctant to commit to anything that might end up to be of chinese origin even through the ebay seller is supposedly shipping from the UK.

But not grown-up sophistication. And being honest, if a teen has the intelligence and wit to be able to pass themselves off as an adult, doesn't that actually say as much about them as any genuine ID method?