Daz to Hexagon Crashing

This one has me stressed. After a decade of moving stuff back and forth between the programs, this is the first time I reseaved this failure notice, which also crashes out Daz. See attachment. The term Access_Violation confuses me, does this mean we can no longer use Hexagon to morph figures? Thanks.


Screenshot 2022-11-03 212805.png
568 x 549 - 42K
Comments
I don't know what that message means, I do know that yes we can still use Hexagon with the latest D/S because I've been using it.
n.b. Hexagon is best installed outside of the official Program folders ['cause the operating system guards those very well]. So I make it its own folder on C > My Programs > install old stuff here.
Then make sure that D/S's Edit > Preferences, bridge tab has the correct location for Hexagon.
n.b. there has been for awhile a problem with D/S closing Hexagon IF one uses D/S to open Hexagon and then closed D/S. If one knows that they want to work with only Hexagon after a transfer, then open Hexagon first and make a sphere or something/anything and send it over the bridge to D/S. After Hexagon has opened D/S, then load what you want in D/S and send it back over the bridge to Hexagon. Then D/S can be closed and Hexagon will remain open.
I reported this issue to the company and the claim was that it was a bug in Hexagon. It isn't. The information log of D/S clearly [I think] indicates that D/S is closing Hexagon.
Thank you. I'll give that a try. At some point I'm off to Blender for such things, but for now I have projects due, and lossing Hexagon would have been a set back. Once again, Thanks!