hexagon logo

The more i run a program the slower it gets

Over time when I run a program and hit cltr+U to start it it takes sometimes upwards of a minute to start. Compared to when I created the program it started almost immediately. My theory is that the program is keeping all of the output dimensions logged somewhere so it is bloating the program. I've tried using the print command to delete previous instances however that only seems to "delete" the from the current report display. I say this because I can remove the line and it will show my previous measurements again if I open the report window.

How do I prevent the program from getting slower the more I run it?
  • If you are using Ctrl+U to start a program each time, it is doing a partial execution from the cursor. When you do that, the software will first refresh the report with the previously measured data, or something like that.

    It is more ideal to use Ctrl+Q to execute the whole program from the beginning. That will start everything fresh and won't require all that up front processing.

    However, if you have some reason to always start a program from the middle using Ctrl+U. You can first go to the File menu and select Reset Execution List. That will clear the past report data and it won't have to do all that up from processing.

    This help file article explains it better: Reset Execution List (hexagonmi.com)
  • I appreciate your help! I was taught to use ctlr+U to start the program. I will start using the ctrl+Q.
  • Keep in mind if you use the CTRL+Q method it will run the manual alignment each time as well unless you highlight it and hit F3 to unmark it.

    What I do is I have the reset execution button on my toolbar that will clear the report. To do that right click the top tool bar and go to Customize>Toolbars>Menu Items>File and at the bottom of the file tree is the reset execution button. Select it and add it to one of your toolbars on the right.
  • Reset will reset the execution list which the report uses to generate. Each re-execution of a command causes the command to be duplicated and added to the list. Full execution clears the list before starting. The report is just using the commands currently in the list.
  • This might have to do with your PC capabilities, or other variables contributing to it (like the size of your CAD or the number of labels in your graphic display window).
    You can always switch off displaying all CAD, as a quick test.
    Also, when I'm done programming a routine, before I set it as read-only and lock it down, I execute the entire routine offline, then right click on a feature label and select "Hide all IDs". From that point forward, your graphics card will only be rendering the CAD, and not all the labels that get produced and re-positioned while panning and moving the view around. Otherwise, some routines have hundreds of labels that just bog the whole system down (even with great hardware).
  • I wanted to visit back and say that using the Ctrl+Q has resolved the issues I had of a slow start. The programs run immediately now. Thank you everyone for the help