![]() Modifying the default limits has not been officially tested and certified by SOLIDWORKS. NOTE: Best practices should be taken in such a way that the default GDI limit should suffice. It’s highly recommended to make backups before making any edits. ![]() Contact your IT or someone with knowledge of working in the Windows Registry before making any changes. If you are setting the limit value at 20,000 or greater, consider making changes to your workflow as this may start affecting your overall operating system functionality.ĬAUTION: Improper changes to the Windows Registry can damage the overall operating system. Increases should only be done at small increments until the warning messages stop for your workflow (i.e. The theoretical max value per session in Windows 7 or 10 is 65,536, though you should always keep it far below this limit. Below is a Microsoft Library article showing the GDI registry key location of the 10,000 default limit. The Memory tabs Processes section displays key. If you must have many documents open simultaneously, the object limit per application can be increased manually through the Windows registry. The tool look depends on the Windows version, but the overall feel is the same. These may be causing significant GDI object use. Restarting SOLIDWORKS will reset the GDI Object count for a new session.Īlso check what add-ins and custom macros you are running. Closing all files won’t necessarily bring the GDI Object usage back to the original amount when first launching SOLIDWORKS (typically under 1000 objects), but it should decrease to an acceptable value of close to 1000. Browse our FAQ page for links to SOLIDWORKS Recommended Hardware.īest practice is to avoid having many documents open at the same time within SOLIDWORKS. At some point it’s time to consider if more RAM should be installed on the machine. You can also increase the Virtual Memory available as outlined in this blog article. It could be another program utilizing most of the memory. If you are running low on memory (or commit charge), you’ll receive a SOLIDWORKS Resource Monitor Warning that “Available system memory is low.” You should close other applications/processes/documents to free up memory. The SOLIDWORKS Resource Manager, originally introduced in SOLIDWORKS 2010, tracks the usage of Physical Memory, Virtual Memory, User Objects and GDI Objects. Newer versions of the SOLIDWORKS Resource Monitor provide more insightful notifications. This could have been from depleting all available memory on the system (physical and virtual) or Windows GDI or User Object limit being reached. In past versions of SOLIDWORKS you may have seen warnings that “system resources are running low”.
0 Comments
Leave a Reply. |