Maxwell Render | Official public forum

I have a problem where all of a sudden from one render to the next my benchmark whent down from 270 to around 20. When i check the resource monitor i saw that the cpu useage had drop down from 100 on all 40 cores to very low values of around 3-5%. I tried restart and render to local disks insteed of our media server but still have the same problem.
I recently updated to 3.2 and it worked very well up until now.
If anyone can help i really appriciate it.

Same here, when rendering starts it is about 5-10% of CPU power and is still growing to ~80% near 15 SL.
After long time it is reaching 99% as it was in previous versions form rendering start.

I have seen this happen with intersecting geometries using alpha channels in the material and other bad types of geometry. I have had to isolate objects, render them in batches in order to find the culprit.

this was also present in 3.1. i was installing one build after another to get rid of this problem but to no avail.
thanks for the alpha maps info, it was driving me crazy due to the deadline.

Thx for the help, guess it might be the custom alpha then.

Have removed the custom alpha but still getting the same problem.

If you could share the scene, it would be a lot of easier to find the problem.

Try to render your scene with Override material. In Studio, go to Attributes Panel, Materials subsection and tick Override. Your scene will be rendered with default material, also you can choose other mxm file.

I will try that, thx. The mxs files are pretty heavy but will se if there is any good way of sharing them

Have you tried my suggestion, rendering groups of certain objects on/off? I do not know what is in your scene but for example. If I have a large scene with roads, buildings, trees etc. I will render the building layers with everything off. If that works fine then I will try the landscape layers with everything off. If that all proves all to be fine. The I render landscape with building. If I find an error, then I start by turning off groups of object layers in groups of 5 to ten layers at a time to find/ isolate the object/s, and maybe their materials, that are causing the problem.

Yeah that was a good idea. The problem was seprate output from multilight when i removed that the problem was gone, dunno if its a bug or just slow writing to disc. But since the files doesnt show up until the render is done i suspect that it might be a bug