From the Server and Scripting UG we hear about more region crossing work. Simon Linden is doing some work on crossings. BUG-214653 – After half-unsit at failed region crossing on vehicle due to network lag, “Unsit” button will not work.
Crossing regions at speed… fast cars, planes, boats, and motorcycles, have a big problem. I was recently testing an Apolon helicopter. Great fun. But, region crossings are an annoyance.
This week was a <15-minute meeting. So, not much news.
On the viewer front, there are no imminent updates. So, we likely won’t see any RC or Project viewers changing status this coming week.
All I ever wanted.
The new server-side capabilities were deployed. The viewers haven’t been released. They are still being tweaked. The Abuse Report category change from built into the viewer to delivered by the servers hickuped. The Lindens left out the ‘localization’. Oops. English only. That is being fixed.
Bakes-On Project Viewer passed QA, Oz was unsure of when it was being released (ta-da: released 3/30). See the release notes.
BUG-215951 – Option to allow nearest neighbor on textured faces. The feature request was rejected. So, this is an example of what a definite Linden ‘no’ looks like.
I take it that some core functionality in the render engine would have to change and the Lindens don’t see an acceptable benefit ratio.
The Lindens are aware of an HTTPS problem for those scripting HTTPS data transfer. They plan to fix it, they just haven’t gotten there yet.
That is about it for the meeting. This link to the video leads to a very quiet meeting this week.
It is Tuesday (well, would have been if I had remembered to post this…) and the main channel was updated to version #18.03.14.513292. The changes are the ever-occurring Internal fixes then logging to help diagnose an issue with in-world HTTP servers returning HTTP 503 (BUG-214702), adding a new capability to request IMs that were delivered to the requesting agent while the agent was offline, and adding a new capability to request the most up to date list of abuse report categories.
Yellow Bag
Until we have a viewer update that can use the new caps, we can’t see or use the new additions.
Wednesday, the Blue Steel channel will be updated with version #18.03.17.513365, ‘internal changes’.
Le Tigre and Magnum may get an update. The Lindens had not decided on a version as I write this. The entry for these channels is a little confusing as they show the #18.03.14.513292 version, which I suspect many will assume is an update going to these channels. But it went to the main channel and may remain in these RC channels.
Le Tigre and Magnum update to #18.03.14.513292. Internal fixes, logging to help diagnose an issue with in-world HTTP servers returning HTTP 503 (BUG-214702), adds a new capability to request IMs that were delivered to the requesting agent while the agent was offline, and adds a new capability to request the most up to date list of abuse report categories.
These ‘adds’ will require a viewer that can use them. Which I assume is somewhere in the QA pipeline.
I wanted to sit in on this week’s Third-Party Developers’ meeting. I wanted some footage of the meeting to use as an opening for my summary of the meeting. I was late. Seems to be a pattern. But, I was planning to use Pantera Północy’s video of the meeting. It comes out Saturday morning.
I was surprised to find Ebbe Altberg talking! Whoa! So, I brought up OBS and recorded the rest of the meeting. The first 15 minutes are missing. Those minutes are in Pantera’s Video, which came out before I got finished.
I’ve been having audio problems with the SL recordings. I got some of that cleaned up. I still had problems but the audio is intelligible and better.
I thought about indexing the video. I usually do. But, Thursday is an RL busy day and I already have a work-related video rendering in the background. My completer is WAY sluggish and all 4 cores are pegged at 100% heating up to 57. This one of the few times I hear the fans pick up speed. So, I’ll do the index later when I don’t have to deal with pauses.
The video is jerky in places. I was recording and had the rendering paused. But, I was still seeing a hit in the viewer. My i5-6600 did pretty well considering the load on the system.