WolfBaginski Bearsfoot

I'm having some odd experiences, I'm not sure which version of the Server code is involved, but if it continues, I'm not sure where the fault is. Place: Kaili region, on the road which runs Laka-Kaili-Poliahu Symptom: Sim-crossing failure with a vehicle, Initially, it seems to be a severe instance of rubber-banding, but then the vehicle vanishes, and the AV "sticks" close to a region boundary. Often, it's reported as still in Kaili region, but with an out-of-range coordinate. A TP is possible, but movement controls are partially locked. Sometimes, after ten minutes or more, the location is corrected and the AV is placed where they should be after the sim-crossing, but the vehicle has vanished. There look to be several abandoned vehicles on the landward side of the road, within the Kaili region. If this does happen. AV movement appears normal. Of the three regions, Laka is BlueSteel, Kaili and Poliahu are LeTigre. I have seen similar events happen elsewhere, but this is the only place I can be sure it happens every time. All I can think of is that something within the region is running with a horrible number of scripts. Or, maybe, we gace hardware in two distinct server centres.

I've been around 1920s Berlin a few times, getting a feel for what things look like. You can't walk around a corner when you're looking at photographs. Not even in SL, some of the writing I do is in a furry version of 1930s Berlin. That awful Reinhard Heydrich chappie is giving foxes a bad name. But it wasn't me who made Dr. Goebbels a turkey.

I know what late nights do to my thinking, so I think you made the right choice there.

I think the RC rollouts might have happened, but there's nothing on the Status page. It looks as though the LeTigre sims have been put on the same code as MC.

Right now there are things happening which make the Viewer you have unreliable. I use the Phoenix viewer, which is reliable and not too different. Check for Avatar Physics support: not having that can mess up a lot of stuff, even if you have no interest in bouncing anatomy. Various other things are changing, and server support for the old-style search, profiles, etc, will vanish eventually.That will hit Phoenix, and anything else not based on Viewer 2 code. So Phoenix isn't so good an answer. Viewer 2 is very different. I hate it, not just for that reason. At the moment I'm using the Firestorm Beta, which is Viewer 2 family, works well for me. If your machine can support it, I would recommend a move to one of the Viewer 2 family, but Firestorm is the only one I've found usable. If you do use the official version, make sure to switch it to Advanced mode, right from the start.

There's a few wind-sailing craft used by the "pirate" types, but maybe a bit modern for what you want. I've also seen a pilot cutter in-world, late 19th Century, and a few small craft that might do. The TSS ships use Linden wind, which can be awkward. https://marketplace.secondlife.com/stores/18842

I'm looking for a good motor-cycle. I'm willing to spend, but I see a lot of bikes on the Marketplace with little or no info about how well they work, I can split the spec into two parts: Part 1: Appearance I'm looking for something in "classic" style, the sort of general look that emerged with bikes such as the Indian and the Brough Superior in the 1920s, and lasted into the 1960s. I'm not looking specifically for a Harley, but that's typical of the period. I'm not looking for "custom" bikes, or the modern machines with alloy wheels and streamlined cowlings, nice though they are. Part 2: Technical Suffice it to say that I have a good-looking bike, pretty much in the style I want, which is horribly over-scripted, and so almost unrideable through a sim-crossing. a: If it uses scripts for changing colour, it should be possible to remove them. b: since I'm in Europe, with ping times of around 250 ms, steering should be either adjustable, or a little bit on the low side of effect. c: it should run without a fancy HUD. It's not just scripts on the bike that are a problem. d: I'd like the sound to stick with a fairly steady engine note while moving, not as if you're blipping the throttle as you flick through the gears. I want something that works for cruising, rather than racing around a track. Much of the time, in my experience of vehicles in SL, "gear change" is effectively the throttle, so the access to that should be simple. Currently, the combination of connection-lag and sim-crossing problems leads me to prefer a low-speed, close-ratio, set of gears. I'm never likely to have fun at 60mph.

I did see the same missing Status problem with Opera. The timestamps look odd, maybe something went wrong.

Looking good so far. Sim crossing is less glitchy, and I went through a very busy sim without any major problem. Script times don't seem to be crazy

