Hi @AbrahamYezioro , @charlie.brooker , and @realrhino1 ,
Thanks for bringing this to my attention and I’m sorry that I missed seeing it 3 months ago.
I don’t really have control over how the native Rhino commands run so I don’t think that I will be able to do anything about the native Rhino ViewCaptureToFile command unless someone from the McNeel team believes that it can be addressed (CC: @wim and @piac ). The issue fundamentally results from how the Rhino DisplayPipeline renders the Sprite and 2dText objects on the screen. Because these objects are specified in 2D screen coordinates, this results in them getting repeated whenever a view is captured, which is larger than the current viewport.
Granted, I may be able to get the LB Capture View component to work correctly because we fully control the code that is running there. I’ll also note, @charlie.brooker , that the transparent_ option on that component does not have the issue that you cite there and I remember revising the code in the component towards this end. So I generally recommend using that component if you want the best compatibility with how we make the graphics in Ladybug Tools.
Let me see if I can figure something out to get the Ladybug Capture View component to work and I’ll post back here if I find a solution.