Trace mouse feature gets stuck

[kosso_olli]

Hello,
after switchting to SP1 for Vray 3.0, trace mouse feature often gets stuck somewhere in the image. The buckets then fly around in circular fashion, but they don't follow my mouse any more. Also, I cannot click any buttons in the VFB anymore, no looking at render elements etc. Switching to another window and then back to the VFB sometimes resolves the problem, but not always. This happens on every scene and it's annoying as hell
3dsMax 2015 SP3, Vray 3.10.03

EDIT: It is not the trace mouse feature. It also happens when I pan the image around. Then the whole VFB freezes.

Regards

Oliver

[vlado]

Thanks; will see what can be done about it. I don't get this here, but I have some suspicions why it happens.

Best regards,
Vlado

[vlado]

By the way, which Windows version?

Best regards,
Vlado

[kosso_olli]

Vlado,
the Windows version is Windows 7 Professional, Version 6.1 Build 7601: Service Pack 1.

[alexyork]

I have this same issue. Win 8.1 Pro. I have a feeling it's when the buckets are completing too quickly. They seem to track nicely when doing full renders but when doing quick rendermask passes for example they often "disengage" from the tracking and carry on from where they last were.

[kosso_olli]

Are there any news on this? I can reproduce this on any scene since updating to 3.10.03.

[vlado]

Not yet, unfortunately. If you get this regularly, can you get me a minidump file from the 3dsmax.exe process using f.e. Process Explorer and set it to vlado@chaosgroup.com ? It will help me figure out what's going on.

Someone suggested that downgrading Max to SP2 solves the issue, but I don't know if this will help you. Still trying to find a way to reproduce this here.

Best regards,
Vlado

[kosso_olli]

Vlado,
I generated the Minidump and sent it to your mail address. While doing this, I noticed that there were 4 processes of 3dsMax running, although there is only one instance of Max running. I suppose the other processes are leftovers from previous sessions. I killed them and so far the problem didn't occur in the last half hour.

[vlado]

Thanks! Good to know about the multiple processes too.

Best regards,
Vlado

[kosso_olli]

Okay, this is getting worse. When my render settings are set to be really quick for test renders, I don't even see any render progress bar or buckets moving. I just have to wait until the render finishes to see the result

[alexyork]

Okay, this is getting worse. When my render settings are set to be really quick for test renders, I don't even see any render progress bar or buckets moving. I just have to wait until the render finishes to see the result

Yep. I have the same thing here. I think the problem is significantly worse when the buckets have little work to do and are therefore changing quickly.

[vlado]

Ok. For some reason when there are too many screen updates, Max can't process them fast enough. Will see if there's anything to do about it.

Best regards,
Vlado

[vlado]

By the way, are you using DR?

Best regards,
Vlado

[alexyork]

By the way, are you using DR?

Best regards,
Vlado

Happens both with and without DBR. I notice this most of the time when doing local render mask renders of matte channels. They whizz by so fast that the buckets just lock and do their own thing until suddenly the whole buffer updates and the render is finished.

[vlado]

Ok, I see - will try to reproduce this here.

Best regards,
Vlado