Tweet
Just thought I'd post this as a warning to you all...
I knew about the problems with the bitmap pager, but as my workstation and most of my nodes were running fine, the possibility that it would reduce one of my render nodes to about 50% efficiency didn't occur to me. I just assumed the node had some serious driver/hardware problems....
so one windows reinstall, fresh drivers, fresh max install, fresh vray install, some TLC, and some industrial language later I for some reason decided to switch off the bitmap pager... and lo and behold the problem was solved! incredible!
What is even more amazing is that if I render my suspect scene with no textures and no map, the problem remains.... So, with NO bitmaps being rendered, 3dsmax still renders at about 50% cpu if the bitmap pager is enabled...
I thought this problem had been resolved in recent hotfixes? Apparently not
grrrrr.
I knew about the problems with the bitmap pager, but as my workstation and most of my nodes were running fine, the possibility that it would reduce one of my render nodes to about 50% efficiency didn't occur to me. I just assumed the node had some serious driver/hardware problems....
so one windows reinstall, fresh drivers, fresh max install, fresh vray install, some TLC, and some industrial language later I for some reason decided to switch off the bitmap pager... and lo and behold the problem was solved! incredible!
What is even more amazing is that if I render my suspect scene with no textures and no map, the problem remains.... So, with NO bitmaps being rendered, 3dsmax still renders at about 50% cpu if the bitmap pager is enabled...
I thought this problem had been resolved in recent hotfixes? Apparently not
grrrrr.
