VRay Frame Buffer - messing me about.

[deflix]

Hi I have an annoying issue that you may know a remedy for.


I render an image and a large number of elements. I am using MAX2013.

Once complete the Vray Frame Buffer window is extremely slow and unresponsive, and cannot be moved or closed.
It then does this weird thing where it oscillates between 'not responding' and 'normal' quite rapidly and for a very long time.
It sometimes ends up crashing MAX.

Is this a graphics card error, or a known bug in Vray?

Cheers,

[super gnu]

i have exactly the same thing in max 2012 x64.. didnt until recently, but i had it in the past too. seems to be intermittent.

im not sure (rendering at the mo) but i believe turning off "progressive refinement" for the viewports helps a bit.

[deflix]

finally I don't feel alone! thanks for the heads up dude..

[mario74]

same here with max 2013... i tried also different graphic cards, same thing.

and this happens not always, only sometimes and this makes it hard to reproduce.

[vlado]

Try using DirectX viewports instead of Nitrous (or at least disable progressive refining for Nitrous); also turning Windows Aero off might help.

Best regards,
Vlado

[joconnell]

This is interesting - I've seen nitrous cause a lot of viewport issues to the extent of messing with the transforms of objects so I'm very wary of it.

Vlado, during network rendering whether with backburner or with deadline or whatever, does max call upon the viewport in any way shape or form, so that something like nitrous might actually mess with your rendering?

[fraggle]

+1 for bad vray buffer

[vlado]

Vlado, during network rendering whether with backburner or with deadline or whatever, does max call upon the viewport in any way shape or form, so that something like nitrous might actually mess with your rendering?

I don't really know. Ideally, no viewport code should be executed during network rendering, but I don't know if this is actually the case.

Best regards,
Vlado

[deflix]

Yes reverting to direct 3d appears to have eliminated this issue. I suspect it probably has something to do with the way nvidia have worked with autodesk on the drivers for non-pro cards in MAX....i.e. sabotaged!
I guess nitrous will only really work if you pay the huge premium for a Quadro card.

[vlado]

I don't think so; I think it's directly related to the way Nitrous handles progressive refinement - it gets in the way of the normal window message processing.

Best regards,
Vlado

[mario74]

i am not quite sure this is the point. i have a quadro 4000 here and a gtx 680... both react in same way with nitrous

reverting to direct 3d solve this also here - with both cards, but speed is not close to nitrous!