"Turn on all cores" script

[simmsimaging]

Hey -
Just switched my workstation over to one of my i7 machines. Running Max 2009 and Vista64. Direct rendering (non-DR) renders with 4 cores only, but if I run this script called "turn on all cores.ms" which I got somewhere, I think from Vlado? It renders with 8. However, I have to run this script everytime I start Max.

I tried sticking it in the scripts/startup folder but it did not seem to work. Is there someway to make it "stick" or is there a permanent fix for this problem?

Thanks in advance
b

[glorybound]

all cores

can you share the script?

[simmsimaging]

For sure - someone shared it with me after all


EDIT: I guess the attachment didn't work and I don't know how people embed scripts here, so here is a link:

http://www.simmsimaging.com/upload/f...l_cores.ms.zip (0.19 KB)

[vlado]

Do you use a MaxStart.max file that overrides the default value for the "system_numThreads" option? Zero is the default value for this, so you shouldn't need to resort to scripts or any of that kind of stuff, but it is possible that your maxstart.max file overrides it with some specific number.

Best regards,
Vlado

[simmsimaging]

Thanks Vlado.

I do use a Maxstart file - I was trying to get it to setup the material editor with Vray materials (which didn't work anyway - can't figure that one out). I am not sure how to tell if that option is set, but it's not something I did intentionally. How would I find out?

If I ran that script and then saved a new MaxStart.max file would that take care of it?

b

[vlado]

If I ran that script and then saved a new MaxStart.max file would that take care of it?

I think this will work for newer scenes, yes. But if you load a scene that has already been saved with that option set, you'll need to run the script.

Best regards,
Vlado

[simmsimaging]

Thanks Vlado. That seems to have been the issue. I will resave the MaxStart file and hopefully that will be the end of it.

b

[Fekta.studio]

simmsimaging I have the same issue with my i7, but I don't need to start the script each time anymore, just copy you script in Scripts\Startup, that solve it for me for every scene. But change the num of threads to 8 - renderers.current.system_numThreads=8 thats all. cheers

[vlado]

It would be best to really leave or force the number of threads to the default zero, so that V-Ray can automatically use the correct number, without the need to modify your scenes each time you change your machine.

Best regards,
Vlado

[Fekta.studio]

It would be best to really leave or force the number of threads to the default zero, so that V-Ray can automatically use the correct number, without the need to modify your scenes each time you change your machine.

Best regards,
Vlado

Yeah , but if I leave it to 0, I have only 4 CPU to render, and force me to manualy assign to 8, and I don't change my machine that often . Anyway it seem on dual quads thats not happening , they uses all the CPU - 8, but on my workstation with I7 - 4. With force CPU to 8 all problem gone and I can focus to my work rather worried how many CPU are rendering


PS. the script adds 8 CPU not in the scene it seem, but for my PC only. On quad core PC scene rendered with force to 8 on I7 is rendering with 4 cores.... but quad core PC have no script that force it to use 8 CPU-s in startup folder like in i7.

[simmsimaging]

Thanks Andro. It seems to be working fine now set at 0. The recurring problem was fixed by re-saving my MaxStart.max file with that script activated. Maybe that will be of use to you as well?

b

[glorybound]

script

Would you need this on all slaves as well?

[simmsimaging]

Not sure why, but the slaves all seem to render fine. Even the workstation would render with 8 cores when used for DR renders. It was only when I made that my workstation and initiated renders that I had this problem.

b

[glorybound]

DR

There has to be a way to monitor slaves when running the vray sprawner. Right now I am finding I need to restart all my vray sprawners after every render, is this normal? Even when it seems like the vray sprawner is woking only 3-5 % of my CPU is being used and 1 of my 12BG per machine is being used.

[simmsimaging]

I use the restart on render end option of DR all the time anyway. It just runs smoother that way, although every once in a while I have to restart one again anyway. I think it's just a timing issue of when renders start versus nodes restarting, but I have never figured it out for sure.

In any case, all my nodes run full out 100% when a DR is going, but the RAM usage varies with each scene.

b