I don't do anything particularly complicated with Hexagon, but it doesn't crash for me on 64 bit Mac OS X; I pretty much just use send-to via bridge, smooth, and send-back via bridge.
-- Morgan
So you're saying the bridge works for you both ways?
Bridge works both ways for me, but only intermittently. Mac OS10.9.5. Usually, the trick is to have your Hex model open, and then send something from Studio to Hex. This opens another iteration of Hex with the imported object. You then switch to the first one, where your model is and send it through the bridge.
Clunky and doesn't always work, but usually does for me.
I don't do anything particularly complicated with Hexagon, but it doesn't crash for me on 64 bit Mac OS X; I pretty much just use send-to via bridge, smooth, and send-back via bridge.
-- Morgan
I wish I had that level of success, I tried on two MacBook Pro's and A Dual Xeon Pro that if I didn't remember to save about every two or three steps into a project "boom goes the dynamite", it also behaved like this in XP 32 bit an Win7 64 bit. It may be you can't approach the interface without a bit of fairy-like daintiness but I wanted the app to work, Blender terrified me at the time, but Hex being a non viable for me drove me to keep at the alternatives (now Blender is my go to app).
I'm not saying they wont or they can't, I would love to have it again to provided they could make it stable for my click-fu.
There is a new version of hexagon being made, it is in a closed beta, if y'all peek at the hex forums every now and then.
This is the best news I've heard in a long time. We really need 64-bit support and a more stable program, not to mention upgraded features like cloth sim and dynamic mesh sculpting.
I think Hexagon is a great program and I'm always sorry to hear of people experiencing nothing but crashes. I don't use the program in conjunction with Studio or any other program and I use Windows 8.1 and 7 and I can use the program for hours without any crash at all.
However, I admit it does crash from time to time but always for me that is when I've tried doing something I'm not familiar with and have clicked here and there, changed my mind or otherwise got confused. That happens to be the position I was in when I was a new user and had more crashes than nowadays. I'm wary of some of the tesselation tools - if my model's mesh is a shambles in any way, these can cause a crash. The mesh being a shambles can arise from having a mesh I may not have welded properly after mirroring and other such flaws.
When I first tried 3d programs (on a Windows 98 computer with minimal graphics capabilities) I found that having more than one 3d program open at once occasionally caused lots of problems. I sometimes wonder whether Hexagon suffers in this way since it goes back that far. Of course I'm displaying complete ignorance of how computers allocate resources and am probably way off the mark.
Typically I can send a mesh to Hexagon from DAZ Studio, use the softening tool on it, and send it back without a problem. When I send it back, DAZ Studio does it's little 'bounce' thing in the dock, because it has the morph import dialog up. Sometimes DAZ Studio doesn't come back to foreground on its own, but it's still waiting with the morph importer dialog when I foreground it.
I used to have Hexagon issues where it would put up some weird message about consistency, or something, on a regular basis (but the program wouldn't exit, I just had to click to continue)...but I haven't seen that message in a long time now.
I don't spend hours modeling in Hexagon, though, I just use it for the softening brush. And I just tried sending a completely fresh model to DAZ Studio, and it didn't do it at all, so it may be only for items that were sent TO Hexagon from DS that can be sent back.
I use Daz Studio and Hexagon, with the bridge, in both directions. The best thing about it is the model keeps it's dimensional and directional integrity. The conversion is x/10 in one direction and X*10 in the other.
I won't say; I have never experienced the Crash, stumble, Crash, BAD WORDS!!!. To minimize them, I make it a habit to make incremental saves, with a version number, and very often. I can revert back to a previous save. Also if I delete a large amount of data, I save as, dump and reload or maybe even restart, depending on the size of the deletion. I have also gotten good at saying when it is time to to the stop and reload. I will say the Win version is more stabe than the Mac Version.
Yes the Bridge works in both directions and it is great for making morphs, you send the model though the Bridge to Hexagon, make the change you want to make, and then send it back to Studio, when it arrives the Morph loader opens and a few keystrokes later, Morph is created. I have actually used it to create several full body morph for Characters, after dialing them up, in that case it is and in and out. select the model, press the icom, Hexagon loads and the model loads, then press the Daz Studio button and it goes back and the Morph loader comes up.
I have made some rather large models, I am talking size not complexity. I created the curtain walls for a rather Large City. I’m also using it to convert some 2D CAD Plans, into 3D models, which I have a process using a Carrara plugin to extrude the plans; bring the extruded plans into Hexagon, to add premade doors and windows; then bridge them into Daz Studio. This takes a lot of fancy dancing with the 2D plan, so you have a usable model when it arrives in Hexagon. the only think I will say is the outside fo the house is just a shell. It was also tricky because I wanted the finished model to be compatable with maclean's Room Creator walls.
There is one thing I have noticed: Daz Studio works in centimeters and Hexagon in decimeters. So Genesis 3 Female is 179 cm in Studio, but 17.9 dm in Hexagon. Also it may show only three decimal places, but I’ve seen there are actually something like six to eight in the file.
If we are making a wishlist for Hexagon-Next, beside stability and 64 bit (of course):
Seamless integration with Daz Studio’s surface shader libraray (so you could do the next item)
Material zone painting, without having make a UV map.
Tthe ability to remove the *^*&^% Default Surface, once it is empty! (Or maybe just rename it)
Add a terrain builder, which can use 16bit grayscale as maps.
I just bought Hexagon, and would like to point out two things:
1) The product description says that it installs with DIM or manually. At least for me, DIM didn't do it. I had to download it manually and install it like any other program. I spent a good bit of time searching my computer, wondering where DIM had installed Hexagon. Finally looked at the DIM - installed list and it wasn't there. Took a while, I'm old and slow.
2) The product key is located in your account - serial numbers section. I didn't know this and wasted some time checking my email and messages, looking for the product key.
It would have been nice to have these two things mentioned in the Product Description. What's intuitive to some people isn't for others.
Now to go play with Hexagon and see what happens. While I watch the videos...
There is a new version of hexagon being made, it is in a closed beta, if y'all peek at the hex forums every now and then.
And has been for a year or more.
Actually it's only just over 6 months since it went into private beta.
May I ask what evidence you have regarding this? (links to posts, etc.)
I've been very interested in Hexagon development for a long time, and have even participated in past closed beta testing. I've seen nothing posted by any DAZ representative regarding further development since my last involvement. I've seen no call for beta testers (which was how I got involved last time).
There is a new version of hexagon being made, it is in a closed beta, if y'all peek at the hex forums every now and then.
And has been for a year or more.
Actually it's only just over 6 months since it went into private beta.
May I ask what evidence you have regarding this? (links to posts, etc.)
I've been very interested in Hexagon development for a long time, and have even participated in past closed beta testing. I've seen nothing posted by any DAZ representative regarding further development since my last involvement. I've seen no call for beta testers (which was how I got involved last time)
We have been informed by a very senior member of the Daz Software team that, and I quote,
The page began displaying that Hexagon 2.5.2.x was in Private Beta in the late evening of September 25, 2015.
May I ask what evidence you have regarding this? (links to posts, etc.)
We have been informed by a very senior member of the Daz Software team that, and I quote,
The page began displaying that Hexagon 2.5.2.x was in Private Beta in the late evening of September 25, 2015.
OK, Thanks. That's good enough for me.
It must be a completely internal beta, with said "page" being only available to DAZ testers.
It's too bad that such activity is not more freely available.
That's the standard setup -- first in-house testing, then private beta, then public beta
And sensible, too. Don't rush it - get it right.
2.5.2.x doesn't sound like a massive leap, and if so that's fine. What we've got, working well, would be great. I got on sort of alright with the Hex and quite fancy getting back into it.
May I ask what evidence you have regarding this? (links to posts, etc.)
We have been informed by a very senior member of the Daz Software team that, and I quote,
The page began displaying that Hexagon 2.5.2.x was in Private Beta in the late evening of September 25, 2015.
OK, Thanks. That's good enough for me.
It must be a completely internal beta, with said "page" being only available to DAZ testers.
It's too bad that such activity is not more freely available.
That's the standard setup -- first in-house testing, then private beta, then public beta
And sensible, too. Don't rush it - get it right.
2.5.2.x doesn't sound like a massive leap, and if so that's fine. What we've got, working well, would be great. I got on sort of alright with the Hex and quite fancy getting back into it.
They're probably just working on bug fixes then and stability issues and not new features. While modernized features would be nice I'll be happy if I can just extrude a surface without it randomly crashing.
Comments
So you're saying the bridge works for you both ways?
Bridge works both ways for me, but only intermittently. Mac OS10.9.5. Usually, the trick is to have your Hex model open, and then send something from Studio to Hex. This opens another iteration of Hex with the imported object. You then switch to the first one, where your model is and send it through the bridge.
Clunky and doesn't always work, but usually does for me.
Never mind, I re-read the description and found the answer.
Thanks.
I wish I had that level of success, I tried on two MacBook Pro's and A Dual Xeon Pro that if I didn't remember to save about every two or three steps into a project "boom goes the dynamite", it also behaved like this in XP 32 bit an Win7 64 bit. It may be you can't approach the interface without a bit of fairy-like daintiness but I wanted the app to work, Blender terrified me at the time, but Hex being a non viable for me drove me to keep at the alternatives (now Blender is my go to app).
I'm not saying they wont or they can't, I would love to have it again to provided they could make it stable for my click-fu.
I wish there will be a Linux version of hexagon.
This is the best news I've heard in a long time. We really need 64-bit support and a more stable program, not to mention upgraded features like cloth sim and dynamic mesh sculpting.
I think Hexagon is a great program and I'm always sorry to hear of people experiencing nothing but crashes. I don't use the program in conjunction with Studio or any other program and I use Windows 8.1 and 7 and I can use the program for hours without any crash at all.
However, I admit it does crash from time to time but always for me that is when I've tried doing something I'm not familiar with and have clicked here and there, changed my mind or otherwise got confused. That happens to be the position I was in when I was a new user and had more crashes than nowadays. I'm wary of some of the tesselation tools - if my model's mesh is a shambles in any way, these can cause a crash. The mesh being a shambles can arise from having a mesh I may not have welded properly after mirroring and other such flaws.
When I first tried 3d programs (on a Windows 98 computer with minimal graphics capabilities) I found that having more than one 3d program open at once occasionally caused lots of problems. I sometimes wonder whether Hexagon suffers in this way since it goes back that far. Of course I'm displaying complete ignorance of how computers allocate resources and am probably way off the mark.
Greetings,
Typically I can send a mesh to Hexagon from DAZ Studio, use the softening tool on it, and send it back without a problem. When I send it back, DAZ Studio does it's little 'bounce' thing in the dock, because it has the morph import dialog up. Sometimes DAZ Studio doesn't come back to foreground on its own, but it's still waiting with the morph importer dialog when I foreground it.
I used to have Hexagon issues where it would put up some weird message about consistency, or something, on a regular basis (but the program wouldn't exit, I just had to click to continue)...but I haven't seen that message in a long time now.
I don't spend hours modeling in Hexagon, though, I just use it for the softening brush. And I just tried sending a completely fresh model to DAZ Studio, and it didn't do it at all, so it may be only for items that were sent TO Hexagon from DS that can be sent back.
-- Morgan
And has been for a year or more.
I used to use Blender, and I've gone back to it.
I'll throw in a few pennies here
I use Daz Studio and Hexagon, with the bridge, in both directions. The best thing about it is the model keeps it's dimensional and directional integrity. The conversion is x/10 in one direction and X*10 in the other.
I won't say; I have never experienced the Crash, stumble, Crash, BAD WORDS!!!. To minimize them, I make it a habit to make incremental saves, with a version number, and very often. I can revert back to a previous save. Also if I delete a large amount of data, I save as, dump and reload or maybe even restart, depending on the size of the deletion. I have also gotten good at saying when it is time to to the stop and reload. I will say the Win version is more stabe than the Mac Version.
Yes the Bridge works in both directions and it is great for making morphs, you send the model though the Bridge to Hexagon, make the change you want to make, and then send it back to Studio, when it arrives the Morph loader opens and a few keystrokes later, Morph is created. I have actually used it to create several full body morph for Characters, after dialing them up, in that case it is and in and out. select the model, press the icom, Hexagon loads and the model loads, then press the Daz Studio button and it goes back and the Morph loader comes up.
I have made some rather large models, I am talking size not complexity. I created the curtain walls for a rather Large City. I’m also using it to convert some 2D CAD Plans, into 3D models, which I have a process using a Carrara plugin to extrude the plans; bring the extruded plans into Hexagon, to add premade doors and windows; then bridge them into Daz Studio. This takes a lot of fancy dancing with the 2D plan, so you have a usable model when it arrives in Hexagon. the only think I will say is the outside fo the house is just a shell. It was also tricky because I wanted the finished model to be compatable with maclean's Room Creator walls.
There is one thing I have noticed: Daz Studio works in centimeters and Hexagon in decimeters. So Genesis 3 Female is 179 cm in Studio, but 17.9 dm in Hexagon. Also it may show only three decimal places, but I’ve seen there are actually something like six to eight in the file.
If we are making a wishlist for Hexagon-Next, beside stability and 64 bit (of course):
Haslor
I just bought Hexagon, and would like to point out two things:
1) The product description says that it installs with DIM or manually. At least for me, DIM didn't do it. I had to download it manually and install it like any other program. I spent a good bit of time searching my computer, wondering where DIM had installed Hexagon. Finally looked at the DIM - installed list and it wasn't there. Took a while, I'm old and slow.
2) The product key is located in your account - serial numbers section. I didn't know this and wasted some time checking my email and messages, looking for the product key.
It would have been nice to have these two things mentioned in the Product Description. What's intuitive to some people isn't for others.
Now to go play with Hexagon and see what happens. While I watch the videos...
Actually it's only just over 6 months since it went into private beta.
May I ask what evidence you have regarding this? (links to posts, etc.)
I've been very interested in Hexagon development for a long time, and have even participated in past closed beta testing. I've seen nothing posted by any DAZ representative regarding further development since my last involvement. I've seen no call for beta testers (which was how I got involved last time).
We have been informed by a very senior member of the Daz Software team that, and I quote,
OK, Thanks. That's good enough for me.
It must be a completely internal beta, with said "page" being only available to DAZ testers.
It's too bad that such activity is not more freely available.
That's the standard setup -- first in-house testing, then private beta, then public beta
And sensible, too. Don't rush it - get it right.
2.5.2.x doesn't sound like a massive leap, and if so that's fine. What we've got, working well, would be great. I got on sort of alright with the Hex and quite fancy getting back into it.
They're probably just working on bug fixes then and stability issues and not new features. While modernized features would be nice I'll be happy if I can just extrude a surface without it randomly crashing.