Hexagon 2.5.2.109, General Release!

24

Comments

  • RaytownmikeRaytownmike Posts: 33
    edited February 11

    I get this message when I try to lauch the Hex General Release. See attached for error message and my Mac version.

    Edited to removed screen shot with serial number

     

     

    Screen Shot 2018-02-11 at 2.09.46 PM.jpg
    803 x 650 - 108K
    Post edited by Richard Haseltine on
  • kenmokenmo Posts: 507
    hgc said:

    I was expecting improved stability, after so many time without updates and...  just opening and closing the program makes it crash!!!
    My personal opinion as 12+ years of C++ proffesional developer: people of DAZ Studio, please implement unit automated test to check you do not break existing features! That's the very basics of software development Q&A...

    People were reporting improved stability with the beta, and not (at least in public) reporting issues - that's why that version was promoted to a general release. If you are seeing crashes please report them to Daz, via a support ticket.

    I would avoid making assumptions about what Daz does or doesn't do for testing in general - though i dos eem to recall references to unit testing in the DS change logs at least.

    Well...for me I've built a few models in the beta version and very few crashes. The public release crashes quite frequently so I've gone back to using the beta version...

    I also get this error when launching the public release. I did not get it with the beta...

    HexError.JPG
    831 x 536 - 58K
  • kenmo said:
    hgc said:

    I was expecting improved stability, after so many time without updates and...  just opening and closing the program makes it crash!!!
    My personal opinion as 12+ years of C++ proffesional developer: people of DAZ Studio, please implement unit automated test to check you do not break existing features! That's the very basics of software development Q&A...

    People were reporting improved stability with the beta, and not (at least in public) reporting issues - that's why that version was promoted to a general release. If you are seeing crashes please report them to Daz, via a support ticket.

    I would avoid making assumptions about what Daz does or doesn't do for testing in general - though i dos eem to recall references to unit testing in the DS change logs at least.

    Well...for me I've built a few models in the beta version and very few crashes. The public release crashes quite frequently so I've gone back to using the beta version...

    I also get this error when launching the public release. I did not get it with the beta...

    That sounds like a bad file in the application or itss ettings. Remember that the new release version is the beta, just with new locations for the application and settings - if something was wrong with the folders (e.g. permissions) or files that aren't repalced by the update (e.g. settings) then that might well trigger different behaviours.

  • ShawnDriscollShawnDriscoll Posts: 280
    edited February 12

    XML errors? That's some bad installs there. Make sure you're not installing over an existing 2.5 from years ago.

    Post edited by ShawnDriscoll on
  • SF-DesignSF-Design Posts: 936
    edited February 12

    Since the update I see something strange when using UV Paint Mode and the Inflate Brush (also happens with the others)

    I see a weird trail of the brush and that makes working with the brush impossible. 

    I have attached a screen how it looks. 

    Anybody an idea what this is? I did not change any settings since the update and I hadn't the problem before. No hardware changes as well. 

    Thanks

     

    Capture_066.jpg
    618 x 919 - 118K
    Post edited by SF-Design on
  • Turn off the redraw or fastdraw? In display setting.

  • SF-DesignSF-Design Posts: 936
    edited February 12

    Turn off the redraw or fastdraw? In display setting.

    That did it, thank you yes disabled local redraw and it is fine now

    Post edited by SF-Design on
  • ChoholeChohole Posts: 29,055
    Disable Edit > Preference Editor > 3D Display > Advanced > Local redraw
  • SF-DesignSF-Design Posts: 936
    edited February 12
    Chohole said:
    Disable Edit > Preference Editor > 3D Display > Advanced > Local redraw

    yap,thank you, that caused the problem smiley

    Post edited by SF-Design on
  • kenmokenmo Posts: 507

    XML errors? That's some bad installs there. Make sure you're not installing over an existing 2.5 from years ago.

    Thanks...but I installed it to a new folder structure.... Really not an issue as the beta version works fine. Even if I get past this XML error the public release is very unstable. So I'll continue with the beta until DAZ3D resolves the issues in the public release....

  • kenmo said:

    XML errors? That's some bad installs there. Make sure you're not installing over an existing 2.5 from years ago.

    Thanks...but I installed it to a new folder structure.... Really not an issue as the beta version works fine. Even if I get past this XML error the public release is very unstable. So I'll continue with the beta until DAZ3D resolves the issues in the public release....

    The Public beta and the release are the same, so any diffrences in stability are down to: settings, if they differ between the two; corrupt file,remember that even if you installed to a different application folder the settings may still be left-overs; folder settings in the OS; security software or other low-level tools treating the two differently. Comparing their settings is the obvious place to start.

  • kenmokenmo Posts: 507

    Welll if there indeed the same, why troubleshoot? Instead I'll continue to use the beta version. It works great... Love it...

    I do computer network server support (file & print and not database or web servers) for a living (30+ years). In my downtime I would prefer to be creating art or taking photos then doing computer support, even if it is my own computer.... :-)

  • kenmo said:

    Welll if there indeed the same, why troubleshoot? Instead I'll continue to use the beta version. It works great... Love it...

    I do computer network server support (file & print and not database or web servers) for a living (30+ years). In my downtime I would prefer to be creating art or taking photos then doing computer support, even if it is my own computer.... :-)

    The whole point of a public beta is to have the application used on a variety of machines, in a variety of workflows, to catch issues that wouldn't be caught in the more circumscribed internal or private testing. In order for that work people do need to report the issues they find. It's true that Hexagon has quite a few settings, but if you would take the time to compare the two versions and see if there's a difference, clearing which resolves the crashing, and then report your findings you would be doing both your future self and your fellow users a service.

  • RaytownmikeRaytownmike Posts: 33
    edited February 12

    I get this message when I try to lauch the Hex General Release. See attached for error message and my Mac version.

    Edited to removed screen shot with serial number

    Any Ideas what this issue is all about? Still can't launch the General Release.

    Post edited by Richard Haseltine on
  • DoctorJellybeanDoctorJellybean Posts: 2,677
    edited February 12

    I get this message when I try to lauch the Hex General Release. See attached for error message and my Mac version.

    Edited to removed screen shot with serial number

    Any Ideas what this issue is all about? Still can't launch the General Release.

    Do you get the same issue with the Beta version, or do you only have the General Release version installed?

    Post edited by Richard Haseltine on
  • I have already filled out a help ticket, but was wondering if anyone else was having issues with the "Set Pivot Point" tool in the Hexagon 2.5.2.109, General Release?

    I do not see the highlight "snap" feedback for new pivot placement. And when I click a point, edge, or even polygon the pivot always seems to end up behind the object.

    If grid snap is activated the pivot always ends up on the Y grid.

    So basically, the pivot tool seems to be ignoring all scene geometry.

  • I get this message when I try to lauch the Hex General Release. See attached for error message and my Mac version.

    Edited to removed screen shot with serial number

     

    Any Ideas what this issue is all about? Still can't launch the General Release.

     

    Do you get the same issue with the Beta version, or do you only have the General Release version installed?

    Only with the General Release.

  • de3ande3an Posts: 792

    I have already filled out a help ticket, but was wondering if anyone else was having issues with the "Set Pivot Point" tool in the Hexagon 2.5.2.109, General Release?

    I do not see the highlight "snap" feedback for new pivot placement. And when I click a point, edge, or even polygon the pivot always seems to end up behind the object.

    If grid snap is activated the pivot always ends up on the Y grid.

    So basically, the pivot tool seems to be ignoring all scene geometry.

     

    As far as I can tell, the Set Pivot Point function has never worked properly (at least not in the Mac version). The previous version (2.5.1.79) has the same issue.

    It seems like I've been able to make it work on rare occasions, but haven't figured out what, if anything, I did to make it work.

  • ShawnDriscollShawnDriscoll Posts: 280
    edited February 13
    de3an said:

    I have already filled out a help ticket, but was wondering if anyone else was having issues with the "Set Pivot Point" tool in the Hexagon 2.5.2.109, General Release?

    I do not see the highlight "snap" feedback for new pivot placement. And when I click a point, edge, or even polygon the pivot always seems to end up behind the object.

    If grid snap is activated the pivot always ends up on the Y grid.

    So basically, the pivot tool seems to be ignoring all scene geometry.

     

    As far as I can tell, the Set Pivot Point function has never worked properly (at least not in the Mac version). The previous version (2.5.1.79) has the same issue.

    It seems like I've been able to make it work on rare occasions, but haven't figured out what, if anything, I did to make it work.

    Pivoting has been working fine for me in Windows 10 Pro 64-bit using the x86 version of the latest Hexagon release. Even works on grouped objects.

    Post edited by ShawnDriscoll on
  • kenmo said:

    Welll if there indeed the same, why troubleshoot? Instead I'll continue to use the beta version. It works great... Love it...

    I do computer network server support (file & print and not database or web servers) for a living (30+ years). In my downtime I would prefer to be creating art or taking photos then doing computer support, even if it is my own computer.... :-)

    I just installed the lastest release of Hexagon from scratch on a Windows 10 computer. It grabbed the Microsoft Visual C++ Redist files during its install, and everything. No issues with running it. The XML editor on this machine is Notepad++. But that shouldn't matter.

  • SF-DesignSF-Design Posts: 936

    I had those XML error first too, then uninstalled everything, also removed left overs manually,  made a clean install, and now no XML errors. 

  • ShawnDriscollShawnDriscoll Posts: 280
    edited February 13
    SF-Design said:

    I had those XML error first too, then uninstalled everything, also removed left overs manually,  made a clean install, and now no XML errors. 

    Did you un-install Hexagon 2.5 using DIM? Or did you use the Program Control Panel to remove it? I been using DIM to do all my un-installing and installing of DAZ apps. Works great.  My DAZ Library is in a roaming profile on my system. I log in as the user that Hexagon is installed for.

    Post edited by ShawnDriscoll on
  • SF-DesignSF-Design Posts: 936
    SF-Design said:

    I had those XML error first too, then uninstalled everything, also removed left overs manually,  made a clean install, and now no XML errors. 

    Did you un-install Hexagon 2.5 using DIM? Or did you use the Program Control Panel to remove it? I been using DIM to do all my un-installing and installing of DAZ apps. Works great.  My DAZ Library is in a roaming profile on my system. I log in as the user that Hexagon is installed for.

    I used DIM to do all the work, usually do that. I had XML errors , then I uninstalled over programs in system settings and also DIM and reinstalled using DIM, then it worked fine. 
    I deleted the profile directory too before that (also located here in the Roaming folder under Users). 

  • SF-Design said:
    SF-Design said:

    I had those XML error first too, then uninstalled everything, also removed left overs manually,  made a clean install, and now no XML errors. 

    Did you un-install Hexagon 2.5 using DIM? Or did you use the Program Control Panel to remove it? I been using DIM to do all my un-installing and installing of DAZ apps. Works great.  My DAZ Library is in a roaming profile on my system. I log in as the user that Hexagon is installed for.

    I used DIM to do all the work, usually do that. I had XML errors , then I uninstalled over programs in system settings and also DIM and reinstalled using DIM, then it worked fine. 
    I deleted the profile directory too before that (also located here in the Roaming folder under Users). 

    I'll try your approach and thanks.

     

     

  • SF-DesignSF-Design Posts: 936
    SF-Design said:
    SF-Design said:

    I had those XML error first too, then uninstalled everything, also removed left overs manually,  made a clean install, and now no XML errors. 

    Did you un-install Hexagon 2.5 using DIM? Or did you use the Program Control Panel to remove it? I been using DIM to do all my un-installing and installing of DAZ apps. Works great.  My DAZ Library is in a roaming profile on my system. I log in as the user that Hexagon is installed for.

    I used DIM to do all the work, usually do that. I had XML errors , then I uninstalled over programs in system settings and also DIM and reinstalled using DIM, then it worked fine. 
    I deleted the profile directory too before that (also located here in the Roaming folder under Users). 

    I'll try your approach and thanks.

     

    you are welcome, I am not sure what step helped here, I guess it was the cleaning up of the user profile folder where lots of files remained after the intallation

     

  • Roaming folder? What and where is this?

  • SF-DesignSF-Design Posts: 936
    edited February 13

    yes here the were in systemdrive\users\USERNAME\appdata\roaming\daz\hexagon

    might be different depending on the windows version you are using, I am on WIndows 10

    they should be in the usual profile folder for your windows user name and usally in Roaming I gues

    Post edited by SF-Design on
  • SF-Design said:

    yes here the were in systemdrive\users\USERNAME\appdata\roaming\daz\hexagon

    might be different depending on the windows version you are using, I am on WIndows 10

    they should be in the usual profile folder for your windows user name and usally in Roaming I gues

     

    SF-Design said:

    yes here the were in systemdrive\users\USERNAME\appdata\roaming\daz\hexagon

    might be different depending on the windows version you are using, I am on WIndows 10

    they should be in the usual profile folder for your windows user name and usally in Roaming I gues

    I am a Mac guy! Thanks though.

  • I am a Mac guy! Thanks though.

    It might be High Sierra related. Unfortunately I can't check that, as I'm sticking with Yosemite for the time being. I'll see if I can find out more from other people.

  • Nah works on my laptop using High Sierra.

Sign In or Register to comment.