Maya 2012 + V-Ray 2.0 = completed render freezes Maya GUI

Hello,

We have an urgent issue where the Maya 2012 GUI totally freezes just after completing a render in the V-Ray frame buffer. This is where Maya stops its output:

[2011/May/18|23:29:00] V-Ray: (Estimated time remaining: 0h 0m 0.0s): 100 % completed
[2011/May/18|23:29:01] V-Ray: Number of raycasts: 6138781600
[2011/May/18|23:29:01] V-Ray: Camera rays: 650476611
[2011/May/18|23:29:01] V-Ray: Shadow rays: 4566503320
[2011/May/18|23:29:01] V-Ray: GI rays: 137751120
[2011/May/18|23:29:01] V-Ray: Reflection rays: 836332084
[2011/May/18|23:29:01] V-Ray: Refraction rays: 3687934
[2011/May/18|23:29:01] V-Ray: Unshaded rays: 0
[2011/May/18|23:29:01] V-Ray: Number of intersectable primitives: 2337740
[2011/May/18|23:29:01] V-Ray: SD triangles: 2335951
[2011/May/18|23:29:01] V-Ray: MB triangles: 0
[2011/May/18|23:29:01] V-Ray: Static primitives: 1788
[2011/May/18|23:29:01] V-Ray: Moving primitives: 0
[2011/May/18|23:29:01] V-Ray: Infinite primitives: 1
[2011/May/18|23:29:38] V-Ray: Successfully written image file “P:/server_path/maya//../render/maya/testrender/tmp/Exterior_v006_ls_renderCam_masterLayer..exr”
[2011/May/18|23:29:38] V-Ray: Total frame time 5h 20m 59.2s (19259.2 s)
[2011/May/18|23:29:38] V-Ray: Total sequence time 5h 20m 59.6s (19259.6 s)
[2011/May/18|23:29:38] V-Ray: Render complete
[2011/May/18|23:29:38] V-Ray: ========================
[2011/May/18|23:29:38] V-Ray: Clearing exporter memory…
[2011/May/18|23:29:39] V-Ray: Total time clearing exporter memory 0h 0m 0.1s (0.1 s)

The bottom left progress bar inside of the Maya 2012 GUI says 100% but Maya is totally unresponsive.
Have anyone seen or experienced this and is there a known work around or perhaps an updated and stable build where this has been adressed?

Extra info:
Maya 2012 64-bit
V-Ray 2.0 official release

Which OS are you using?

Windows 7 Professional 64-bit. No service packs or anything like that.

Do you have the V-Ray frame buffer enabled or disabled?

Best regards,
Vlado

The V-Ray framebuffer was enabled and the image was fully renderered. No incomplete buckets or anything like that.

Does it work with the regular Render View?

Best regards,
Vlado

We never use the Maya render view any more, now that we have the excellent V-Ray framebuffer :wink:
However, we could give that a try tonight and I will let you know how that goes.

Happened to me also. Only with VFB with standard window it works, but after hard restarting Maya.

Ok then; will be looking into it. There is probably something that we don’t do quite right with Qt…

Best regards,
Vlado

The problem persists (although inconsistent) and it also happens when just region rendering using the V-Ray framebuffer.

Seeing a simliar (if not the same) problem here. VFB appears to freeze everything, but CTRL-Alt-DEL > Task Manager “switches” to windows (and Maya/VFB) still working fine.
Happens every time I’m going to save image/multiple images from VFB as well. It all appears to freeze, with the file requester hiding behind the VFB. Again, CTRL-Alt-DEL > Task Manager fixes this (feels like alt-tabbing, but using the task manager).

It’s a workaround, but a terribly uncomfortable one at the moment.

I have V-Ray also locking up hard while rendering with the Maya Framebuffer and VFB. The only way to fix this is to set Max CPU’s to 10 instead of 12 on a 6Core proc. But there currently isn’t a way to limit CPU’s in RT CPU mode is there? That also causes my computer to lock up until the render finishes.

Metzger:
You can limit the number of threads used by starting V-Ray Standalone manually and specifying -numThreads=10.
The complete command will be “full_path_to\vray.exe -server -numThreads=10”

I forgot the -portNumber flag, so the complete command is “full_path_to\vray.exe -server -numThreads=10 -portNumber=20207”

I will try that, but what about for RT CPU mode?

Metzger: Have you checked if you’re running the vrayspawner (vray slave)? If you’re running it, try to stop it and see if vray rt cpu will start normally.

Which build of V-Ray is this?

Best regards,
Vlado

Nevermind, this is fixed for the next night build tomorrow.

Best regards,
Vlado

Ah sorry for the delayed reply, I was on the road.

Happy to confirm the latest nightly has it all fixed perfectly, thank you :slight_smile: