It’s time for another release of Radegast; this time with version 2.54. This version brings many under-the-hood updates and changes. Still wrangling in memory use and fixing deadlocks that caused freezing. This version drops Vivox support in favor of WebRTC. However, the WebRTC does not work reliably due to underlying library issues with .NET 4.8.1. It is taking time to get the fixes upstream to SIPSorcery.

Offline IMs should now download correctly. Autosit should work again. There has been another round of inventory robustness changes and appearance changes. Client baking (OpenSimulator baking) should once again work. Shape morphs are applied in 3D Scene which has been broken for about 16 years. Alphas are also correctly applied now. There are various other small changes, and it should certainly be a better experience for those running v2.52 or previous.

Looking ahead, we are on the precipice of releasing a total rewrite of the Radegast Viewer from near scratch with a new modern UI and fully working cross-platform and architectural compatibility, many new plugins, many neglected and unimplemented features from Second Life (things such as pathfinding, GLTF materials, Animesh, etc. As always with a text-first focus ond accessibility and automation (bots) as first-class features. So be on the lookout for a beta soon!

For now, this is Radegast, and I hope that you enjoy the changes. Any bugs can be reported on the Issue Tracker, and downloads are available here.

For those wanting a quick link, if you are running a Windows PC with a 64-bit processor (very very likely unless you know otherwise), this is the installer for you.


Leave a Reply

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

3 responses to “Radegast v2.54”

  1. Camden McAndrews Avatar
    Camden McAndrews

    This all sounds great, but I still don’t see any mention of being able to disable the extremely unwelcome feature that processes text into emojis.

    That “feature” is (1) ugly and (2) makes it impossible to send code in Radegast text IM. We have had to revert to a very ancient version of Radegast to get it working again.

    Regarding a new UI: Make sure you’re doing things because they improve the performance of the software, and not simply because you can. There have been times these past few years where I daydream about running amok at Microsoft, taking a sledgehammer to their keyboards.

    ANY change to a familiar UI is a huge negative, requiring a very compelling positive benefit to offset the loss of the user’s investment in learning and developing expertise with the UI.

    1. Cinder Roxley Avatar

      Thanks for the feedback. On the emoji/smiley text substitution: that feature was added last year, and yours is the first request I’ve seen to make it toggleable despite every release post pointing to the Issue Tracker for exactly this kind of thing. Not a single issue asking for it, until now, in a comment section. If it’s breaking your ability to send code over IM, file an issue with specifics; what you typed, what it turned into. That’s worth more than “extremely unwelcome,” which tells me nothing except that you’re annoyed.

      On the UI: the sledgehammer-to-Microsoft’s-keyboards line is bringing a lot of rage to a free hobby project maintained in spare time by volunteers. The rewrite isn’t happening because “we can” — it’s driven by cross-platform support, fixing genuinely old architectural debt, and features the current codebase can’t support (pathfinding, GLTF materials, WebRTC, Animesh, better automation tooling). A new UI is a side effect of that work, not the goal of it and rewriting a seventeen year old WinForms app in Avalonia MVVM is of no interest to me. If you’ve got specific, concrete concerns about what might get harder to use, raise them during the beta; that’s actionable. Vague objection to change on principle isn’t.

  2. Kabalyero Avatar

    Things that were broken are working again but the client exits in Scene Viewer. Thank you.