top of page

What You Need to Know About Bg Renderer Pro 14 and Its Amazing Features

  • canalolisgaro
  • Aug 16, 2023
  • 3 min read


The first M1 Max spec that jumped out at me is the 64 GB of unified memory; having this amount of memory meant I could finally render some of the largest scenes I have for my hobby renderer.To test out the M1 Max with 64 GB of RAM, I chose the forest scene from my Mipmapping with Bidirectional Techniques post.This scene has enormous amounts of complex geometry; almost every bit of vegetation in this scene has highly detailed displacement mapping that has to be stored in memory, and the large amount of textures in this scene is what drove me to implement a texture caching system in my hobby renderer in the first place.In total, this scene requires just slightly under 30 GB of memory just to store all of the subdivided, tessellated, and displaced scene geometry, and requires an additional few more GB for the texture caching system (the scene can render with just a 1 GB texture cache, but having a larger texture cache helps significantly with performance).


Same. I am unfortunately on OSX 11.5.2, and wanted to utilise the command line renderer, but this bug prevents me from doing so, or using any plugins like render garden. But good to see it's being looked at as Dan commented below.




Bg Renderer Pro 14



The Vaadin Web Components no longer support to render content.Use renderer functions instead (see the "Replace Template Elements With Renderers" section).Alternatively, you can use the @vaadin/polymer-legacy-adapter package which has been created to maintain backward compatibility.


Changing the ANGLE backend to OpenGL only "fixes" the issue by disabling hardware acceleration completely as evidenced by chrome://gpu. Similarly, changing the MKS renderer in the vmx file to OpenGL has the same effect (Yes, of course I made the change while the guest was shutdown). This is further verified when vmware-vmx.exe and mkssandbox.exe no longer appear in the NVidia Activity monitor. A windows guest on a windows host must use DirectX in order to achieve 3D acceleration as stated in the following articles (and elsewhere in the community):


I don't know where the root of the problem lies. This problem has been around for some time (maybe since version 12.5.x, could be earlier) but does not seem to have affect all configurations (host GPUs). The reason I stumbled on the OpenGLRenderer workaround was the problem did not show up when running on Fusion on MacOS did not exhibit those problems (at that time Fusion was still using OpenGL renderer to deliver DX10/OpenGL 3.3 on Windows VMs, current version now use only Metal). The problem also does not show up on VMs running on Linux hosts as Workstation Pro/Player uses GLRenderer for accelerated graphics.


I don't get that problem (white screen, rendering problemsw with Chrome) with a laptop with Skylake CPU HD630 with GTX 960M on a Windows 11 Home host. Switching to GLRenderer for VMware Workstation also does not disable 3D acceleraton (i.e. mks-sandbox.exe still appears on GPU Activity and Chrome inside still has "Hardware Acceleration"). With laptops, Nvidia Control Panel lets you choose a Default graphics processor so there is no need to use mks.dx11.vendorID to choose. With Intel HD630 as default and OpenGL renderer in the vmx, the horrible rendering problems even with Windows logon/menus still occur though.


So it is strange that once you switched to GLRenderer that the Nvidia GPU is not being used and 3D acceleration is disabled (hence disables Chrome graphics acceleration). Unless the vmx entries you added resulted in disabled DX11renderer and the GLRenderer was not enabled (typo error perhaps??)


Which MKS renderer I use is not the issue here because neither of them work. GL doesn't because, as you say, it is not supported in a Windows 10/11 host/guest configuration. The DX renderer loads but forces one to choose between the visual defect in Chrome or no GPU acceleration at all. I don't need to make a case because the sheer volume of users affected by the bug already have. This has been amazing, but I'm quickly losing interest. Our dialouge will provide insight to others who seek answers and perhaps even a degree of satisfaction. Who knows, maybe we've stirred the waters enough to prompt real action. Thank-you for the opportunity to represent.


2ff7e9595c


 
 
 

Recent Posts

See All

Comments


© 2023 by The Green Conference. Proudly created with Wix.com. 

bottom of page