VulkanSceneGraph-1.0.x series RoadMap

[robertosfield]

This thread is discussing what happens next for the VulkanSceneGraph and companion projects over the coming months, for me this broadly fits in to maintenance of the VulkanSceneGraph-1.0 series, and work on new features that will go into the next stable release which will be 1.2, I'll start a separate thread for this new feature development.

Maintenance work on the 1.0 branches

On the maintenance front I have already a fix to vsg::CollectResouceRequirements so that it handles the new vsg::VertexDraw node, and a number of CMake related fixes/refinements, this changes made into VulkanSceneGraph master, but I've now pulled these into the VulkanSceneGraph-1.0 branch. The changes are:

#594

The changes to vsgXchange are the addition of a vsgXchange::curl::SSL_OPTIONS value that can be passed in via vsg::Options and defaults to CURLSSLOPT_NATIVE_CA under Windows to work around issues with reading https files, and the assignment of assump node/mesh names to the corresponding VSG objects via Object::setValue("name",name), something that useful for matching VSG objects to elements set up in a modelling tool. The changes don't change the ABI so should be fine to merge with 1.0. The changes are:

https://github.com/vsg-dev/vsgXchange/pull/133/files

Finally we have some updates to vsgExamples, initial build fixes for the Android example, and to the vsgintersection example the addition of console output of "name" values assigned to objects in the scene graph hierarchy of intersections. The changes are:

vsg-dev/vsgExamples#189

I expect as the VulkanSceneGraph-1.0.0 gets tested on more platform/build combinations and with more hardware and applications will see other build or bugs appear and need to get fixed. Reporting these problems on the repetitive Issue trackers with details on how to recreate the problem will help us investigate and resolve the issues that appear.

If you do come across an issue, have a look at the Issues that already have been resolved and if it looks like it might be fixed try out the VulkanSceneGraph/vsgXchange/vsgExample-1.0 branches to see if it's been addressed.

In general testing out these 1.0 branches will become more helpful to us as we approach 1.0.1 release. I don't yet have a plan for when this release might be tagged, it all depends upon if anything critical comes up and the benefit of pushing fixes out more widely vs time for us in the community to do all the build and runtime testing prior to a path release - I appreciate that all this testing takes time and effort, so don't want to burden the community on a constant cycle of testing.

Provisionally perhaps a 1.0.1 in December or January. Welcome input on this.