I would recommend reading up on the Benchmark 2.0 thread, for some ideas about which current Main Processors are the best. That takes time, so while the information is being passed to the Manager, that process pauses Mastercam until it is complete.Īlso, there are certain paths which are not Multi-threaded at all, which means Mastercam is unresponsive, or idle, while those paths are processing. What that means is "Mastercam has to package all the data, and ship it off to the Thread Manager, before it can be processed as a Parallel Thread. Only the Dynamic and Surface High-Speed paths support Multi-threading.īut, there is also the "pipe to the threading manager" to consider. That said, Mastercam makes poor use of Multi-threading in general. You can gain processing advantages, if you say "have an 8 core chip", and you set the max number of threads to 8. There is a lot to consider in the response.ġst, I believe the default for "# of Threads" is only 2. The Multi-threading is a loaded question. I don't think there is an option to disable it. The Mastercam Logger must be manually turned off every time you boot Mastercam. I think you can modify the Operation Defaults File, to modify each Default Operation Type, to default the setting to "off". I believe there is an option on each different Toolpath dialog box. Is there a way to configure Mastercam "Tool Display" to always be off, or is this something I need to do each time I create a tool path? Do I Have to manually close the event logger each time I start Mastercam? Is it faster to set the hyper threading to only do one task at a time?įor the Tool Display, I'm not sure if there is a Global Default or not. (Unfortunately, this must always be done manually.) This can give the Thread priority for calculations during each clock cycle. Set it to "one thread per core on your processor".Īlso, when Threads are generating, you can Right-click on the specific Thread (path), and change the Processor Priority to "High". Here you can set the maximum number of simultaneous threads. If the no threads are actively generating, click on the "settings" button (exclamation point). You can pause, stop, and resume the threads. If you are generating multiple "multi-threaded" paths at a time, open the "Multi-threading Manager" (View Ribbon), and look at the threads that are generating. Whenever I boot up Mastercam, the first thing I do is shut this off. You can also look in the "system tray" for the Mastercam Event Logger Icon. If you turn this off (select Ops > Right-click > Edit Common Parameters), it can seriously boost the regeneration time. If you are generating lots of large paths: Mastercam has a "tool display" setting, which basically "draws" the lines and arcs of the path, as the path is generating.
Mastercam 2019 post crash how to#
Does anyone know what causes this? How to Fix it? I was able to replicate this issue on our reseller's computer and stumped them as well. This makes it cumbersome when I import the operations to use at a later date. I end up with duplicates of the first 10 operations, but with no geometry. I export and for some reason it selects the first 10 operations and does those too. Then I un-check the box, and just select the remaining Ops. I export the first 10 with the geometry and they export as expected. Lets say the first 10 Ops have geometry and the last 30 don't. When I export Ops, I Export some ops with Geometry and some without. Wondering if there is anything that I can do to minimize the frequency of this happening? Can I tweak some settings to give me better stability?Īnother Bug I get is when Exporting Tool Paths. I am running a Dell Precision T1700 with an Intel i7-4790 at 3.6 GHz. I save often but I do lose some production every now and again. Not a huge number but it seems to be about once per week. I know this could be a million things but was wondering if anyone else gets frequent crashes? I decided to keep track on my white board the number of times it crashes since January 1st. First off, I get some crashes in thee middle of tool path regens. I have a few bugs when using 2019 that I'm not sure if it is me or the software.
0 kommentar(er)