The sim-crossing problem is certainly related to the general Mono-script problem. Physical vehicles need scripts, and however they come into the region, the Mono-problem applied. The Sim hesitated. Add the complexity of actual sim crossing. The Mono-2 fix does make a big difference. But I've also paid for some thoroughly awkward vehicles, things like scripted colour changes with no way to remove the scripts which do that. It makes for a lot more data to transfer from sim to sim, and that doesn't help. There's clothing items which do the same. There are better ways of handling the problem now, but a couple of years ago the onlt usable method was to put a script in every prim. As far as I've been able to find out. it things do run slow, you can temporarily be at one of several "wrong" locations within the new region, depending just where in the transfer cycle yoiu might be. And where the Sim thinks you are may have little to do with where your Viewer thinks you are. It doesn't help if one of those temporary locations is protected by ban lines or security orbs.

I don't know what you plan to do next week, but I think you've managed to bust things big-time. The Mono-2 fix seemed to work, at least on Mainland. Sim crossings were not perfect, but they worked. I was able to drive significant distance with only minor rubber-banding. But there was that scripting problem which was revealed. Since you fixed that, Sim-crossing has become as bad as it ever has been Sometimes sims behave as if they're just not there, and if the viewer doesn't crash, the only thing to do is log out. I count myself lucky if I can make a half-dozen sim-crossing without disaster. If you can't fix problems as basic as that, why should I expect Mesh to be worth the trouble.

It is possible to run something pretty easily. Just google on simonastick That's a complete Windows distribution which can run off a USB stick. Without access to the Asset servers, it's a bit limited. It needs a lot of work to set up an environment, The scripting might be awkwardly different, sometimes. But you don't need any connection to the Internet to run the server. I can see it being useful for some things. I don't know how the land tools compare, but if you can do the same things with an SL Private Island, you can test the planned terrain before you ever have to start paying tier.

It's a tangled mess, but since 16-year-olds can lawfully bonk their brains out in RL, here, maybe it doesn't matter so much what they do in SL.

I've seen nothing more than high script times, but have you checked the RC server code is clean?

You obviously don't read everything I write about the Lab. It is not unknown for me to get a trifle heated. I can use all the tricks, dramatic irony, metaphor, bathos, puns, parody, litotes and... satire. I can make a few wild guesses about why this wasn't spotted earlier. And the communication could have been better. But they're getting a fix out, and I've not seen any sign of the fix breaking something else. So I find it hard to get emotional about this. I know enough to know that I have no chance of understanding the details. It's not impossible that the server code is a tangled mess of accumulated crud, which is the very devil to work on. I wonder if they even know enough to write the specification for a Server 2, in the way that they obviously did for Viewer 2. But this time, they are getting the job done. Which do you want? Grovelling apologies, or working code?

Looking good at the highest detail-level. The strip pattern has gone. Not sure that the system is fully working yet, but things are definitely more usable.

The JIRA system is part of how they manage how they fix problems, so I don't see a problem with that. Some companies, we wouldn't even see that much information. It does seem strange that, with both pre-release testing and the RC stage, this wasn't spotted until it went out on main channel. But we don't know about the things which don't get that far. I reckon they're working pretty fast on this, but their communications could be better. Look at the notice on Status. Thinking back, I might have spotted something was wrong last week, but I was in a place where the script-load varies a lot anyway. But I was on the right RC and seeing high script times.

I've been noticing problems for nearly a week, and with different Viewers. It's great north-south strips not loading across the whole map. Sometimes the gaps are filled at lower resolution, sometimes not. I don't speak JIRA but I did put in a support ticket.

The estimate for my local County Show was 65,000 people. The timezone I'm in, I might not see the peak figure for SL, but I've known things start to feel laggy when things are that busy. Oh, and Baloo, about HTTP textures: other people tell me that turning it off will speed texture loading It rather sounds as if changing texture-loading method is seen as a magic button, fixing the problems whatever the starting position in. And that just doesn't make sense. Oh, that must be the magic of SL that they were all going on about.

And I see a definite improvement in Sim-crossing with vehicles.

