Build Announcements

Visual Assist 2022.2 is here

Visual Assist 2022.2 has just been released! We have a well-rounded update this time— a number of new features as well as some much needed fixes.

Unreal Engine 5 Support

The biggest announcement in this release is the the start of official regression and other testing related to Unreal Engine 5. This also comes with some modifications to the IDE UI to make it apparent that our features work with both engines.

We’ve also updated VA’s  behavior when used alongside Unreal’s core redirect function. This adjustment allows UE devs to rename classes in their C++ code and allows their Blueprint code to find the renamed classes by editing a redirect file for them. 

Visual Studio 2022 Icon Updates

Visual Assist in Visual Studio 2022

Visual Studio 2022 introduced some style and UI changes so Visual Assist’s UI (no matter how sparse) has been updated to complement those changes. Bonus: This was admittedly the most difficult part of the release according to our amazing dev team. 

Here’s what it looks like in the IDE:

Complete view of Visual Assist 2022.2 in Visual Studio 2022

More ubiquitous code assistance

A few of Visual Assist’s popular code assistance features now work in more file types by default. For example, sorting selected lines will now work in plain text files (they were only active in source files before). Spell check will have some UI prompts (shown as underlines) that will now appear by default.

Code Inspection improvements

We also added some code inspection improvements. The first checks for an easy-to-make mistake where std::move does nothing, where it should speed up copying of a type.  It will now detect and correct a few easy and potentially performance costing mistakes when using std::move.

The second check for performance-move-const-arg validates user defined move constructors to ensure they are properly marked noexcept, which would prevent them from being used.

Some notes from our dev team

This release caps some long-term items we had in our pipeline. In the future, however, we would like to revert to working on less long running tasks. This helps keep our small team’s development direction agile, and thus allows better and prompt answers to user expectations.

So, if you have any suggestions, or encounter anything that needs a fix, please send support a message or post on our user forums.

For more information about the changes in this release, please read the documentation.

Happy coding!

Related posts
Tips and Tricks

How to Query File Attributes 50x faster on Windows

Tips and Tricks

C++ versus Blueprints: Which should I use for Unreal Engine game development?

Tips and Tricks

Getting started with how to use C++ for embedded systems in financial services

Tips and Tricks

The biggest challenges in writing C++ programs for finance and banking

Leave a Reply

%d