I would really like to model some stuff and Hexagon is the only tool I've found that I can use (none of the other programs I've tried were usable, or if they costed money, ever had free giveaways =p), and I hope someone can help me solve this problem.

I assume "randomly" crashes means you have been unable to link the crash to any action you have done? If so, ignore this reply.

Otherwise I'd suggest you try to track/record exactly what you were doing just before any crash to see if you can assess app error or possible user error?

My best advice is to work somewhat slowly; such as once you make an action/command/etc. wait for Hex to complete the action before you do anything else...usually that is only a second or 2 but for complicated large models it can be several seconds and it you try to "stack" commands in a row (which it should be able to do) waiting in queue, Hex often crashes.

If I do a multi key/mouse-click tool command, in wrong order; Hex may crash or do nothing....and I see that as operator error...tho may not seem so because I thought it was a correct order of actions.

There are a number of things you could try - in preferences, re-set to default. Set OGL optimization to no optimization, uncheck anti-aliasing.

Set your graphics display panel to let application decide, or words to that effect instead of optimized.

Common user error - Hex is not good at catching user errors.

1. Being in too much of a hurry - with some complex actions Hex needs time to think, but shows no indication that it is doing so.
2. Going on to the next action without validating when validation is required.
3. Trying to do an action in DG mode when this is not allowed, working at the wrong level of DG or using too much or full DG

Then there are some faulty meshes which will cause crashes - mainly twisted N-gons.

Try to isolate any particular action or mesh which causes the crashing

I was looking for this thread, because I experience frequent crashes too. And it appears that once Hexagon starts crashing, it will not work anymore, until you reinstall it. This is all very tiresome. I guess it has to do with me being impatient. However, this should be prevented somehow by a better indication that the program is still thinking.
Otherwise, I really like it. However, for every slightly complex model I try to build, I have to reinstall at least once.
I hope there will be a 2.5.1.80 or something version that is more stable!

This is an old fix going back years. I'm not into coding, so don't know exactly what happens when it goes wrong - something to do with the preferences file getting corrupted?

A question I have asked and never had answered is if there is a method of saving a "good" preference file and use that to replace the "bad" one instead of having to re-set and then go in and set the preferences to what you want.

This is an old fix going back years. I'm not into coding, so don't know exactly what happens when it goes wrong - something to do with the preferences file getting corrupted?

A question I have asked and never had answered is if there is a method of saving a "good" preference file and use that to replace the "bad" one instead of having to re-set and then go in and set the preferences to what you want.

Hopefully some guru will help us out?

I'm definitely not a guru, but on a Windows system the preferences are stored in User\AppData\Roaming\DAZ 3D\Hexagon 2
You'll only need to copy the 3 files preferences.xml, shortCuts.xml and usergui.xml
If you have trouble finding them (or if you're not using windows) try a search on one of the filenames.

I've located the files. If I understand you correctly, what I'd need to do is copy these three files and save them somewhere, then when the preferences get corupted, instead of resetting them, replace them with the previously saved good ones?

@ genejoke - lots more information, please:)

What sort of problems are you having? What do you do before and after using chamfer that causes the problem? What sort of mesh are you using it on?

I've located the files. If I understand you correctly, what I'd need to do is copy these three files and save them somewhere, then when the preferences get corupted, instead of resetting them, replace them with the previously saved good ones?

Yes, that should do the trick if the crashing thingie is indeed a result of the preferences getting corrupted. I'd still reset the settings anyway, then replace the files.

The meshes are usually fairly basic. I'm trying to make some spaceship models, starting from a cube and extruding and such like. I can usually do it on one edge without issue but doing any more and it hangs. I'm running on windows 7 64 bit with 6gb of ram and a quad core processor. As for before and after... well before I'm selecting the relevant edges and after well it does what it is supposed to but a few moments later it stops and the error message comes up.

Well, your specs are certainly good enough - I take it you have a graphics card to match?

When you use chamfer, I take it you are using the values input and not trying to do it with the mouse - and that you are validating afterward?

The problem with using chamfer the way you are doing it is that it causes N-gons on the faces that haven't been chamfered - see my example 3. These need to be cleaned up by joining the verts. I've never had Hex pick up problems with N-gons - except when they are twisted - but some users have reported crashing because of them.

BTW, you can get better results, cleaner mesh and lower poly count by using extract around and smoothing instead of chamfer.