Release and plans update (Patreon)
Content
Hi all-
I know it has been a while since I last posted. My apologies for that. I needed to take some unplanned personal time off after the last release to recuperate and reset. This project does not exactly have built-in holidays or downtime, and I often work 7 days a week, so I take time off as needed when I feel I am not being productive or over-stressed. The last release (1.20.0) was a lot of work, and I was beginning to stress a lot about spending too much time on VaM and not enough on VaM2. More on that later in this post.
So, what has been happening on this project since the last release (1.20.0.10)?
- I took about 2 weeks of time off. The rest of the team continued to work on VaM and the Hub
- 1.20.1 work - this release is all about Hub integration and is nearing completion. This release will also include some bug fixes and tweaks based on feedback since 1.20.0.10. Please note the Trello board has not be actively kept up to date but will receive some updates over the next week to reflect the changes.
- VaM2 work - rewriting of some of the core VaM functionality from VaM
- VaM2 work - feature and roadmap planning
- VaM2 work - technology research and development (DOTS, Unity versions, HDRP)
- New 1.20.1 and Hub feature (already released): dependency tab on resources to make it much easier to get all the pieces needed for the resource to work as designed. A lot of the work behind this also applies to the Hub integration into VaM in 1.20.1.
- New Hub feature (already released): Promotional link for Hub Hosted resources. This allows creators to share a link to an external site while still uploading a var package directly to Hub. This makes it easier to get the download, while still providing a way to promote the content. The upcoming 1.20.1 release of VaM will take advantage of this setup more fully than what is shown on the Hub.
- Hub tweak (already released): The star-rounding for reviews was not quite fair. For example, a 4.99 average rating would show up as 4.5 stars. This has been tweaked to be fairer.
- Hub tweak (already released): Externally linking to Hub was not allowing for proper preview. This was fixed so links made to Hub from Discord or other sites can now show a full preview with thumbnail.
- Ramp up of an additional part-time developer for the team. This new member will help with both VaM and VaM2 coding going forward.
I have personally split my time since the last release between the Hub, VaM, and VaM2, making progress in each area slower. And this leads to the next important topic.
Change of plans for 1.20.2 (Scene Wizard) and VaM2
The time off gave me a chance to reflect on what is important for this project going forward. It is quite clear VaM2 needs to be the top priority. VaM2 is getting behind where I had envisioned due to ongoing VaM development and the Hub. VaM needs to stop interfering with VaM2 work to prevent further delay.
VaM has also reached the point of polishing something that will never be optimal due to being stuck on older technology that limits both performance and appearance.
VaM2 is the chance to fix some core issues in VaM and bring 3 years of new tech into VaM. VaM2 will be a complete rework or rewrite of VaM code, systems, and assets, some of which is already complete. The goal of VaM2 is to improve all aspects of VaM: performance, appearance, functionality, and usability. VaM2 will feature newer tech like Unity HDRP (for vastly improved appearance), Unity DOTS (for vastly improved physics performance), revamped GPU physics for cloth and hair, support for newer and different models (Daz3D Genesis 3 and Genesis 8 as an example), and possibly other recent technology advances like raytracing, if feasible.
Since VaM2 needs to be the top priority going forward, we have made the decision to shelve the development of the Scene Wizard for now and cancel the planned 1.20.2 release which was to mainly feature the Scene Wizard functionality. Instead, some of the team will continue to make improvements, tweaks, and bug fixes to VaM in the form of new VaM releases further out in time, and I will personally be moving full time to VaM2 starting immediately after 1.20.1 release is complete.
I hope everyone can see the value in this reset of plans and the decision to put priority on VaM2. These decisions are not easy to make, but we feel this is the right one at this time.
Thank you for your ongoing support to ensure the future of this project’s success!
Meshed and Team