Tweet
Hello,
I've been comparing export speeds for the .vrscene exporter within 3ds max recently. I've found some cases in witch the export gets really slow and memory intensive for no apparent reason. For examble:
For all these examples I'm using the "vrayExportRTScene" Maxscript command:
I'm having a scene containing just VrayProxy objects which load alembic files with animation (animated trees) and a light. If I export this scene to a .vrscene file, the .vrscene file stays nice and small and the export is lightning fast.
Now If I would apply a geometry changing modifier to the objects like bend or turbosmooth or whatever, I'd understand that the export speed would be MUCH slower and file size of the .vrscene file would get huge because it would have to re-write all that animation information into the .vrscene file. So far so good. What I don't understand is: If I apply a VrayDisplacement modifier to the VrayProxy Objects it does not change geometry, only the link to the alembic file gets written into the vrscene file, not the geometry itself. But the export speed is really really slow compared to not having the VrayDisplacement modifiers there. The .vrscene file stays nicely small after the export but the export itself takes a very long time.
Now what I've found out is, that if I use disablesceneredraw() prior to vrayExportRTScene() the export is lighting fast again, my question now is: is it "save" do do it this way? In all my tests, this worked great so far, are there cases in which you guys grab information from the viewport that would be "missed" by the exporter if the redraw is disabled? Would you guys have any concerns?
If it is save to use, I'd recommend you guys to add this option to the gui dialog asap because from my tests, the export is a lot faster in most of the cases even if a lot of info is written to the .vrscene file.
This could prevent potential frustration for people who want to use the gui exporter by a quite significant margin.
Thank you
-Robert
I've been comparing export speeds for the .vrscene exporter within 3ds max recently. I've found some cases in witch the export gets really slow and memory intensive for no apparent reason. For examble:
For all these examples I'm using the "vrayExportRTScene" Maxscript command:
I'm having a scene containing just VrayProxy objects which load alembic files with animation (animated trees) and a light. If I export this scene to a .vrscene file, the .vrscene file stays nice and small and the export is lightning fast.
Now If I would apply a geometry changing modifier to the objects like bend or turbosmooth or whatever, I'd understand that the export speed would be MUCH slower and file size of the .vrscene file would get huge because it would have to re-write all that animation information into the .vrscene file. So far so good. What I don't understand is: If I apply a VrayDisplacement modifier to the VrayProxy Objects it does not change geometry, only the link to the alembic file gets written into the vrscene file, not the geometry itself. But the export speed is really really slow compared to not having the VrayDisplacement modifiers there. The .vrscene file stays nicely small after the export but the export itself takes a very long time.
Now what I've found out is, that if I use disablesceneredraw() prior to vrayExportRTScene() the export is lighting fast again, my question now is: is it "save" do do it this way? In all my tests, this worked great so far, are there cases in which you guys grab information from the viewport that would be "missed" by the exporter if the redraw is disabled? Would you guys have any concerns?
If it is save to use, I'd recommend you guys to add this option to the gui dialog asap because from my tests, the export is a lot faster in most of the cases even if a lot of info is written to the .vrscene file.
This could prevent potential frustration for people who want to use the gui exporter by a quite significant margin.
Thank you
-Robert
Comment