Vray 6 - Backburner - Extreme Performance Issues

[RedStar]

Running into another issue with Vray6. If I render an image locally the computer works just fine, I can multitask, move around, open folders, etc. When I send the 100% same job/file to my backburner and have the same image render on the same machine but now through the backburner server my computer is almost frozen, extremely delayed perforamnce, just impossible to work on.
This is a fresh issue only on vray6. I can say this 100% because I am re-rendering the same jobs and the performance issues are on all my computers.

Not sure what is causing this. I ask the admins please do not blame my computer or 3d max. AGAIN, this only started happening with Vray6 update and is happening on 14 of my machines, THIS IS NOT AN OLD ISSUE! I am sorry to be putting things in caps, but based on my last problem which was finally resolved, it seems the staff likes sometimes just points fingers at Autodesk or PC issues versus examining the issue at hand which is caused by Vray6.

[3d-laboratory]

I have no soluttion but questions:
- Which version of backburner do you use?
- Are you working on the same project with the same assets, textures e.g. as in the scene which is rendering through backburner?
- What happens if your own computer is not server at the same time
- What happens on the other render nodes if the job from your computer is rendered there, can others work then fluently on that machines rendering your job at the same time?

[RedStar]

I have no soluttion but questions:
- Which version of backburner do you use?
- Are you working on the same project with the same assets, textures e.g. as in the scene which is rendering through backburner?
- What happens if your own computer is not server at the same time
- What happens on the other render nodes if the job from your computer is rendered there, can others work then fluently on that machines rendering your job at the same time?

- Latest Backburner. 2019. I checked Autodesk website today and it is still the same.
- I am. But I actually just made a teapot scene to show how awful the issue is.
- My personal computer is usually never on server. I have a seperate server for backburner to run off of. My main workstation is usually either free or being worked on. But when I grab lunch or head out of office I fire up backburner to keep progress going, thats where I noticed the awful perormance.
- All computers act the same, absolutely useless and frozen.

I actually went ahead and created a youtube video showing the issue. Used my cellphone to make sure no delays in recording. Link below to the video along with timestamps of where to look since its realtime there is a lot of dead air.
https://www.youtube.com/watch?v=08gn-5RRcSo

0:14 Normal Render on PC 2:30 Render 100% same file through backburner 3:14 Frozen Area and PC Specs 3:47 Render Jumps Progress

Also, in case anybody is interested. Here is the scene file that I did the test with. Again, works 100% normal as you would expect when opening max locally and rendering locally, as soon as I use backburner on the same file it goes to hell.

https://1drv.ms/u/s!AnEPb6dOabGJ1wak...Mxpi4?e=PyhN5z

I even used 100% Vray assets to help reduce pointing fingers at other plugins like Forest Pack or dense Cad data.

[alchymista]

Hello. Same for me after updating to the latest vray 6.
Rendering via Bacburner causes the system to freeze (lagging) / as RedStar describes in his video.

• Installed V-Ray v.60004
• License server 6.0.0
• 3DS Max 2021
• Backburner 2019.0.0_5.

My previous V-Ray v.52023 was fine in backburner.
Is there any way to prevent the system from lagging in backburner?

[RedStar]

Hello. Same for me after updating to the latest vray 6.
Rendering via Bacburner causes the system to freeze (lagging) / as RedStar describes in his video.

• Installed V-Ray v.60004
• License server 6.0.0
• 3DS Max 2021
• Backburner 2019.0.0_5.

My previous V-Ray v.52023 was fine in backburner.
Is there any way to prevent the system from lagging in backburner?

Glad I am not the only one with this issue. I just emailed Chaos as well since this topic is being ignored on the forum. If they find a solution I will let you know as well.

[response]

Having the same issue while using Pulze Render Manager (machine locks up). Local render no problem. Have reverted back to Vray v.52023 and problem has gone.

[RedStar]

BUMP. This is still a major issue and is still being ignored it seems.

[^Lele^]

Something is definitely afoot, and not through BB either.
We haven't communicated back because we're still looking into it, and it's not obvious yet what it could be.
Kindly be patient for a bit longer.

[RedStar]

Something is definitely afoot, and not through BB either.
We haven't communicated back because we're still looking into it, and it's not obvious yet what it could be.
Kindly be patient for a bit longer.

Thank you so much for the reply Lele!
No problem at all and no rush, just wanted to see if the team is looking into it or not.
Apprecaite your efforts!

[maria.keskinova]

Hello,
we have reproduced it on our end as well and are working on narrowing it down, dev are already looking into it, too.
Sorry for the delay!

[Joelaff]

We are seeing this with Deadline as well. I am glad this is not on our end. Even the newest hardware gets crazy slow.

[RedStar]

We are seeing this with Deadline as well. I am glad this is not on our end. Even the newest hardware gets crazy slow.

Now you know its a big problem when something as fancy as deadline also has this issue. I can understand the free backburner having a bug, but deadlines amazing haha.

[yavor.rubenov]

Overall this is related to the fact that we run rendering with Normal priority when started with Backburner/Deadline because we assume this is some render server that is not used for anything else. Rendering is tiny bit faster this way.
When rendering is started from a regular Max session - we use the lowest possible priority.

While we are looking for solutions - if you want to use the BB machine while rendering you could limit the number of threads used for rendering to one/two less than the total available threads. You could do that with the VRAY_NUM_THREADS environment variable.

[RedStar]

Overall this is related to the fact that we run rendering with Normal priority when started with Backburner/Deadline because we assume this is some render server that is not used for anything else. Rendering is tiny bit faster this way.
When rendering is started from a regular Max session - we use the lowest possible priority.

While we are looking for solutions - if you want to use the BB machine while rendering you could limit the number of threads used for rendering to one/two less than the total available threads. You could do that with the VRAY_NUM_THREADS environment variable.

So question, why not just leave it the way it was for years without issues? Why create an issue and tell users to find work arounds? :/

[yavor.rubenov]

Actually it has been like this since V-Ray Next, no change in that direction. I was just explaining why there's a difference between running from local Max and from BB on the same machine