It is true that those who have access to OctaneRender for DAZ Studio plugin can also use it to gather an estimate if the scene will fit into VRAM in Iray as well. repeat as necessary until scene fits into VRAM step 4) automatically or manually refresh the Iray live preview viewport and update VRAM scene information step 3) user makes changes to texture size and geometry in addons based on the information gathered step 2) VRAM information for the current scene is displayed in DAZ Studio, plugins and addons step 1) user activates the Iray live preview windows so VRAM information of the current scene is gathered > When the Iray live preview window is in use then all the information about VRAM use should in theory be accessible. I hoped that sooner or later someone at DAZ3D would be able to make a similar workflow possible with Nvidia Iray: Nevertheless the moment the live viewport is activated all the VRAM information based on the current scene remains available until the moment the user makes any changes to the scene. How VRAM information is gathered in other 3rd party pluginsĪs long as the live render engine viewport is not active there is no VRAM information available. Tools to reduce texture size with VRAM information included
space used by the software itself (engine runtime data, nodesystem data)
space reserved for the rendered images (frame buffer) Since 2013 the OctaneRender plugin for DAZ Studio featured both basic and even advanced tools to monitor the scene size in VRAM and even adjust the texture size. how to know exactly how much space each texture and scene object takes in VRAM. Nevertheless, on a regular basis there are threads on the forum of customers who are confused It seems some artists and developers creating plugins and addons for DAZ Studio either are struggling with this limitation or do not feel like customers are interested in accurate VRAM information. Users have to carefully choose texture sizes and subidvision levels of geometry.Ĭurrently DAZ Studio users are forced to make such changes blindly in a trial and error way without knowing for sure if the scene will fit VRAM or not.īased on some other posts a main challenge of monitoring VRAM is that information can only be gathered when the live rendering preview viewport is in use.
Since Iray has been introduced in 2015 the same issues and challenges remain unadressed for GPU rendering with DAZ Studio:ĭAZ Studio does not offer any official tools that show accurate VRAM information of the current scene.Īs a consequence users do not have any clear way to tell when exactly Iray switches from GPU mode to CPU mode when scenes do not fit the VRAM.
0 kommentar(er)
