July 2026 VaM2 Development Log

In our last post we mentioned the next post you would see from us should be the announcement for VaM2 Beta1.2 release. We worked hard this last month to try to meet that goal, but we are not quite to completion.

We have decided to take another week for more polish, bug fixing, and to include additional addon content that is now ready, but needs final testing before inclusion.

What is left:

• (4-5 days of work) Final bug fixes and polish. The current BUG count is 5, and the current usability items count is 7. For reference, over 60 items (both bugs and polish) were completed in July, and the new bug discovery rate has dropped dramatically.

• (1-2 days of work) Review and final packaging of additional addon content already completed by our asset manager and developer, VaMDeV. This is content that is complete that just needs a final quality check to be included in the release.

• (<1 day of work) One last Unity update. We want to update to the latest Unity 6000.5.6 release that was released last week. We are still testing on an older 6000.5 release. This is a minor update and should not cause much delay.

Some details of a few unplanned things we addressed this last month during testing and polish:

• UI clarity in VR: The UI in VR is rendered inside the world itself as this makes it the most usable for VR. There were a number of problems with this, like pixelization and being affected by DLSS and other post process effects, making the UI hard to read in some circumstances. We added a custom VR UI rendering pass that allows the UI to be rendered at 2X resolution and downsampled (basically SSAA) to reduce pixelization, and then renders after post-process and DLSS to prevent those effects from altering visibility. This gives much better clarity and overlays the UI on top of regular game objects while still maintaining the UI in the world itself so it can be freely moved around you.

• Customization of VR UI and UX: In testing, it became clear we needed more ways for users to customize the experience for comfort of use, so we added more customization preferences for VR movement and how the VR UI looks and feels to interact with. VR devices also come with different controller button, thumbstick, and trigger variations that were not accounted for very well in the VR toolkit we are using, so some additional work was needed to account for that. We will add more preferences over time to optimize the VR experience for everyone.

• Added more DLSS preference options to select specific presets (J, K, L, M) within each DLSS performance level. During performance testing we discovered a performance issue related to DLSS and root caused the problem. M is the default for Performance and L is the default for Ultra Performance in Unity's Nvidia plugin, but both of these presets can actually hurt performance on systems not using 4xxx and above Nvidia GPUs when operating at high resolutions (like 5K desktop and VR headset resolutions).

We are looking forward to getting this VaM2 Beta1.2 release out to everyone. Thank you!

Meshed and Team