VFB issues when moving to different monitor

[GMTJay]

Hi. I'm running V-ray for Cinema 4D on a MacBook Pro with an external monitor. I noticed the other day that if I open the VFB window and move it from the external monitor where C4D is running to the MacBook display, the VFB loses the render buttons to the right. I found that if the main C4D window is on the laptop display, the VFB window opens fine. However, if I then move it to the external monitor, the VFB appears to be taking up only a small portion of the overall window, and resizing it doesn't do anything. I have some screen grabs in case they're useful:
Main C4D window on external display
VFB window moved to laptop display—buttons missing
Main C4D window on laptop display
VFB window moved to external display—doesn't fill window

2019 MacBook Pro running Big Sur 11.5.2. C4D r24. V-ray 5.10.22.

Jay

[zAppledot]

I was about to post this same exact behavior. If I move the VFB or Cosmos window to another screen it doesn't fit the window same as your screenshots. This does not happen with native cinema 4d windows, only the vray windows.


I am on an iMac Pro running macOS Big Sur 11.5.2

[aleksandar.kasabov]

Hello,

This is a known issue, caused by different DPI settings for both monitors. It has already been reported (bug ID: VC4D-1086) and I will let you know once we have more information on the matter.

If you set the DPI of the MacBook as the DPI of your external monitor the issue won't happen anymore. Alternatively, once you move the VFB window to your other monitor, you can use the additional menu at the top left corner and "undock" the window. Thank you.

[GMTJay]

Thanks, Aleksandar, the trick about undocking the window is a quick and simple fix (I should have thought to try it myself). In case anybody comes across this who has the problem (and you missed Aleksandar's link):


FWIW, I couldn't find a setting for the laptop display that didn't have the problem, but this is a simple workaround.

[zAppledot]

Sweet, now i can use vray on more than one monitor. Thanks for the workaround!