[RocketSurgeon]

I have CGDI BMW with all authorizations, and CG Pro. I'm happy with both of them. Change VIN, change mileage, and Cas3+ keys all work great on CG Pro. CGDI pulled ISN off MSV80 without issue. I really like the coding and programming options for used modules. My only issue at the moment is the Data manipulation from dump doesn't seem to calculate the ISN correctly. I'm confident they will fix it soon.

and how are you doing the wt chips are they working well im looking at this but getting mixed reviews even cg themselves are telling me maybe only 80 % working?

I would say my experience has soured since my last review. I'm still pretty happy with the CG PRO, but not the CGDI.
To answer your question about 35160WT, general consensus is that it doesn't work. A tiny number of people have been successful, but in many cases the first 2 lines turn to FF and the chip is toast. I think cloning the chip to the erasable vvdi chip is the best option.

It would seem that CG essentially advertises all of the capabilities of autohex, though they only offer a fraction of the capabilities. To be fair, CGDI is also a fraction of the price. I wish it could read ISN from more DME, but it's mostly limited to the older MSD/MSV stuff. It doesn't support most of the newer MEVD computers, though they claim otherwise. 
It does an excellent job making keys from dump, so that is exactly what I do. Downgrade carries some risk. If you go to the effort of making a backup before downgrade, you might as well just make the key from dump and skip downgrade altogether. FEM bricking also occurs, though generally fixable with e-sys. Recent FEM i-step is said to minimize risk.