Announcement

Collapse
No announcement yet.

Gibbscam Slow and Laggy

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Gibbscam Slow and Laggy

    Hey everyone, my reseller is currently working with me on this, but so far no luck so thought I'd check with the think tank here. Gibbs seems to be weirdly slow and laggy since updating. I have this issue with every version since 2016, so since the revamp. I installed 2016 on the new computer just for poops and giggles, and it worked like a top. I've checked the forum, and actually did see one person experiencing the exact same issue. But they didn't get a reply or come back with a fix, sadly.

    So, my issue: dialogue boxes take as much as 3 seconds to open. For example, having an existing operation tile, double clicking it, then going to the op tile on the left and double clicking it to open the dialogue box. 1-3 seconds before it actually opens. Same to open the box to change operation type (contour to holes, for example). And in general, processing for surfacing/advanced 3d/volumill is taking longer as well

    Things we've tried:
    updating to the latest Nvidia drivers. Reinstalling gibbs (after uninstalling and deleting everything related in program files, user files, and the program data hidden folder). Settings seem to be the same between gibbs 23 and the 2016 I installed to try. GPU is selected for everything (the new computer has no integrated graphics, even). Tried unselecting the background material calculation, seemed to not make a difference. Made sure Nahimic isn't installed.

    Computer specs:
    One computer has an i7-7700, gtx1060, 16gb ram

    The other is:
    1 x Xeon W-2235 / 3.8 GHz
    RAM 16 GB
    HP Z Turbo Drive
    RTX A4000

    Anyone have any ideas would could be wrong? I can't imagine everyone is waiting 2-3 seconds for dialogue boxes to open, dozens or more times a day?

    Edited: here are some old posts for reference. Same exact thing for me. Hopefully this isn't something that people have just gotten used to over time



    https://forums.gibbscam.com/showthre...wer-than-V2016!
    Last edited by Wadep; 03-14-2023, 02:11 PM.

  • #2
    Unfortunately, it will never be as fast as v2016. It's copying more information from more locations and it just takes more time.
    I used to have the preference 'Open Process Dialog on Op Load' checked, but had to turn it off years ago because it was an unbearably long time to wait for it to open.

    Not what you are going to want to hear, but eventually you get used to it. It's just the transition that's rough.

    Comment


    • #3
      It's true that the process dialogs (for instance) are somewhat slower than they were, but @Wadep seems to be running into something more serious.

      For reference, on my PC the mill roughing process dialog takes around 250ms to open in 2016, and around 800ms to open in 2023, using the generic 5-axis mill MDD. This is the "expected" slowdown that @Mjbanderson is referring to. It's usually about 3x or so; barely noticeable for most dialogs (but easily measurable on some of the more complex dialogs, like the tool dialog, mill roughing and drilling, etc). Your MDD can make a difference; do you experience the same problems when using one of the generic MDDs?

      There were a few versions that had pretty severe slowdowns, which is what those other forum posts are about. GC14 in particular is much slower than either 2016 or 2023, and the Volumill dialog had some especially bad problems with flickering and sluggishness. Those problems should be resolved at this point.

      Comment


      • #4
        Thank you both for the reply. Mjbanderson, definitely not what I want to hear ha. I truly can't imagine the majority of most people just accepting Gibbs running the way mine is. If I can't get it sorted I'll be going back to 2016 for efficiency and sanity

        @DanielR, can I ask your PC specs for reference? I could live with an ~800ms time to open, that's quick enough where I'd either not notice or easily adjust. But this 2-3 seconds (maybe longer, I'm just counting in my head) is totally f'd. Before I realized it was just being slow, I'd double click to open the dialogue, move the mouse to about where I expected to be clicking, wait half a sec and think "oh I must've missed clicking it," and go back to the tile just before it finally opened. The tool dialogue box has never done this, it is consistently quick ish. I would guess that 800ms ish sounds about right, I can tell it's slower than I'm used to but not enough to impact anything. (Mind you, this is using no tool holders/custom tools/etc, so maybe that would slow that dialogue box down too. I'll see if I can get that one to slow down, in case that becomes helpful in diagnosing)

        We only have generic MDDs at this time. This happens on 3 axis mill vertical, 4 axis mill vertical, and horizontal lathe generic shank. I just double checked on a lathe program, since I've been doing mostly milling lately. Same thing. Roughing and contouring both do it. And not consistently to individual tiles, even- I tried checking the last op, and then opened the dialogue box and it was quick. Try the first op, slow. Go back to the last op, slow this time.

        I had Gibbs 12 on a different computer, it was similarly slow but at the time I chalked it up to not being a super computer. On this new computer (and that other), I've tried 22 and 23 and both are doing this. The volumill dialog is maybe a bit slower than the others, but not significantly so. Also hard to say as none are consistent.

        Comment


        • #5
          Originally posted by Wadep
          Thank you both for the reply. Mjbanderson, definitely not what I want to hear ha. I truly can't imagine the majority of most people just accepting Gibbs running the way mine is. If I can't get it sorted I'll be going back to 2016 for efficiency and sanity.
          I don't accepted it, but this is my chosen CAM software so I am stuck with it. I don't know how many times I sat in front of my computer swearing at it because I am waiting for Gibbs to do something such as.........

          Open a tool dialog
          Import tools or process
          Copying or cutting Geometry.

          And I work on simple 3axis vertical mill parts, I can't imagine 5axis mill turn parts. But in all fairness, I know the engineers that I work with are fighting the same things with solidworks. Sometimes they have to wait four minutes to open a simple assembly.

          Do as you wish, I have gotten use to Gibbs2022 and I wouldn't move back. But maybe forgot what I am missing. I have grown accustomed to waiting 2-3 sec, but if I have to wait 20+ seconds, I need to take a deep breath or I might bash my screen in.
          Jeff Schueller
          CNC mill machinist
          Northern Valley Machine
          East Grand Forks, MN USA
          3axis Vertical Hurco Mills
          Kao-Ming KMC 5-Face bridge mill, Fanuc18i

          Comment


          • #6
            That's a shame. Well, if support gives me some magical solution and it does remedy this, I'll be sure to let you know as well! But our reseller, who uses gibbs all day, confirms that this isn't their normal experience. And through screen sharing has shown a similar delay to what DanielR described

            Comment


            • #7
              Just following up for anyone who finds this. No solution yet. But an interesting find- if we select the preference/option to "open process dialogue on op load" or something like that. Then I double click an op tile and the process dialogue box opens faster- under a second to load the op and automatically open the dialogue box, which sounds more correct. But even with this box selected, if I double click the process tile to reload the dialogue box (or close the automatically opened one, and double click the tile to reopen it), it is still the usual 2-3 seconds to open.

              I don't particularly want it set on that option permanently. But maybe someone else with this issue will like that option, or maybe this helps towards a diagnosis

              Comment


              • #8
                Originally posted by Wadep
                Just following up for anyone who finds this. No solution yet. But an interesting find- if we select the preference/option to "open process dialogue on op load" or something like that. Then I double click an op tile and the process dialogue box opens faster- under a second to load the op and automatically open the dialogue box, which sounds more correct. But even with this box selected, if I double click the process tile to reload the dialogue box (or close the automatically opened one, and double click the tile to reopen it), it is still the usual 2-3 seconds to open.

                I don't particularly want it set on that option permanently. But maybe someone else with this issue will like that option, or maybe this helps towards a diagnosis
                I saw this just come through to dev. I'll take a look.
                Software Development Manager: GibbsCAM

                Comment


                • #9
                  Originally posted by JeremyS
                  I saw this just come through to dev. I'll take a look.
                  Awesome, thanks Jeremy!

                  Comment


                  • #10
                    Originally posted by JeremyS

                    I saw this just come through to dev. I'll take a look.
                    Hey Jeremy, just curious- did anything ever come of this? Haven't heard back from anyone yet, and not sure if it'd be through our reseller or through you guys. (Sent westcam an email to check as well of course, but haven't heard back yet)

                    Comment


                    • #11
                      Originally posted by Wadep

                      Hey Jeremy, just curious- did anything ever come of this? Haven't heard back from anyone yet, and not sure if it'd be through our reseller or through you guys. (Sent westcam an email to check as well of course, but haven't heard back yet)
                      I took a look into it but I can’t replicate this in a debug session that makes this traceable in any meaningful way. I have a few other things to try but a bunch of other things have jumped on my plate in the last bit as we approach closed beta but once things free up here it will be back at the top of my list to try to understand and see what if there’s something we can do.

                      In short: I looked into it, couldn’t replicate it reliably in a way that I could trace where it was coming from. It got pushed back due to other issues but will be at the top of my list again here soon.
                      Software Development Manager: GibbsCAM

                      Comment


                      • #12
                        check that material tolerance in the Document contol is set to 0.3 min..
                        otherwise it would take ages to calculate,..

                        Comment


                        • #13
                          Originally posted by JeremyS

                          I took a look into it but I can’t replicate this in a debug session that makes this traceable in any meaningful way. I have a few other things to try but a bunch of other things have jumped on my plate in the last bit as we approach closed beta but once things free up here it will be back at the top of my list to try to understand and see what if there’s something we can do.

                          In short: I looked into it, couldn’t replicate it reliably in a way that I could trace where it was coming from. It got pushed back due to other issues but will be at the top of my list again here soon.
                          Thanks Jeremy. I understand, I just wanted to follow up. Look forward to hopefully a future resolution.


                          And Metco, material tolerance is .01" (and spline tolerance is .001"), so basically .3m. Thanks for that though, I hadn't checked that so it's nice to tick off one more possibility

                          Comment


                          • #14
                            Originally posted by JeremyS

                            I took a look into it but I can’t replicate this in a debug session that makes this traceable in any meaningful way. I have a few other things to try but a bunch of other things have jumped on my plate in the last bit as we approach closed beta but once things free up here it will be back at the top of my list to try to understand and see what if there’s something we can do.

                            In short: I looked into it, couldn’t replicate it reliably in a way that I could trace where it was coming from. It got pushed back due to other issues but will be at the top of my list again here soon.
                            Hey there JeremyS, just wanted to follow up on this and see if there was any progress

                            Comment


                            • #15
                              Originally posted by Wadep

                              Hey there JeremyS, just wanted to follow up on this and see if there was any progress
                              I had made a few small changes, but they didn't impact the different that greatly. I'm still working on this, though as it's very hard to replicate in a development environment and a fair number of items have required my attention, I haven't spent much time on this most recently.

                              We did make some drawing changes recently, which might have some impact on this.
                              Software Development Manager: GibbsCAM

                              Comment

                              Working...
                              X
                              😀
                              🥰
                              🤢
                              😎
                              😡
                              👍
                              👎