Discovery Import

Discovery Import

Ansys Discovery Modeler vs Spaceclaim speed

    • n.koetsier
      Subscriber

      Goodafternoon,

      At our company (MechDes) we are looking into Ansys Discovery. During trial periode we found that the modeller works slower compared to spaceclaim. Rotating, panning, pulling, moving, all commands are more 'sluggish' compared to spaceclaim. 
      It is also visiblie in the task manager. Spaceclaim utilizes 100% 3d gpu graphics. While Discovery utilizes around 60%. Settings are the same.

       

      Is this a known issue? Is there any fix possible to have the same performance as in spaceclaim?

       

      Thanks in advance.

       

      Greetings,

      Nick Koetsier

    • Devendra Badgujar
      Ansys Employee

      Hello Nick Koetsier

      We have not seen this before. Are you experiencing this behavior with any specific model or is it happening in general?

      Please try updating your graphics drivers directly from the manufacturer website (i.e. NVIDIA).

      You might also want to clear your user settings from File > Settings> Advanced > Reset All User Settings.
      Regards.

    • n.koetsier
      Subscriber

      Hello Devendra,

      No, it is with every model. And my drivers are up to date. We have this on 3 different pc's. And also our software provider Infinite has the same problem.

      • Devendra Badgujar
        Ansys Employee

        Nick Koetsier 

        Which version of Discovery are you using?

        When running under Discovery Modeling at least 2 GB of discrete video memory is required (4+ GB recommended). 

        Make sure your computer is using the main graphics card for Discovery. Sometimes especially with laptops, Windows might assign a low performance graphics setting to Discovery.

        Regards.

      • n.koetsier
        Subscriber

        Devendra Badgujar 

         

        I am now running 2022 R2. I have a 4gb card (quadro M4000M)

        I think it is using the quadro card, becaus in task manager I can see the 3D percentage go up to 40%.

        Is there a way to confirm this?

      • n.koetsier
        Subscriber

        Devendra Badgujar 

        I have done the above:

        - confirmed driver up to date

        - graphics settings of discovery is set to performance

        Still no luck.

    • Devendra Badgujar
      Ansys Employee

      Hello Nick Koetsier

      You can try a couple of things with Discovery and SpaceClaim to improve graphics performance:

      1. Turn off Enhanced view of geometry
      2. Turn off anti-aliasing and recalculate Retendering

      Regards.

      • n.koetsier
        Subscriber

        Hello Devendra Badgujar 

        Thanks for the reply. Unfortunately still no effect. GPU maxes out at 40/50% usage.

        Also not a cpu bottleneck. Would you maybe have time to call over teams about the problem?

        Thanks in advance

      • Devendra Badgujar
        Ansys Employee

        Nick Koetsier 

        Please can you try disabling Intel graphics on the machine and see if that helps. 

        Can you try reinstalling the application again with Administrator rights? Temporarily turn off firewalls and antivirus during this. 

        I'm not sure if GPU usage is the correct measure for performance in modeling, will have to discuss this with the team and get back to you. 

        Regards.

      • n.koetsier
        Subscriber

        Devendra Badgujar 

        I will try what you said. 

        It is not only visible in task manager. But I can also see the difference in response time and frame rate in discovery vs spaceclame. 2 programs next to eachother.

        Thank you

      • n.koetsier
        Subscriber

        Devendra Badgujar Hello Devendra,
        I still have the same problem. I am thinking it is in the Ansys software or maybe some other driver?

      • Devendra Badgujar
        Ansys Employee

        Nick Koetsier 

        Discovery doesn't use all the available GPU and consumes memory which is only required for that geometry involved. It won't use 100% GPU as it might cause a crash. 

        Please can you share a short video describing the behavior in both Discovery Model mode and SpaceClaim?

        Regards.

      • n.koetsier
        Subscriber

        Devendra Badgujar Where kan I send this video to?

      • Devendra Badgujar
        Ansys Employee

        Nick Koetsier 

        Please send the video to ansys-discovery-support@ansys.com 

    • Devendra Badgujar
      Ansys Employee

      Hello Nick Koetsier

      Please try installing the latest redistributable. You can try installing the appropriate one from here: Latest supported Visual C++ Redistributable downloads | Microsoft Docs

      Please try installing the VC_redist.x64.exe and vc_redist.x86.exe for Visual Studio 2015, 2017, 2019 and 2022 package. If you already have 2015 installed, you may need to uninstall before installing this downloaded version.

      Let me know if this helps.

      Regards.

      • n.koetsier
        Subscriber

        Devendra Badgujar Also I have tried this, but without luck.
        I have sent you 2 videos of the same model. You can see the difference between discovery and spaceclaim. It is small, but for me very noticable during modelling.

      • Devendra Badgujar
        Ansys Employee

        Nick Koetsier 

        Thanks, will check and update you. 

        Regards.

    • Devendra Badgujar
      Ansys Employee

      Hello Nick Koetsier

      In the Discovery video you shared it has a simulation setup which means it's not a 1-1 comparison to SpaceClaim. You can try this model without simulation setup in Discovery and check. 

      At least 4 GB of discrete video memory (8 GB recommended) for Explore stage, and when running under Discovery Modeling at least 2 GB of discrete video memory is required (4+ GB recommended).

      Regards.

      • n.koetsier
        Subscriber

        Devendra Badgujar Also without the simulation it is slower.

        Also our provider, Infinite, has the same problem on their hardware. They also contacted Ansys; And got the reply that it is just the software, just the way it is. Ansys doesn't see it as a problem... Unfortunately. Hopefully fix in future versions.

      • Devendra Badgujar
        Ansys Employee

        Nick Koetsier 

        Thanks for your update. We will take a note of the suggestions. 

        Regards.

Viewing 5 reply threads
  • You must be logged in to reply to this topic.