The FOV issue is one that TRimble acknowledged. It doesn't work like before:
This is a known issue that we're investigating. If you press "Tab" or click in the measurements box to adjust the value you can see this error. To work around the problem, click once to start using your SketchUp tool, move your mouse a bit, then start typing right away without clicking or tabbing into the Measurements box. You can then specify your exact value, then press return.
Does anybody know what happened to the ability to key in the desired value for the FOV or the eye height.
I now get the shift part for the FOV, but what about the eye height?
Is there a means to enter values anymore????? It was quick and efficient.
What if a component has two materials in it? That's where is seems to get a bit tricky unless the component is placed a layer NOT associated with a material. Advice? Thanks!!! 
I just want to make sure that nested components are not causing crashes...
Hello Everyone!
I want to make sure that I am doing this right.
I have a window assembly component with metal and army green glass. Each of the layers inside the component is on that layer. I put the component on layer 0.
Is that how this is done?
mac Vray 1.6
Mac Sketchup 2013
10.8.4 MacBook Pro July 2012 Graphics cad activated
Best,
William Huchting
@dkendig said:
can you reliably reproduce this issue by following certain steps? I can't fix what I can't reproduce, I'm still not getting this error in my tests.
I'll give it a shot.
Thanks!!!
I get the blank screen now with only 1 file open and it is in the finder too. It disappears when I quit Sketchup.
"V-Ray doesn't use web dialogs, and I am unable to reproduce the issue at all on my machine. We don't handle multiple windows of SU being open on OSX at all, because they have an entirely different way of doing things under that environment. It's something we would like to address soon, but so far have found no simple solution for it. We support 1 SU window open on OSX at a time. If you do open a second window, you will corrupt your scene, get crashes, and other horrible things. Thomthom's utility will likely not be helpful at all with the way the OSX version of SU works."
Would you send an email to all Mac OS users explaining this?
It would be very helpful!!!!!
I get the same thing on my Mac all of the time.
Maybe the latter. Devin, what does the bug report say that it was related to the file I sent you?
The form topic posted by Olishea above was helpful.
The debugging command "clear texture cache" has seemed to stop the crashes for now! 