It’s time for another release of Radegast: version 2.55. This one leans into the unglamorous-but-necessary side of maintenance: dependency updates, crash fixes, and a handful of accessibility improvements that have been long overdue.

LibreMetaverse got bumped several times over the course of this cycle (3.2.0 through 3.3.1), picking up fixes along the way, and the NuGet dependencies across the board have been refreshed to their latest versions.

On the fix side:

– Relogging into the same region after a disconnect no longer leaves stale appearance/COF state behind, and multi-factor auth now carries through the reconnect flow properly.
– A stack overflow that could occur when the grid’s seed capabilities kept failing to fetch is now handled gracefully instead of crashing.
– Group chat participant lists no longer crash on refresh.
– The active group is now properly exposed to screen readers, alongside accessible names for the IM, group, and conference tab controls and the profile picker buttons.
– Typed-but-unsent text in an IM window is preserved when a new tab or notification pops open, instead of getting silently wiped out.
– Join Voice is now disabled outright when a parcel or estate doesn’t permit it, instead of letting you hit a confusing error. Parcel audio also no longer restarts itself if you’ve explicitly stopped it, and a round of leak and state-tracking fixes landed in the voice console.
– The streaming media title now tracks the artist tag separately, so now-playing text updates correctly when a new tag comes in.
– A sound upload that fails outright is now blacklisted for the rest of the session instead of being retried forever.
– The portable/tarball download was quietly missing some runtime XML data; that’s fixed now.

Thanks to Ruben Santos for several of the fixes in this round, including the seed-caps crash, the group chat crash, and the relogin/COF leak fix.

As always, downloads are available here, and if you’re running 64-bit Windows (which, these days, is almost certainly you), grab this installer directly. Bugs, as always, go on the issue tracker.


Leave a Reply

Your email address will not be published. Required fields are marked *