I have been experiencing this problem for about a month and it has annoyed me enough. Every scene that I use vray with, the default scanline raytracer messages window will always open when I hit render. I have checked all of my scenes for non vray lights and materials, and non of them have anything that would require the raytracer to activate. What’s even more suspicious is that once the render finishes, the raytracer message windows reports that 0 rays were traced, signaling that the raytracer did nothing to begin with.
Every time I go into the scanline > raytracer tab to turn off the option to “show messages”, it mysteriously gets turned back on. Today I discovered that if I turn this off, save the scene, then re-open the scene, it is again back on! So something here is not right.
I am using vray with 3dsmax 2012 64bit on Win 7. Is anyone else seeing this?
Attached is an empty 3dsmax 2012 scene. The scene is saved with the raytracer show messages option turned off. Yet as soon as I open the scene and go to this setting, it is shown as turned on. So something is turning it back on when the scene opens. This is really annoying! Can someone please try and open this scene and see if they get the same behavior?
Here is a fix-
Change your renderer to scanline. Under the “raytracer” tab there is a “show messages” check box. Make sure that is unchecked. Switch back to VRay. Problem fixed.
Actually that does not fix the problem, or at least permanently. If you try the steps I listed in my post, you will see that the messages always turn themselves back on. Did you try the test scene?
This has been happening to me a lot lately… weird but for me it brings up a Blur Studios Ray something or other dialog stating there is a problem. Annoying…
I finally resolved this problem. It turns out that somehow the old materials from when the scene was a mental ray scene somehow where still there. Even though these materials where not visible in the material/map browser, you could see the maps they used in their reflective slots listed in the Asset Manager. In order to fix it, I just merged the scene into a new one. Very odd situation, but that fixed it.