- Sun Jun 12, 2016 8:38 pm
In Rhino, you set the number of threads in Scene Manager > Output > Engine > Threads; in Studio, click Render Options in the Scene Tree, and set Scene > CPU Threads in the Attributes Panel. You can use Task Manager to find how many threads you have to work with; on CPUs without hyperthreading, you have one thread per physical CPU core, while on those with hyperthreading, you have two. If you are overheating with threads set to 0 (i.e. auto-detect, or "Automatic" as Studio shows, when you set the value to 0), you might try setting the value to something like 2 fewer than the total number of threads available, to begin with.
Be aware though that by doing this, you will slow down the render time, proportional to the decrease in threads Maxwell is allowed to use; a better option, provided you do not find by searching that your model of laptop has general overheating issues, would be to fix the issue -- it could be that over time, dust has built up, and the heat sink is no longer cooling the CPU as it should. On the other hand, it could also be that the manufacturer did not foresee people stressing the machine to this degree, so as I suggest, you may want to begin by searching the web to see if other people report similar issues.
In checking this out, remember to keep in mind that it may not actually be an overheating issue at all, and could instead be something like a problem with the memory or a hard drive. Either way, what we can know with certainty is that it is something with the hardware, because it is not possible for software (drivers not included) to shut down the machine, except by asking the OS, but that is not what is happening here, because Maxwell doesn't ever do that.
Next Limit Team