Aller au contenu principal

Crushing all the time...

Commentaires

8 commentaires

  • Tim Heeney

    In V5 i personally find the 'freezing or processing something forever' doesn't happen ( to me anymore), I also personally find the 'back-up file' system works fine.

    Since V2 to V5 i have made around 20 software support tickets. Helping users solve their issues really helps my understanding of using DSM effectively and supports the reporting by trying to establish cause / effect circumstances.

    Sure doing some things IS SLOW...especially putting 100+ holes into spline surfaces with rounded 'pulled' edges does take some time to 'compute' if changing the holes somehow.

    Moving / alterating hole patterns ( hundreds of holes) can also take a few secs upto maybe a minute ( it often froze in V4 but is much better in V5).

    Maybe your pc system is getting close to the minimum spec ? - I don't know...

    There's also 'best working practices' advice available if your system is unresponsive / sluggish etc.

    Anyway, please post up your problems , maybe i / we can help.

     

    0
  • Horatiu Pintilie

    Dear Tim,

    I am honestly very merciful for being so helpful with me.
    Thank you very much!
    However, for me the freezing problem is a permanent "feature".
    Is very hard to explain why and when it happens but is very clear everything works fine in the case of the other programs.
    Sometimes the nVicdia GTX card makes some problems but is clear when it does because is easy perceivable from computer startup.
    About DSM is something else, something about faceting, something about how the model is processed during design actions.
    When it happens the processor gets busy (25 - 40 %) memory used is increased (maybe 10% in the case of small designs and up to 70-80% for the large ones) and the system becomes hardly responsive, the solution to make everything normal being (usually) the shutting down of the DSM application.
    Sometimes the app. gets frozen even for small files (with not even 10 beveled holes for instance), but indeed it is usually friendly while working on small and very small files.

    The backup was also many times a problem. I lost plenty of work hours especially when I was tired and forgot to make a "just in case" saving.

    In my opinion so far it's a lousy program in many regards.
    A good basic design program with a huge impact on the market especially due to the easy going approach in regard the modeling (reason why I recognized I used it almost 2 years) but is also full of bugs and problems that you find finally hardly acceptable especially when designing time becomes a critical aspect.

    I don't think I did something wrong in order to get suggestions (although I do appreciate a lot any help) because I simply have nothing wrong in my computer (I7, 8gb RAM, GTX 950M, 512 Gb SSD ... etc) and everything leads to the simple conclusion the DSP program itself is the faulty one.
    I rather suspect when this program was tested (before release) they did not cover all the possible operational states, because in some cases (and indeed maybe for some systems) it simply gets frozen.

    However, I do thank you very much for your interest.
    Please don't judge me wrong. I am rather ready to recognize I was a stupid user if somebody will give me the working hint about how to make this bloody software stop crushing, but so far all the tries I made, all the settings I changed and all the others ideas where simply not working.
    Is not about being happy to counterargument, is about a program which I want it functional, because yes ... I do like it in some many other regards.

    Best regards

    0
  • Tim Heeney

    Hello Horatiu.

    These suggestions have worked well to speed up DSM especially the 'freezing' or the very slow responses.

    Please ask for more information if required.

    or this to...

    working this way, auto selection is off but all the selection is very easy to turn on when required. Select line, click magnifier icon as shown ( finds all lines within a single part, option now, click 'search all bodies' ( finds all lines within active part and bodies under active part ( i.e parts not 'greyed out' )

    I hope some of these suggestions will speed up your work flow.

    Absolutely, they have helped me.

    If you work with spline surfaces, these must be at the lowest graphical resolution possible as they are very 'data dense'. Again, ask if unsure.

    Regards...

    1
  • Tim Heeney

    However, I too think DSM could do with speeding up somehow... 64GB ram 1866Mhz  E5-1660v2 ( 3.7 Ghz ) Nvidia K4200 ( 4GB ) Pass Benchmark (single thread) 2146 - so it's barely just OK, next processor must be over 3000.

    Moving dense patterns seems the slowest DSM action. The below takes around 3 secs. I'm surprised it's not closer to 1/3 s !

    The below is an unusual situation for me - but some DSM users do indeed need this type of manipulation !

    in V4, it used to freeze, but in V5, it now completes OK but could be faster.

    But, just like you, the below takes way to long and i don't know why - think i'll raise a support ticket...EDIT - these are spline surfaces and very data dense - so it's understandable to be slower...No support ticket raised by me.

    EDIT:

    It takes along time because the countersinks are actually a spline surface and NOT a cone ( analytic) face.

    But, if a cone can be made, i.e countersinking on a flat plane...

    50 countersinks changed in 2.0 s...hmm - not bad.

    For spline faces above, deletion and recreation can be 'processing time' more efficient than time for modifying if the wait is too long.

     

    0
  • Richard Miller

    I am having the crashing issue also. After using it for a little while my computer goes blue screen and reboots. The time period is not consistent, it could be 5 minutes or 20 minutes. I went back to version 4.0 and everything is working fine. Version 5 acts like it has a memory leak in the software.

    0
  • Tim Heeney

    Hi Richard.

    The latest release is V5 - it could be very useful if the reason for this is identified and perhaps...advice could be given to stop it.

    Even though by versioning back to V4 the problem disappears, why not post up your specific problem ?

    I assume 'none of the above' would make any difference in your circumstance as you haven't made any comment.

    I'm totally certain V5 is more stable / faster and less 'unresonsive' than V4. The new sketcher constaints has introduced ' some working / open component / window ' constraints and FPS (F9) delays- which 'bug me' somewhat but the old sketcher is still there available to be set live in DSM Options > Advanced...

    Being a bit cheeky, have you checked your pc meets the minimum requirements ?

     

    0
  • Horatiu Pintilie

    Hi everyone,

    To just add a little fun to all these, I just had to use the surface border of a piece in order to generate another, so I simply tried to move the contour of my original piece while pressing CTRL (the copying method that is used with the move tool).

    The result was a never ending calculation, computation and kneading of all the bits (which were resting initially very calm and peaceful in my machine :) )...

    However, the operation was finally ended successfully (but after more than 1 minute, an eternity for the size of the job), while the same copying operation was made with CTRL-C and Paste in milliseconds....

    Beside the fact the use of CTRL_C and Paste instead of the move tool is like returning back to DOS console from Windows, the abnormal effort to compute the enclosed copied surface makes me wonder (again) about the logic used to compute the edges of the adjacent surfaces and the fact maybe there is a predisposition due to inherent computing error (such as truncation of the numbers) to slip one from another and generate convergence issues.

    Is like with the move tool DSM tries to move every individual piece to the new location and after each move to manage the fitting of the edges (which because of the curves involved is hardly possible without very very high precision), while the simple copy paste method takes the assembly as a full container with the edges already well fixed...

    In my opinion DSM has bugs ... but even so it is still my favorite CAD tool... :)

     

    0
  • Tim Heeney

    Hello Horitiu, ( sorry, i had to reply... ;) )

            ' I just had to use the surface border of a piece in order to generate another, so I simply tried to move the contour of my original piece while pressing CTRL (the copying method that is used with the move tool).

    The result was a never ending calculation, computation and kneading of all the bits (which were resting initially very calm and peaceful in my machine :) )... '

    This seems to work OK on my machine - even with options >advanced>enable geometry convergenge ( while dragging).

            ' Beside the fact the use of CTRL_C and Paste instead of the move tool is like returning back to DOS console from Windows '

    This command is windows universal - why 'reinvent the wheel ' and it works very successfully...

    If DSM 'stutters', learn to approach the problem from another way perhaps. All 'tools' ever invented have defined working procedures for safe and consistent behaviour do they not...

    Sure, the 'help' could be better and yes, there are 'bugs' and yes, there can be a head scratch wondering which tool is best to use - no arguement from me here...

    The above faces have been moved/copied without any issues. It slows slightly if dragging through another object but even with a complex multi inserted part assembly - i'm not seeing an issue here...

    my pc spec: ( Lenova S30 circa 2014 )

    E5-1660v2

    64 GB ram 1866Mhz

    Nvidia K4200

    meeting the V5 minimum requirements.

     

    Please post up your problem.

    0

Vous devez vous connecter pour laisser un commentaire.