7GB Vray log file?

[Dman3d]

One of our team had an "out of disk space" error when he came in this
morning. He said he found his vraylog.txt was 7GB.

Now I did not see this file as he deleted it before telling me, but his
machine had been erroring out on renders for some time on various
jobs. We always slave machines so I think what was happening is he
would always slave his machine, errors insue and the log file grew.
I thought the log file always started over at some size or point.

We run two managers and this particular machine was mostly slaved to
the manager I dont use. Would it be possible for this to occur on other
machines and if true what would cause it?

At any rate there was a period of time where users did not have admin
rights on their own machines, we are now. Does any of this sounds
plausible? I cant imagine how much text would have to be in a file to
make it 7GB!

The other wierd part is he said he deleted it and 14GB cleared on his drive and his machine is (of course) running faster and smoother and
appears to no longer error out on jobs.

[Olli96]

make sure every object got proper uvw coordinates. i had this some while ago where i forgot to remap an xfrog tree and my log file was full with missing uv coordinate messages...

Olli

[studioDIM]

that's normally the case with XFrog tree: their W coordinates are bad (ie. +#IND or something like it), and vray outputs a warning for each textured vertex of the mesh, per rendered frame.
A workaround Vlado suggested was to set the vraylog file path to empty in the vray system options.
Or simply lower the log sensitivity by 1 (at 2 it should be fine, or better still at 1).

Lele

[Dman3d]

Thanks!