Not seeing it in DiM either and have all the required boxes ticked that should make it show up.. Strange even though I own Hexagon, I had to go to the beta store page and put it into my cart and free pruchase it, to make it show up in DiM..

Unfortunately, the 64 bit version crashes DAZ Studio if I use the Hexagon bridge. I've attempted it several times - crashes every time.

Working OK here, both ways.

EDIT: Windows 10 Pro, version 1709

A bit more testing and it turns out to be a 3rd. Party Anatomical Elements geograft causing the crash. It does not crash when a plain-vanilla G3F is sent over the bridge. I don't think I will need to modify figures with that geograft in place so it might not be a problem.

One thing that is a problem though - some of the character skins don't display in the Hex viewport. The basic Jeane is fine but most of those I've tried, including several using the G3F UV and also Bethany 7 and Mei Lin 7, will only display in wireframe - no solid options (which just result in the figure disappearing if selected).

2. 4.11.0.101 bridge / transparency fix; in the meantime a work-around is simply to set the transparency to whatever you want in Hexagon once the item is imported from Studio (on the Mac it's a one-time change, remembered in back/forward moves of the object).

3. no more info.

4. So I used the beta to make a "little black dress" (from a cylinder) as attached, all OK including dForce modifier.

5. Hexagon 2.5 crashes quite often during exit .. but the application puts up the standard Crashreporter output (which sends the crash report to Apple) .. So I kept a copy - is there somewhere you'd like me to send it? (or should I raise a "normal" bug report?).

PlugIns are now included within the application bundle as individual files in ./Contents/PlugIns

is that an indication that it might be possible (at some stage) for 3rd parties to author plugins for Hexagon? ... I, for one, would be interested in authoring plugins to sanitise meshes for dForce (in some cases, I have had to take [other people's] meshes out to blender etc. to fix) .. maybe this is subject for some different thread/forum.

For the tools like "soften" the "cursor" (i.e representation of the area and strength of influence for the tool) is not being erased when the mouse moves, so leaves a trail which obscures the model making it hard to work with. AFAICT, the tools are behaving correctly - but the interface experience is, erm, not the best...

PlugIns are now included within the application bundle as individual files in ./Contents/PlugIns

is that an indication that it might be possible (at some stage) for 3rd parties to author plugins for Hexagon? ... I, for one, would be interested in authoring plugins to sanitise meshes for dForce (in some cases, I have had to take [other people's] meshes out to blender etc. to fix) .. maybe this is subject for some different thread/forum.

It'sd a bit of tidying up, so that the Mac version works as the Windows version does - it also means that Mac users could now disable a plug-in to aid in trouble-shooting.

5. Hexagon 2.5 crashes quite often during exit .. but the application puts up the standard Crashreporter output (which sends the crash report to Apple) .. So I kept a copy - is there somewhere you'd like me to send it? (or should I raise a "normal" bug report?).