I look forward to trying the Mono2 fixes. Sim-crossing with vehicles has been a tad dodgy sometimes, and I assume that getting this on the Main Channel will make a difference I will see,

OK, they're very different events. And the RL County event can handle far more people than the whole of SL can. But, several times, I was acutely struck by the differences. 1: The County event is easier to navigate. Some parts of the show have been in the same place for decades, because they use specialised buildings and other permanent features. But there has been a consistent broad layout pattern for as long as I can remember. Certain types of trader have been in about the same place for over thirty years. Add to that clear signs and markers at the intersections of the grid pattern. SL8B has more detailed information in the coordinate system, but in-world it can be confusing enough to figure out which direction you're facing. "SL8B Marvellous" Which direction is that from where I am? It's a tricky balance in VR, because we do have maps. and maybe Landmarks, but after a few minutes of walking around at random, I felt confused. No sun shadows and (see later) no distant landmarks. 2: The lag didn't help. There's no avoiding it, but it's likely that people with run on lower-quality graphics just to be able to move around. Which means they're not seeing distant objects. Frankly, texture-loading generally seems to be slower than it was a year ago. That changes the whole dynamic of display and signage. And if you're not seeing from a distance, the high-up signs might not be in the field of view when the wall does rez. The eye-catching features of reality just aren't usefully visible. 3: Ever seen a Show Catalogue? A list of every stand, and every event? I've found event lists, but they're lacking. They're just times and names. I'm not big on the dance-halls and DJs and discotheques of SL, and there was nothing I could see that meant anything to me. (I can't say the gesture-spam at the events I did attend was any help.) Yes, there's the section in the Destinations guide. That turns SL8b into a point-to-point teleport tour of the selected highlights, and rest of the show becomes irrelevant. 4: While I remember the way the start was announced in the "Featured" blog, default on the Dashboard, and the amended details were hidden in "In World", including a different start-time, seemed a little careless. I'd sum it all up as poor communication Sometimes, it might be the stand designers, but I'm left with the feeling that the event, as a whole, hasn't been organised to make it easy for the visitors.

Yes, the non-existent region problem seems to have struck again, a couple of minutes ago, when crossing from Burandt to Miller, at the start of the road bridge. In fact, the scenery was slow to rez, then the bridge rezzed, and then everything vanished on the Miller side of the boundary, before I was translocated to Burandt (0,0,0), with nothing visible but a flat white plane, occupying Burandt region-space only, apparently with a snow texture.

My AV is maybe on the tall end of reality (not that it's exactly meant to be real), but I'm not one of the giants. In any case, we can have two distinct scales in many situations. There's the visual scale, based on avatar appearence, and scale effects arising from such things as Physics limits. Nothing can move faster than 572mph and that's an insane speed to try and cross a sim boundary at. Yet people making working models of rifles, and use them in simulated combat. The bullets move at around half that speed (there are quantisation effects), somewhere around 1/15 of the speed of a real bullet, maybe a dozen times the speed of an Olympic sprinter, so you have a lead a moving target is if it was a thousand metres away rather than a hundred, That sort of difference, weapon-effect scales and scenery scales, is commonplace in wargaming with scale models.

I think something has gone wrong, but I'm not sure I have enough data to pin it down, and I don't speak JIRA 1: All this has happened since the completion of roll-outs this week. 2: In some cases, I know the Le Tigre RC server is involved. In other cases I'm not at all sure which versions of the Server code were involved. 3: Both problems have been seen the current versions of Firestorm and Phoenix. That is, V1 and V2 codebases, both programs having worked well for at least a week before the problems started. Problem 1: A region becomes isolated from all adjacent regions, with nothing visible. I've had this happen with the Furness and Uzume regions. Problem 2: Region-to-region transfers, whether by teleport or by crossing the boundary, are sometimes incredibly delayed. This can lead to large-scale rubber-banding, up to 5km in one case By the time it gets that bad, it's likely to fail completely, with the Viewer exiting. It's clearly worse with scripted vehicles, and I have some which are decent, some dreadful, for the number of scripts used. Problem 3: Failure to initiate a group chat session. There's a initialisation-error message in Firestorm. No message in Phoenix, but the chat session doesn't start.