Frame buffer not giving progressive feedback - Can't cancel Renders

[MegaPixel]

I've recently made the switch to Vray 1.5 SP5 on MAX 2011 Design 64bit coming from Vray 1.5 SP4 on MAX 2009 Design 64bit. One of the first things I've noticed is that the frame buffer is not showing me the progressive movement that the buckets make a crossed the screen. I'll see the initial start of the render, and then things pretty much don't change until the render is complete. I've also noticed that it's become increasingly difficult to cancel a render once started. (The two issues might be one in the same?). Has anyone else experienced this or have any suggestions for me?

Note: Running Windows XP64 (all updates and SP's)

Thanks All - Dave

[Morne]

I've had this also but more intermittant. I thought it was because I'm using compositor at the same time while also encoding with another program

[MegaPixel]

Even after a fresh boot with no other app.s running in the background, Max 2011 behaves this way. Is it a video card driver issue or perhaps some hyper threading settings? (/shrug)

[trixian]

Hmm are you using autograss by any chance?
This happens to me quite often when using it. It also makes my dual quadcore near completely unresponsive and even locks up my mouse (even though the render is using only about 30% of my ram)

[vlado]

Does this happen with the 3ds Max frame buffer, the V-Ray one, or both?

Best regards,
Vlado

[Morne]

hmmm I only use the vfb. It happens now and again. Using max 2011 but I can't say how to reproduce it. Then it does it then it doesnt

[trixian]

For me it happens with both (when using autograss) but the problem is worse when using max's fb. With vray's fb it does update quite a bit more, but seeing as my whole workstation starts to convulse and cough, the lack of updating in the Vfb could be due to this. So I'm guessing this is autograss doing something bad when managing memory.

[MegaPixel]

Vlado, it is happening with both the Max and V-Ray frame buffers and with great frequency.

trixian, no I am not using autograss.

[vlado]

Have you tried using the "Low thread priority" option in the System rollout? You can also try setting the 3ds Max process priority to "Below normal" in the Task Manager.

Best regards,
Vlado

[trixian]

As in regards to my problem, low thread priority is always on, and when rendering through BB, max is automatically launched in low priority. This even happens when removing one cpu through the affinity setting in the taskmanager. It still makes the machine stutter like hell. But I think I'm hijacking this thread now, so I'll shut up. I'd go shout over at the autograss forum, but I might as well shout at the wall.

[MegaPixel]

In my case, checking the "Low Thread Priority" did seem to help. Thanks guys