algorithmic modeling for Rhino
Hi all-
I have been working with the Display Conduit for a component group that manages custom HUDs, and have had some good success. I have been working primarily with 3D objects, but writing them very close to the screen (the model unit equivalent of a pixel deep). I am using the DrawForeground override to generate these objects...everything is fine, except that we'd also really like the users to be able to output high quality images directly from the viewport. Using the ViewPortCapture (either to file or clipboard) with higher scales can create some excellent images...but here's where we run into trouble.
The geometry that is created close to the screen through the Display Conduit tiles along with the resolution in the output image...so even though the rest of the model geometry scales up, the HUD geometry stays the same resolution but gets repeated in a grid (2x2 at 2 scale, 3x3 at 3 scale, etc.). What is interesting is any geometry created in the normal model space (say, a circle at the WorldXY) gets rendered correctly. I have also tried using the CalculateBoundingBox override, using bounding boxes for the objects drawn, but it doesn't seem to help.
I have picked up on a discussion over at the McNeel forums, but haven't gotten any guidance over there, and was curious if anyone here had any pointers.
thanks!
Tags:
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by