[An...] Posted 2 hours ago Share Posted 2 hours ago Hi, after i was informed that 2026 release had indeed a flaw regarding the utilization of high core count CPU (i have 32C-64T) and the software was using maximum 16 Threads even if in option the logical core were set to 64. After updating to SP1 I observe the exact same behavior, so nothing changed apparently. I tried retesting 2025 release with latest SP installed and it uses all cores (in option i have the flaw on for use all cpu resources). I took a 18GB files of acquisitions and tried timing the 2 releases: 2026 did it in 4 minutes and 16 seconds while 2025 in 1 minute and 57 seconds. For us speed of polygonalization is quite important since we need the meshes right after the acquisition. If you need any king of specific information of log, setting, machine detail etc I'm welcome to give them to you to fix this problem with 2026 release. 1 Link to comment Share on other sites More sharing options...
[Na...] Posted 1 hour ago Share Posted 1 hour ago Hi Andrea, I will have a look internally and come back to you. If it's a different issue we probably need sample data and handle it in a support case. Nanno Link to comment Share on other sites More sharing options...
[Na...] Posted 21 minutes ago Share Posted 21 minutes ago Hi again, it was fixed with 2026 Service Pack 1. Please check the config file: C:\Users\*USER*\AppData\Roaming\GOM\2026\gomsoftware.cfg The relevant settings are: Global_ControlMaxAllowedParallelism = 12 EnableHyperCore = 0 EnableHyperCore should be set to 1, and the other setting to the maximum number of logical cores of your system. The setting in the preferences of Inspect 2025 will be carried over to the 2026 config, when 2026 is reinstalled. Alternatively edit the settings in the config file. Please let me know if this worked Nanno Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in