René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"QAPage","mainEntity":{"@type":"Question","name":"Software crashed when I run vsgExamples/examples/commands/vsgexecutecommands","text":"
When I run the 'vsgexecutecommands' example, the software crashes.
\nThe command line shows \"Using SecondaryCommandGraph and ExecuteCommands\",and the window displays a white screen.
\nMy operating environment:
\nCPU: Intel Core i7-12700
\nGPU:NVIDIA GeForce RTX 3060
\nRAM:32GB
\nOperating System:windows 11
\nEditor: Visual Studio 2019
\nVulkan: x64 1.4.335.0
\nVSG:1.1.11
\nvsgXchange:1.1.7
","upvoteCount":1,"answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"
I have reproduce the crash on my system with VSG/vsgExamples master and created a Issue for this bug.
\n
I then investigated the issue and found the regression was caused by the SecondaryCommandGraph's connection of the CommandBuffer and State objects not handling the addition of lazy state updating that was add to State.
\n
When I added the lazy state updating support (for performance reasons) I modified the the CommandGraph implementation uses the new State::connect(commandBuffer) function but missed updating the similar SecondaryCommandGraph code to use these new method.  This meant that CommandBuffer and State objects that needed to be connected in a particular way
\n
The fix ended up being very simply - just replacing the pointer assignment with a State::connect(..) call, this fix is now merged with VSG master and will be part of the up coming 1.1.14 release that I'll make later this week.
","upvoteCount":1,"url":"https://github.com/vsg-dev/VulkanSceneGraph/discussions/1663#discussioncomment-15627399"}}}