Possible D-Former Bug in 4.9.4.117?

Hey guys,
I'm having an issue that I haven't seen before and I am wondering if what I'm experiencing is a bug with D-Formers. The issue has happened several times since I upgraded to 4.9.4.117, however I also started using Genesis 3 at the same time, so I'm not sure if it's related to that instead.
Whenever I create and set up a D-Former on clothing fitted to Genesis 3 that has a reverse deform morph loaded on it, the transforms of the D-Former field will change after I save / close / re-open the project. To be more precise, the values of the D-Former field's transforms don't change, but for whatever reason the field is not in the same place / scale.
Here's a screenshot I took during testing to show the position of the D-Former field: http://i.imgur.com/d8xiUcv.jpg
And here's a screenshot of the same D-Former field after saving/re-opening the project: http://i.imgur.com/Upv6SLN.jpg
It's getting old pretty fast, so I'm really hoping I'm wrong about it being a bug and there's something I'm missing here. If anyone has any suggestions please let me know!
Comments
Don't use D-formers on posed figures.
Maybe once you have the deformer how you like it spawn the morph, which will turn your deform into a morph slider. I know thats not what youre asking for but might serve as a workaround.
How should this work ?
I had a scene with loads of d-formers attached. All of them on posed objects. With some of the d-formers I had the same problem as you.
My skills whith this tool are very limited, so, after I did it all the 3rd time, I simply made a screenshot of the field and d-former settings. Does not solve the problem, but takes 25 seconds to have the same as before.
You can use a dForm with a weight map on a posed figure, you can also use a dForm on a posed figure dirctly but it will help to hae a copy of the unposed figure too to use as a placement guide.
Baking it to a morph would actually probably be a viable workaround -- I forgot about that option.
That said, I don't think the behavior I'm seeing should be happening, and while a workaround is great it isn't really the purpose of this post.